dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
7952
share rss forum feed

Smallfry7

join:2007-01-25
Payson, UT

Netflix HD Streaming and Comcast

So I keep getting really bad picture quality on Netflix (anywhere from 1 bar to 4 bars). I finally decided to call them and see what was going on. Apparently my connection to them is very sporadic. They say that I am getting anywhere from 12mbps to .9mbps.

Naturally, I didn't believe them because I had just ran a SpeedTest and got 20mbps download. He said that they require a long term stable connection over 5mbps, so I ran a 700MB legal torrent and that thing did not deviate more than 5% from 12mbps the entire time.

I angrily called them back, but they insisted that it was either a hardware issue (like a router), a packet loss issue, or a routing issues on the ISP's end.

I know that Comcast doesn't throttle connections to specific services, but you guys know that they legally are able to now, right?

The sad thing is that I have to agreed with Netflix on this one. Something is very wrong and certain connections are getting throttled. I can SpeedTest to some locations fine, but others just plain suck.







Isn't this a little strange?

ssavoy
Premium
join:2007-08-16
Dallas, PA
Reviews:
·Anveo
Your pings seem really high for a cable connection. The only thing Comcast does throttle is your modem, only if A) Your modem is the source of congestion in your local area, and B) Other modems are experiencing service degradation because of you.

I've downloaded gigs worth of updates without being throttled, also partly because I'm in a rural area.

from the speed tests it looks like there's a congestion issue specifically in the Salt Lake City area-ish. And, maybe the same link is used for Netflix streaming. I really doubt this if your tests to Palo Alto are good, though. Have you tried PingTest.net just for the heck of it?
--
»www.speedtest.net/result/5980632 ··· 3272.png

Smallfry7

join:2007-01-25
Payson, UT
Yeah, don't even bother telling me about the pings. I've contacted Comcast through every channel about that. They usually refuse to listen or help, especially if you try to call them. "You must delete your temporary internet files to get better routing and a better ping.
" lame.

What is basically happening is that Comcast is running all of their traffic through a single hub here depending on IP address. Most IP addresses run all traffic through Seattle or Texas. Luckily, I kept changing my MAC until I got one that runs always through Denver. It still sucks, but it is definitely better than the alternatives.

PingTest is always stable and no packet loss, albeit high latency.

I am only being throttled to specific destinations on the internet. How is that possible? It seems that they have limited bandwidth for certain backbone peers. Could this be it?


beachintech
There's sand in my tool bag
Premium
join:2008-01-06
kudos:5
reply to Smallfry7
»Comcast High Speed Internet FAQ »How To Get Help!

take your router out and run some tests as well...
--
Tech at the Beach.
I speak for myself, not my employer.

ssavoy
Premium
join:2007-08-16
Dallas, PA
Reviews:
·Anveo
reply to Smallfry7
said by Smallfry7:

I am only being throttled to specific destinations on the internet. How is that possible? It seems that they have limited bandwidth for certain backbone peers. Could this be it?
That's definitely a possibility. I have no idea what their bandwidth is like (probably huge), but if they only have let's say 100mbps to Level3 in your area and 10gbps to Level3 to Palo Alto, then yes your connection would appear to be throttled to anything going over Level3 in your area (i.e, Netflix streaming). Level3 is a backbone BTW

Can you do a traceroute to Netflix, and then a second traceroute to Google just so I can see if they differ at all?
--
»www.speedtest.net/result/5980632 ··· 3272.png

Smallfry7

join:2007-01-25
Payson, UT
Target Name: netflix.com
IP: 208.75.76.17
Date/Time: 5/16/2010 7:46:48 PM

1 2 ms 2 ms 1 ms 2 ms 2 ms [192.168.1.1]
2 * * * * * [-]
3 10 ms 12 ms 9 ms 18 ms 10 ms te-8-2-ur02.orem.ut.utah.comcast.net [68.85.39.5]
4 15 ms 34 ms 12 ms * 25 ms te-8-1-ar02.saltlakecity.ut.utah.comcast.net [68.87.170.33]
5 27 ms 38 ms 26 ms 26 ms 31 ms te-0-0-0-0-cr01.denver.co.ibone.comcast.net [68.86.90.201]
6 88 ms 74 ms 73 ms 72 ms 72 ms pos-0-14-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.130]
7 79 ms 90 ms 86 ms 75 ms 74 ms pos-0-1-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.86.50]
8 76 ms 93 ms 77 ms 92 ms 81 ms [75.149.230.90]
9 80 ms * 90 ms 98 ms 74 ms vlan955.jnrt-edge02.prod1.netflix.com [69.53.225.30]
10 78 ms * * * * te1-8.csrt-agg02.prod1.netflix.com [69.53.225.10]
11 76 ms 79 ms 77 ms 74 ms 73 ms www.dc1.netflix.com [208.75.76.17]

Ping statistics for netflix.com
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 73ms, Maximum = 79ms, Average = 75ms

Target Name: google.com
IP: 74.125.19.104
Date/Time: 5/16/2010 7:47:25 PM to 5/16/2010 7:47:32 PM

1 2 ms 2 ms 1 ms 1 ms 1 ms 2 ms 2 ms 2 ms [192.168.1.1]
2 * * * * * * * N/A [-]
3 11 ms 11 ms 11 ms 22 ms 31 ms 31 ms 10 ms 11 ms te-8-2-ur02.orem.ut.utah.comcast.net [68.85.39.5]
4 12 ms 11 ms 14 ms 13 ms 12 ms 13 ms 12 ms 11 ms te-8-1-ar02.saltlakecity.ut.utah.comcast.net [68.87.170.33]
5 26 ms 26 ms 25 ms 32 ms 26 ms 31 ms 33 ms 27 ms te-0-0-0-1-cr01.denver.co.ibone.comcast.net [68.86.90.133]
6 41 ms 41 ms 50 ms 40 ms 41 ms 48 ms 40 ms 40 ms pos-0-9-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.174]
7 * 49 ms 40 ms 43 ms 41 ms 42 ms 40 ms 49 ms pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.90]
8 87 ms 80 ms 79 ms 80 ms 80 ms 80 ms 79 ms N/A [75.149.231.70]
9 82 ms * 80 ms 80 ms * 94 ms 83 ms 93 ms [72.14.233.77]
10 84 ms 79 ms 79 ms 82 ms 81 ms 79 ms 79 ms 80 ms [72.14.233.111]
11 82 ms 80 ms 78 ms 131 ms 90 ms 81 ms 78 ms N/A [216.239.43.144]
12 80 ms 99 ms 78 ms 82 ms 78 ms 81 ms 80 ms 80 ms nuq04s01-in-f104.1e100.net [74.125.19.104]

Ping statistics for google.com
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 78ms, Maximum = 99ms, Average = 82ms

I'm working on trying it out without the router right now, but my routing does change with MAC address, so be forewarned.

ssavoy
Premium
join:2007-08-16
Dallas, PA
Reviews:
·Anveo
reply to Smallfry7
I looked up the IP 75.149.231.70 (which is in your 2nd traceroute, and the first spot where high pings appear). The site I looked it up from says it's in Salt Lake City, and it appears to be a Comcast router.

If that's the case I find it odd you're being routed from Utah to Texas back to Utah again.

As for the first traceroute, it seemed like it dropped packets on Netflix's end. Overall your connection doesn't seem horrible, but at the same time it looks like stuff from Netflix did drop a bit before reaching you.

But again that Utah -> Texas -> Utah routing is kind of interesting.
--
»www.speedtest.net/result/5980632 ··· 3272.png

Nobbie16

join:2000-09-28
Jersey City, NJ
reply to Smallfry7
Conducting a traceroute to the domain name of the company providing the video streaming services is not necessarily accurate as the streaming can be (and most likely is) from an entirely different loacation. To get a true picture of what's happening along the route you need the exact IP address or URL as the routing can be quite different to the above results.

Smallfry7

join:2007-01-25
Payson, UT
reply to ssavoy
My connection with no router

Target Name: netflix.com
IP: 208.75.76.17
Date/Time: 5/16/2010 7:58:53 PM

1 * * * * * [-]
2 11 ms 9 ms 9 ms 12 ms 8 ms te-8-2-ur01.orem.ut.utah.comcast.net [68.85.39.1]
3 15 ms 16 ms 13 ms 15 ms 11 ms te-8-1-ar01.saltlakecity.ut.utah.comcast.net [68.87.170.25]
4 28 ms 30 ms 29 ms 40 ms 31 ms te-0-1-0-1-cr01.seattle.wa.ibone.comcast.net [68.86.90.205]
5 32 ms 34 ms 35 ms 38 ms 33 ms pos-0-9-0-0-cr01.portland.or.ibone.comcast.net [68.86.85.102]
6 44 ms 44 ms 44 ms 44 ms 45 ms pos-1-12-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.86.229]
7 67 ms 64 ms 63 ms 59 ms 58 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.181]
8 78 ms 77 ms 61 ms 62 ms 64 ms pos-0-0-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.86.54]
9 61 ms 62 ms 61 ms 66 ms 62 ms [75.149.230.90]
10 62 ms 62 ms 63 ms 89 ms 63 ms vlan955.jnrt-edge02.prod1.netflix.com [69.53.225.30]
11 64 ms 62 ms 63 ms 65 ms 77 ms te1-8.csrt-agg02.prod1.netflix.com [69.53.225.10]
12 78 ms 62 ms 63 ms 61 ms 66 ms www.dc1.netflix.com [208.75.76.17]

Ping statistics for netflix.com
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 61ms, Maximum = 78ms, Average = 66ms

Target Name: google.com
IP: 74.125.19.103
Date/Time: 5/16/2010 8:00:32 PM

1 * * * [-]
2 15 ms 8 ms 8 ms te-8-2-ur01.orem.ut.utah.comcast.net [68.85.39.1]
3 16 ms 22 ms 20 ms te-8-1-ar01.saltlakecity.ut.utah.comcast.net [68.87.170.25]
4 31 ms 29 ms 33 ms te-0-1-0-4-cr01.seattle.wa.ibone.comcast.net [68.86.90.185]
5 30 ms 28 ms 43 ms pos-0-2-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.85.42]
6 59 ms 63 ms 60 ms [75.149.231.90]
7 60 ms 59 ms 59 ms [209.85.249.34]
8 63 ms 60 ms 69 ms [209.85.240.228]
9 59 ms 61 ms 66 ms [216.239.47.185]
10 N/A N/A 71 ms [209.85.251.94]
11 63 ms 59 ms 60 ms nuq04s01-in-f103.1e100.net [74.125.19.103]

Ping statistics for google.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 59ms, Maximum = 63ms, Average = 60ms

Welcome to the world of having all traffic routed through Seattle.

Utah > Seattle > Anywhere








That was all without a router.

My modem is a RCA DHG536C.

RF Parameters
Downstream
Frequency 531 MHz Power 0 dBmV
Signal to Noise Ratio 39 dB Modulation QAM256
Upstream
Frequency 28 MHz Power 34 dBmV
Upstream Data Rate 2560 Ksym/sec Modulation QAM16

Smallfry7

join:2007-01-25
Payson, UT
I sniffed out some packets that were being used by netflix while streaming vids. The IP address is actually on the amazon cloud, I think.

Target Name: ec2-184-73-248-217.compute-1.amazonaws.com
IP: 184.73.248.217
Date/Time: 5/16/2010 8:24:31 PM to 5/16/2010 8:24:40 PM

1 * * * * * * * * * * [-]
2 10 ms 14 ms 10 ms 9 ms 15 ms 25 ms 23 ms 23 ms 17 ms 10 ms te-8-2-ur01.orem.ut.utah.comcast.net [68.85.39.1]
3 14 ms 11 ms 14 ms 10 ms 13 ms 10 ms 12 ms 10 ms 11 ms 11 ms te-8-1-ar01.saltlakecity.ut.utah.comcast.net [68.87.170.25]
4 31 ms 30 ms 28 ms 32 ms 52 ms 28 ms 44 ms 30 ms 37 ms 30 ms te-0-1-0-4-cr01.seattle.wa.ibone.comcast.net [68.86.90.185]
5 30 ms 30 ms 40 ms 37 ms 40 ms 30 ms 36 ms 31 ms 33 ms 28 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
6 61 ms 28 ms 37 ms 59 ms 43 ms 50 ms 30 ms 40 ms 31 ms 35 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]
7 41 ms 45 ms 45 ms 45 ms 52 ms 44 ms 46 ms 41 ms 49 ms 51 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
8 63 ms 62 ms 62 ms 73 ms 63 ms 63 ms 64 ms 62 ms 64 ms 77 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
9 63 ms 70 ms 65 ms 76 ms 63 ms 68 ms 66 ms 64 ms 64 ms 67 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
10 100 ms 96 ms 93 ms 94 ms 96 ms 96 ms 94 ms 94 ms 96 ms 104 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]
11 107 ms 105 ms 109 ms 105 ms 105 ms 100 ms 102 ms 92 ms 103 ms 102 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
12 172 ms 93 ms 94 ms 93 ms 94 ms 96 ms 94 ms 93 ms 138 ms 93 ms ae-4-99.edge1.Washington1.Level3.net [4.68.17.208]
13 97 ms 118 ms 94 ms 100 ms 95 ms 93 ms 94 ms 183 ms 93 ms 92 ms AMAZONCOM.edge1.Washington1.Level3.net [4.79.20.14]
14 94 ms 99 ms 114 ms 94 ms 105 ms 97 ms 93 ms 98 ms 98 ms 92 ms [72.21.199.38]
15 104 ms 94 ms 93 ms 97 ms 94 ms 93 ms 92 ms 102 ms 112 ms 92 ms [72.21.222.157]
16 92 ms 105 ms 100 ms 96 ms 97 ms 106 ms 260 ms 240 ms 226 ms 242 ms [216.182.232.53]
17 218 ms 221 ms 217 ms 188 ms 93 ms 93 ms 97 ms 104 ms 95 ms 97 ms [216.182.224.22]
18 97 ms 95 ms 94 ms 95 ms 104 ms 104 ms 96 ms 94 ms 94 ms 93 ms [216.182.232.163]
19 * * * * * * * * * * [-]

Destination not reached in 35 hops


tshirt
Premium
join:2004-07-11
Snohomish, WA
kudos:5
I'm wondering if you are using ComCAST DNS, or a third party?
Third party DNS often does NOT find the best route for multicast/anycast addresses frequently used by video stream providers.

Smallfry7

join:2007-01-25
Payson, UT
Yes sir. First party Comcast DNS.

And proof: This is my DNS according to my laptop.

Target Name: cns.cmc.co.denver.comcast.net
IP: 68.87.85.102
Date/Time: 5/16/2010 9:37:10 PM

1 1 ms 2 ms 3 ms 1 ms 1 ms [192.168.1.1]
2 * * * * * [-]
3 21 ms 11 ms 10 ms 10 ms 12 ms te-8-2-ur02.orem.ut.utah.comcast.net [68.85.39.5]
4 12 ms 35 ms 15 ms 12 ms 12 ms te-8-1-ar02.saltlakecity.ut.utah.comcast.net [68.87.170.33]
5 * * * * * [-]
6 26 ms 25 ms 24 ms 25 ms 26 ms te-1-1-ar01.potomac.co.ndcwest.comcast.net [68.86.72.58]
7 26 ms 25 ms 33 ms 33 ms 26 ms te-5-3-ar01.cmc.co.ndcwest.comcast.net [68.86.206.1]
8 26 ms 36 ms * 29 ms 26 ms te-3-1-ur03.cmc.co.ndcwest.comcast.net [68.86.132.46]
9 26 ms 26 ms 25 ms 33 ms 25 ms vl125.cmc.co.denver.comcast.net [68.87.85.97]
10 * * * * * [-]
11 * * * * * [-]
12 * * * * * [-]
13 * * * * * [-]
14 * * * * * [-]
15 * * * * * [-]
16 * * * * * [-]
17 * * * * * [-]
18 24 ms 25 ms 40 ms 27 ms 24 ms cns.cmc.co.denver.comcast.net [68.87.85.102]

Ping statistics for cns.cmc.co.denver.comcast.net
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 24ms, Maximum = 40ms, Average = 28ms

When streaming netflix, I get packets from limelight and amazon. Which could it be?

Here is Limelight:

Target Name: cds881.lax.llnw.net
IP: 208.111.145.216
Date/Time: 5/16/2010 9:42:05 PM

1 1 ms 7 ms 1 ms 3 ms 1 ms [192.168.1.1]
2 * * * * N/A [-]
3 18 ms 18 ms 32 ms 11 ms 9 ms te-8-2-ur02.orem.ut.utah.comcast.net [68.85.39.5]
4 13 ms 12 ms 76 ms 11 ms 12 ms te-8-1-ar02.saltlakecity.ut.utah.comcast.net [68.87.170.33]
5 42 ms 29 ms 39 ms 24 ms 30 ms te-0-0-0-0-cr01.denver.co.ibone.comcast.net [68.86.90.201]
6 * 63 ms 40 ms 41 ms 43 ms pos-0-8-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.178]
7 53 ms 52 ms * 48 ms 77 ms TenGigabitEthernet6-2.ar3.DAL2.gblx.net [67.17.157.221]
8 52 ms 66 ms 50 ms 48 ms 74 ms Limelight-Dallas.TenGigabitEthernet7-3.ar3.DAL2.gblx.net [64.214.145.150]
9 87 ms 89 ms 100 ms 84 ms 83 ms tge14-3.fr4.phx2.llnw.net [69.28.189.17]
10 78 ms 100 ms 85 ms 75 ms 82 ms tge9-3.fr4.lax.llnw.net [69.28.172.110]
11 86 ms * 105 ms * N/A tge6-4.fr3.lax.llnw.net [69.28.171.205]
12 * * * 92 ms 76 ms ve7.fr3.lax5.llnw.net [68.142.88.198]
13 86 ms 89 ms 85 ms 84 ms 81 ms cds881.lax.llnw.net [208.111.145.216]

Ping statistics for cds881.lax.llnw.net
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 81ms, Maximum = 89ms, Average = 85ms

noname10

join:2009-10-14
said by Smallfry7:

Yes sir. First party Comcast DNS.

And proof: This is my DNS according to my laptop.

Target Name: cns.cmc.co.denver.comcast.net
IP: 68.87.85.102
Date/Time: 5/16/2010 9:37:10 PM

1 1 ms 2 ms 3 ms 1 ms 1 ms [192.168.1.1]
2 * * * * * [-]
3 21 ms 11 ms 10 ms 10 ms 12 ms te-8-2-ur02.orem.ut.utah.comcast.net [68.85.39.5]
4 12 ms 35 ms 15 ms 12 ms 12 ms te-8-1-ar02.saltlakecity.ut.utah.comcast.net [68.87.170.33]
5 * * * * * [-]
6 26 ms 25 ms 24 ms 25 ms 26 ms te-1-1-ar01.potomac.co.ndcwest.comcast.net [68.86.72.58]
7 26 ms 25 ms 33 ms 33 ms 26 ms te-5-3-ar01.cmc.co.ndcwest.comcast.net [68.86.206.1]
8 26 ms 36 ms * 29 ms 26 ms te-3-1-ur03.cmc.co.ndcwest.comcast.net [68.86.132.46]
9 26 ms 26 ms 25 ms 33 ms 25 ms vl125.cmc.co.denver.comcast.net [68.87.85.97]
10 * * * * * [-]
11 * * * * * [-]
12 * * * * * [-]
13 * * * * * [-]
14 * * * * * [-]
15 * * * * * [-]
16 * * * * * [-]
17 * * * * * [-]
18 24 ms 25 ms 40 ms 27 ms 24 ms cns.cmc.co.denver.comcast.net [68.87.85.102]

Ping statistics for cns.cmc.co.denver.comcast.net
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 24ms, Maximum = 40ms, Average = 28ms

When streaming netflix, I get packets from limelight and amazon. Which could it be?

Here is Limelight:

Target Name: cds881.lax.llnw.net
IP: 208.111.145.216
Date/Time: 5/16/2010 9:42:05 PM

1 1 ms 7 ms 1 ms 3 ms 1 ms [192.168.1.1]
2 * * * * N/A [-]
3 18 ms 18 ms 32 ms 11 ms 9 ms te-8-2-ur02.orem.ut.utah.comcast.net [68.85.39.5]
4 13 ms 12 ms 76 ms 11 ms 12 ms te-8-1-ar02.saltlakecity.ut.utah.comcast.net [68.87.170.33]
5 42 ms 29 ms 39 ms 24 ms 30 ms te-0-0-0-0-cr01.denver.co.ibone.comcast.net [68.86.90.201]
6 * 63 ms 40 ms 41 ms 43 ms pos-0-8-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.178]
7 53 ms 52 ms * 48 ms 77 ms TenGigabitEthernet6-2.ar3.DAL2.gblx.net [67.17.157.221]
8 52 ms 66 ms 50 ms 48 ms 74 ms Limelight-Dallas.TenGigabitEthernet7-3.ar3.DAL2.gblx.net [64.214.145.150]
9 87 ms 89 ms 100 ms 84 ms 83 ms tge14-3.fr4.phx2.llnw.net [69.28.189.17]
10 78 ms 100 ms 85 ms 75 ms 82 ms tge9-3.fr4.lax.llnw.net [69.28.172.110]
11 86 ms * 105 ms * N/A tge6-4.fr3.lax.llnw.net [69.28.171.205]
12 * * * 92 ms 76 ms ve7.fr3.lax5.llnw.net [68.142.88.198]
13 86 ms 89 ms 85 ms 84 ms 81 ms cds881.lax.llnw.net [208.111.145.216]

Ping statistics for cds881.lax.llnw.net
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 81ms, Maximum = 89ms, Average = 85ms
When you are tracerouting Limelight what hostname are you using to look up the IP adress? That trace doesn't make any sense and suggests you are either using a hostname specific to LAX (which you shouldn't be), or you are tracing an IP address directly (which you shouldn't be) or you are not using Comcast's local DNS servers, or Comcast DNS's servers are returning you the wrong IP, or ther have some screwed up routing.

Try tracerouting cdn.netflix.com

That should resolve to your local Limelight servers unless you are using custom DNS's servers.


w0g
o.O

join:2001-08-30
Springfield, OR
reply to Smallfry7
Not trying to hi-jack the thread, but how do you get Netflix to stream high-definition? I've watched a lot of Netflix instant streaming and the quality isn't anywhere near HD, it's worse than DVD even... more like VHS quality.
--
www.aimless.us - irc.aimless.us channel #fix


nerdburg
Premium
join:2009-08-20
Schuylkill Haven, PA
kudos:1

1 edit
said by w0g:

Not trying to hi-jack the thread, but how do you get Netflix to stream high-definition? I've watched a lot of Netflix instant streaming and the quality isn't anywhere near HD, it's worse than DVD even... more like VHS quality.
Quality is based on your available bandwidth. Netflix thinks your connection is too slow for HD. Other than getting a faster connection, there isn't anything you can do about it.


JohnInSJ
Premium
join:2003-09-22
Aptos, CA
reply to w0g
said by w0g:

Not trying to hi-jack the thread, but how do you get Netflix to stream high-definition? I've watched a lot of Netflix instant streaming and the quality isn't anywhere near HD, it's worse than DVD even... more like VHS quality.
In addition to nerdburg's comment, you will ONLY get HD via a Netflix appliance - pretty much anything that's not a PC can get HD streams. PC/Mac get low-def stuff that looks worse then youtube, no matter how fast the pipe. This is probably part of their agreement with content producers who don't want any chance of you capturing a HD stream.
--
My place : »www.schettino.us

DDR4040

join:2006-12-25
Maple Shade, NJ
said by JohnInSJ:

said by w0g:

Not trying to hi-jack the thread, but how do you get Netflix to stream high-definition? I've watched a lot of Netflix instant streaming and the quality isn't anywhere near HD, it's worse than DVD even... more like VHS quality.
In addition to nerdburg's comment, you will ONLY get HD via a Netflix appliance - pretty much anything that's not a PC can get HD streams. PC/Mac get low-def stuff that looks worse then youtube, no matter how fast the pipe. This is probably part of their agreement with content producers who don't want any chance of you capturing a HD stream.
Looks like that is no longer the case...

»hd.engadget.com/2010/05/17/netfl ··· -and-ma/


nerdburg
Premium
join:2009-08-20
Schuylkill Haven, PA
kudos:1
I'd love to get HD to my PC...of course I'm pushing my 250MB cap as it is...

MADx

join:2005-05-25
Richmond, IN

2 edits
reply to nerdburg
If you are using the Roku box here is a nice hack to change your streaming quality from the default automatic. I change mine to 2.2Mbps, and I get a constant 4 dots with HD and SD content.

»www.hackingnetflix.com/2008/09/n ··· yer.html


jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
kudos:3
reply to beachintech
said by beachintech:

»Comcast High Speed Internet FAQ »How To Get Help!

take your router out and run some tests as well...
I think this is good advice. In particular, post your RF levels! (»Comcast High Speed Internet FAQ »Viewing the Modem's Signal Levels, Firmware Version & Log Entries)

Also, tracing to NetFlix's website is totally different from where their content is sourced. They use a variety of CDNs, mostly Akamai these days. We have no control over where Akamai may serve the content from though.
--
JL
Comcast

Smallfry7

join:2007-01-25
Payson, UT

2 edits
reply to Smallfry7
Hey everyone. My internet still sucks.

RF Parameters
Downstream
Frequency 531 MHz Power 0 dBmV
Signal to Noise Ratio 38 dB Modulation QAM256
Upstream
Frequency 28 MHz Power 33 dBmV
Upstream Data Rate 2560 Ksym/sec Modulation QAM16

Check out my thread on the comcast forum

»forums.comcast.net/t5/Internet-C ··· p/775498

Check out this routing fail

Target Name: hexillion.com
IP: 70.84.211.98
Date/Time: 6/28/2010 6:36:48 PM

1 1 ms 1 ms 1 ms 1 ms [192.168.1.1]
2 * * * * [-]
3 10 ms 9 ms 10 ms 9 ms te-8-2-ur01.orem.ut.utah.comcast.net [68.85.39.1]
4 11 ms 13 ms 10 ms 14 ms te-8-1-ar01.saltlakecity.ut.utah.comcast.net [68.87.170.25]
5 29 ms 31 ms 30 ms 30 ms te-0-1-0-4-cr01.seattle.wa.ibone.comcast.net [68.86.90.185]
6 35 ms 34 ms 33 ms 35 ms pos-0-11-0-0-cr01.portland.or.ibone.comcast.net [68.86.85.110]
7 60 ms 46 ms 46 ms 45 ms pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.197]
8 65 ms 68 ms 67 ms 66 ms pos-1-13-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.86.2]
9 65 ms * 64 ms 74 ms pos-0-12-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.118]
10 102 ms 65 ms 76 ms * pos-0-3-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.154]
11 79 ms 64 ms * 65 ms theplanet-cr01.dallas.tx.ibone.comcast.net [75.149.228.2]
12 * * 65 ms 67 ms te3-5.dsr02.dllstx3.theplanet.com [70.87.253.90]
13 * * * * [-]
14 65 ms 66 ms 65 ms 66 ms po2.car01.dllstx5.theplanet.com [70.87.254.6]
15 64 ms 68 ms 71 ms 67 ms hexillion.com [70.84.211.98]

Ping statistics for hexillion.com
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 64ms, Maximum = 71ms, Average = 67ms


meoge

join:2008-03-07
Bloomington, IN
reply to Smallfry7
I've had the same Netflix streaming issues for a long time now and it's to the point that I simply don't even try anymore. It's so inconsistent that I can't narrow down where the problem is. I've got 16/2 service and my speeds seem good most of the time, but I'll only get 1 bar most of the time (Hence the inconsistent part) from my Xbox or my samsung blu-ray player. I'll then go to my computer and try to stream and it'll work in HD. I'll run speed test and they'll be very fast but still won't be able to get more than 1 bar in my living room. I've tried plugging the Xbox directly into my modem with the same results. Everything is hard wired with Cat6 in my house so I'm just not sure where the problem is. I do occasionally get a full HD stream in the living room, but there's no rhyme or reason to it. I've never called Netflix about the problem, but I guess I could give that a try. I seen today that Hulu will be availble on the PS3 and xbox soon, but I wouldn't pay $10 a month at this point for any streaming service unless I knew it would work in HD all the time. I thought that was why I bought the faster connection.


Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:10

1 recommendation

reply to JohnInSJ
said by JohnInSJ:

said by w0g:

Not trying to hi-jack the thread, but how do you get Netflix to stream high-definition? I've watched a lot of Netflix instant streaming and the quality isn't anywhere near HD, it's worse than DVD even... more like VHS quality.
In addition to nerdburg's comment, you will ONLY get HD via a Netflix appliance - pretty much anything that's not a PC can get HD streams. PC/Mac get low-def stuff that looks worse then youtube, no matter how fast the pipe. This is probably part of their agreement with content producers who don't want any chance of you capturing a HD stream.
You can stream HD on your PC. There are selections specified for HD viewing on your PC:
--
In God we trust; all others bring data!


JohnInSJ
Premium
join:2003-09-22
Aptos, CA
Yep, this is NEW as of the last month or two... I missed it. Sue me
--
My place : »www.schettino.us