dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
14
Smallfry7
join:2007-01-25
Payson, UT

Smallfry7 to ssavoy

Member

to ssavoy

Re: Netflix HD Streaming and Comcast

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?
ssavoy
Premium Member
join:2007-08-16
Dallas, PA

ssavoy

Premium Member

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?
Smallfry7
join:2007-01-25
Payson, UT

Smallfry7

Member

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.
Nobbie16
join:2000-09-28
Jersey City, NJ

Nobbie16

Member

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.