Time Warner Cable YouTube throttling

Thu Mar 7 08:46:40 UTC 2013

Also if your upstream has Google Global Cache (or whatever it's
called), the results can be very different I suppose.

Does Google use different naming structure for IPv6 CDN? Maybe this
particular cache does not offer IPv6.

;; QUESTION SECTION:
;r3---sn-n2uxaxjvh-j5xe.c.youtube.com. IN A

;; ANSWER SECTION:
r3---sn-n2uxaxjvh-j5xe.c.youtube.com. 60 IN CNAME
r3.sn-n2uxaxjvh-j5xe.c.youtube.com.
r3.sn-n2uxaxjvh-j5xe.c.youtube.com. 1800 IN A   64.53.1.78

;; QUESTION SECTION:
;r3---sn-n2uxaxjvh-j5xe.c.youtube.com. IN AAAA

;; ANSWER SECTION:
r3---sn-n2uxaxjvh-j5xe.c.youtube.com. 60 IN CNAME
r3.sn-n2uxaxjvh-j5xe.c.youtube.com.

Level3 peers with Google, I am curious why it hand the traffic off to XO.

> On Wed, Mar 6, 2013 at 10:46 PM, Mark Jeremy <mejndp at rit.edu> wrote:

>> traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 30 hops
>> max,
>> 60 byte packets
>>  3  rit-rit1-pp-core1-vlan2811.rit.edu (129.21.8.42)  0.508 ms  0.497 ms
>> 0.484 ms
>>  4  te-7-2.car2.Buffalo1.Level3.net (4.59.214.21)  2.293 ms  2.294 ms
>>  2.282
>> ms
>>  5  ae-4-4.ebr2.NewYork1.Level3.net (4.69.140.242)  10.332 ms  10.339 ms
>> 11.022 ms
>>  6  ae-72-72.csw2.NewYork1.Level3.net (4.69.148.38)  15.274 ms  10.212 ms
>> ae-92-92.csw4.NewYork1.Level3.net (4.69.148.46)  10.204 ms
>>  7  ae-1-60.edge2.NewYork1.Level3.net (4.69.155.16)  10.202 ms
>> ae-2-70.edge2.NewYork1.Level3.net (4.69.155.80)  10.174 ms  10.171 ms
>>  8  206.111.13.65.ptr.us.xo.net (206.111.13.65)  10.160 ms  10.345 ms
>> 10.336 ms
>>  9  207.88.14.185.ptr.us.xo.net (207.88.14.185)  18.555 ms  18.541 ms
>> 20.749 ms
>> 10  ae0d1.cir1.ashburn-va.us.xo.net (207.88.13.65)  16.241 ms  16.322 ms
>> 16.261 ms
>> 11  209.48.42.86 (209.48.42.86)  16.673 ms  64.114 ms  64.054 ms
>> 12  208.117.251.184 (208.117.251.184)  16.313 ms  16.306 ms  16.486 ms