nanog mailing list archives
Re: Time Warner Cable YouTube throttling
From: Derek Ivey <derek () derekivey com>
Date: Wed, 6 Mar 2013 22:47:38 -0500
I think your trace routes are just to their web servers. You need to figure out where the actual videos are being streamed from. I used the Developer Tools (Network tab) in Google Chrome to figure this out. The FQDNs will probably look like the ones in my trace routes. Derek On Mar 6, 2013, at 10:38 PM, John Zettlemoyer <john () razorservers com> wrote:
I've been seeing the same thing and was thinking it was me. Just to add to some of the results here... Verizon FIOS 1 32 ms 3 ms 5 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 2 33 ms 6 ms 7 ms g0-3-3-7.cmdnnj-lcr-22.verizon-gni.net [130.81.183.186] 3 22 ms 22 ms 21 ms xe-4-1-8-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.84] 4 22 ms 21 ms 21 ms 0.so-0-0-0.xt2.nyc4.alter.net [152.63.17.21] 5 58 ms 24 ms 24 ms tengige0-5-4-0.gw8.nyc4.alter.net [152.63.18.206] 6 * 76 ms 76 ms google-gw.customer.alter.net [152.179.72.62] 7 25 ms 21 ms 24 ms 209.85.255.68 8 21 ms 34 ms 34 ms 209.85.252.242 9 30 ms 28 ms 31 ms 209.85.249.11 10 31 ms 29 ms 29 ms 72.14.236.149 11 38 ms 36 ms 36 ms 72.14.238.173 12 31 ms 29 ms 31 ms iad23s05-in-f8.1e100.net [74.125.228.8] Comcast 1 33 ms 15 ms 25 ms 68.38.220.1 2 8 ms 10 ms 15 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 3 10 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 4 14 ms 15 ms 15 ms pos-3-6-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.92.161] 5 15 ms 13 ms 14 ms pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.26] 6 * 23 ms 25 ms 75.149.231.62 7 17 ms 15 ms 14 ms 209.85.252.46 8 17 ms 16 ms 15 ms 72.14.238.173 9 17 ms 15 ms 16 ms iad23s05-in-f8.1e100.net [74.125.228.8] Our datacenter 1 <1 ms <1 ms <1 ms static.razorinc.net [70.34.208.101] 2 <1 ms <1 ms <1 ms 70.34.251.9 3 <1 ms <1 ms <1 ms xe-0-2-0.phi10.ip4.tinet.net [199.168.63.233] 4 2 ms 3 ms 2 ms xe-7-2-1.was14.ip4.tinet.net [89.149.181.174] 5 3 ms 3 ms 3 ms 72.14.213.61 6 4 ms 4 ms 4 ms 216.239.46.248 7 5 ms 5 ms 5 ms 72.14.238.173 8 5 ms 5 ms 5 ms iad23s05-in-f8.1e100.net [74.125.228.8] It would be nice if the ISPs and content providers could work out something when dealing with this much traffic and clearly needing to add capaicty. It's nice to dream too... John
Current thread:
- Re: Time Warner Cable YouTube throttling, (continued)
- Message not available
- Re: Time Warner Cable YouTube throttling Grant Ridder (Mar 06)
- Re: Time Warner Cable YouTube throttling Min (Mar 06)
- Re: Time Warner Cable YouTube throttling Derek Ivey (Mar 06)
- Re: Time Warner Cable YouTube throttling Min (Mar 06)
- Re: Time Warner Cable YouTube throttling Derek Ivey (Mar 06)
- Message not available
- Re: Time Warner Cable YouTube throttling Derek Ivey (Mar 06)
- Re: Time Warner Cable YouTube throttling Robert M. Enger (Mar 06)
- Re: Time Warner Cable YouTube throttling Andrew Fried (Mar 06)
- Re: Time Warner Cable YouTube throttling Derek Ivey (Mar 06)
- RE: Time Warner Cable YouTube throttling John Zettlemoyer (Mar 06)
- RE: Time Warner Cable YouTube throttling Mark Jeremy (Mar 06)
- Re: Time Warner Cable YouTube throttling Grant Ridder (Mar 06)
- Re: Time Warner Cable YouTube throttling Yang Yu (Mar 07)
- Re: Time Warner Cable YouTube throttling Warren Bailey (Mar 07)