jimpal wrote:
boylan wrote:
. . . The only alternative I see is that they knowingly allow serious bottlenecks (at least with respect to throughput rates, maybe few customers) to occur, at least to Minnesota, for probably business reasons ($$$) and are just letting it slide knowing that most customers won't cancel because the next best alternative has very limited content.
From my own situation, I just wonder is ANYONE able to stream Netflix from my area?!?
Yes, boylan, I have been able to stream at full 5800 kbps on my Apple TV 3 in my Minneapolis home for about a month now. It was bad for a while before that, but then suddenly got better. No action at all from me except waiting for Netflix to get it right.
I agree with you, it is business. Netflix and the ISP's each have an iron in the fire, and I believe that once Netflix gets their routing right and makes the proper financial agreements with the ISP's all will be well again.
Editing error. I see the same thing as you. I can get 4300 on my iPad Air about 530am and as soon as little kids start streaming X Men it goes to 235kbps. Typical of every device I own except ATV (5800 solid now).
I suppose they might have some follow up training but there was no reference to it on the Netflix employee discussions I saw.
The reason I mention Minnesota is that I'm here and I don't know anyone who is having any luck with Netflix except with ATV devices since mid-December. I supppose I should check Chromecast again to confirm that is still impacted, but there are thousands of Comcast customers here that have Netflix. Are we all using the same route and it's garage? Or just those using my route:
1 |
<1 ms |
<1 ms |
<1 ms router.asus.com [192.168.0.1] |
2 |
10 ms |
7 ms |
8 ms 73.127.246.1 |
3 |
8 ms |
7 ms |
7 ms te-4-2-ur02.webster.mn.minn.comcast.net [68.85.167.149] |
4 |
8 ms |
17 ms |
15 ms te-8-1-ur01.webster.mn.minn.comcast.net [68.86.232.17] |
5 |
19 ms |
12 ms |
11 ms te-0-2-0-0-ar01.crosstown.mn.minn.comcast.net [68.87.174.149] |
6 |
14 ms |
11 ms |
11 ms pos-0-1-0-0-ar01.roseville.mn.minn.comcast.net [68.87.174.2] |
7 |
21 ms |
20 ms |
19 ms he-1-11-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.94.73] |
8 |
21 ms |
21 ms |
19 ms be-12-pe03.350ecermak.il.ibone.comcast.net [68.86.84.190] |
9 |
20 ms |
29 ms |
21 ms a23-62-97-112.deploy.static.akamaitechnologies.com [23.62.97.112] |
Yes, I know this isn't the return path.
Netflix is responsible for the interconnect port charges from what I've read and been told.
> I am painfully aware that I did nothing to fix the Apple TV issue and it could easily comeback at any time -
> - fingers crossed / touching wood etc.
Know exactly how you feel...