Re: Time Warner Cable YouTube throttling
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 ;; 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 mej...@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
Re: Time Warner Cable YouTube throttling
I had the opportunity to look at this from a TWC fiber customer in Ohio, and this did not seem to affect them. From my Android phone on T-Mobile. The first nationwide 4G network. Original message From: Grant Ridder shortdudey...@gmail.com Date: 03/07/2013 2:22 AM (GMT-05:00) To: Mark Jeremy mej...@rit.edu Cc: John Zettlemoyer j...@razorservers.com,nanog@nanog.org Subject: Re: Time Warner Cable YouTube throttling RIT is probably on a commercial circuit and from what i have seen on this chain so far, it is only affecting home/consumer users. At MSOE (msoe.edu) i dont show any latency but we are on TWTC. Anyone chime in if that is wrong. -Grant On Wed, Mar 6, 2013 at 10:46 PM, Mark Jeremy mej...@rit.edu wrote: Jumping into the bandwagon here to help out. Here's the result from RIT to r19.sn-p5qlsm7d.c.youtube.com, going through at least 4 hops through XO territory. traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 30 hops max, 60 byte packets 1 rit-west1-gw-014-vlan453.rit.edu (129.21.153.254) 0.593 ms 0.584 ms 0.576 ms 2 rit-core1-pp-west2-vlan824.rit.edu (129.21.8.93) 1.938 ms 1.941 ms 2.116 ms 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 -MJ -Original Message- From: John Zettlemoyer [mailto:j...@razorservers.com] Sent: Wednesday, March 06, 2013 11:19 PM To: 'Derek Ivey' Cc: nanog@nanog.org Subject: RE: Time Warner Cable YouTube throttling Yup... This might be more helpful. I went to r19.sn-p5qlsm7d.c.youtube.com for better comparison. Verizon FIOS 1 8 ms 4 ms 4 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 2 9 ms 6 ms 7 ms g0-3-3-6.cmdnnj-lcr-22.verizon-gni.net [130.81.182.44] 310 ms 9 ms 9 ms xe-9-1-2-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.144] 4 8 ms 8 ms 9 ms 0.xe-3-1-0.br3.nyc4.alter.net [152.63.26.117] 523 ms24 ms24 ms 204.255.168.118 633 ms34 ms34 ms 144.232.4.93 722 ms22 ms22 ms sl-crs4-nyc-0-3-5-0.sprintlink.net [144.232.7.122] 825 ms22 ms24 ms sl-crs2-dc-0-4-0-2.sprintlink.net [144.232.8.164] 922 ms21 ms22 ms sl-st31-ash-0-2-0-0.sprintlink.net [144.232.25.15] 1050 ms49 ms49 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 1120 ms19 ms19 ms 208.117.251.184 Comcast 127 ms31 ms21 ms 68.38.220.1 2 8 ms 9 ms11 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 311 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 415 ms16 ms15 ms pos-4-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.93.233] 514 ms14 ms13 ms be-27-pe06.ashburn.va.ibone.comcast.net [68.86.82.174] 615 ms13 ms14 ms 144.232.6.97 715 ms14 ms15 ms sl-st31-ash-0-4-0-3.sprintlink.net [144.232.3.169] 834 ms32 ms31 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 930 ms31 ms31 ms 208.117.251.184 Our DC 11 ms1 ms1 ms static.razorinc.net [70.34.208.101] 21 ms1 ms1 ms mx1.razorinc.net [70.34.252.9] 31 ms1 ms1 ms xe-0-2-0.phi10.ip4.tinet.net [199.168.63.233] 4 3 ms 8 ms 3 ms xe-7-2-1.was14.ip4.tinet.net [89.149.181.174] 5 3 ms 3 ms 3 ms as2828.ip4.tinet.net [77.67.68.14] 6 3 ms 3 ms 3 ms 216.156.8.189.ptr.us.xo.net[216.156.8.189] 7 4 ms 4 ms 4 ms 209.48.42.86 8 4 ms 4 ms 4 ms 208.117.251.184 John
Re: Time Warner Cable YouTube throttling
Jumping on the bandwagon. I have not had the chance to follow the entire thread but have seen this behavior from ATT Uverse, Time Warner, and Verizon FIOS. I believed initially this was a capacity issue with Google and Youtube. The reason for this thought is fairly simple with no scientific troubleshooting invested at this time. I can replicate slowness on ATT Uverse and Time Warner at the exact same times, the anomoly is Verizon FIOS does not align with the other two. When there is slowness on Uverse 99% of the time my Time Warner connections to Youtube will be slow as well even if you are streaming different video's. - Original Message - From: Randy Carpenter rcar...@network1.net To: NANOG nanog@nanog.org Sent: Wednesday, March 6, 2013 3:11:50 PM Subject: Time Warner Cable YouTube throttling We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. This makes speeds go from ~1 Mb/s to the full connection speed (30 Mb/s in my case). It appears that TWC is forcing traffic to this netblock over a congested link, or otherwise throttling it. Trying to communicate this to tech support results in the typical Derrr, what? Does anyone at Time Warner care to comment on WTF? thanks, -Randy
Re: Time Warner Cable YouTube throttling
On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO space, not Google and not TWC space. Would you care to engage in some troubleshooting to help everyone out? :) This makes speeds go from ~1 Mb/s to the full connection speed (30 Mb/s in my case). It appears that TWC is forcing traffic to this netblock over a congested link, or otherwise throttling it. Trying to communicate this to tech support results in the typical Derrr, what? Does anyone at Time Warner care to comment on WTF? thanks, -Randy
Re: Time Warner Cable YouTube throttling
- Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO space, not Google and not TWC space. Would you care to engage in some troubleshooting to help everyone out? :) I'll be happy to help troubleshoot in any way I can. -Randy
Re: Time Warner Cable YouTube throttling
On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter rcar...@network1.net wrote: - Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO space, not Google and not TWC space. Would you care to engage in some troubleshooting to help everyone out? :) I'll be happy to help troubleshoot in any way I can. excellent.. I'll arrange my ducks, let's chat offlist?
Re: Time Warner Cable YouTube throttling
I'd like to help, too, I'm from a TWC business class site with 650 Mbps bandwidth and still regularly poor performance with YouTube. -Rick Sent from my iPhone 4S On Mar 6, 2013, at 4:10 PM, Christopher Morrow morrowc.li...@gmail.com wrote: On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter rcar...@network1.net wrote: - Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO space, not Google and not TWC space. Would you care to engage in some troubleshooting to help everyone out? :) I'll be happy to help troubleshoot in any way I can. excellent.. I'll arrange my ducks, let's chat offlist?
Re: Time Warner Cable YouTube throttling
I don't think it's just Time Warner. Definitely looks like XO. I have Verizon FiOS and it was pretty bad for me as well (not sure if it still is since I'm not home right now). There's also atleast two threads in the Verizon FiOS section on Broadband Reports: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds http://www.dslreports.com/forum/r28071070-How-to-Reddit-YouTube-firewall-rule-with-MI424wr Derek On Wed, Mar 6, 2013 at 5:56 PM, Rick Coloccia coloc...@geneseo.edu wrote: I'd like to help, too, I'm from a TWC business class site with 650 Mbps bandwidth and still regularly poor performance with YouTube. -Rick Sent from my iPhone 4S On Mar 6, 2013, at 4:10 PM, Christopher Morrow morrowc.li...@gmail.com wrote: On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter rcar...@network1.net wrote: - Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO space, not Google and not TWC space. Would you care to engage in some troubleshooting to help everyone out? :) I'll be happy to help troubleshoot in any way I can. excellent.. I'll arrange my ducks, let's chat offlist?
Re: Time Warner Cable YouTube throttling
Can any one provide traceroutes to youtube to see if there is any correlation between last mile providers? -Grant On Wed, Mar 6, 2013 at 6:37 PM, Derek Ivey de...@derekivey.com wrote: I don't think it's just Time Warner. Definitely looks like XO. I have Verizon FiOS and it was pretty bad for me as well (not sure if it still is since I'm not home right now). There's also atleast two threads in the Verizon FiOS section on Broadband Reports: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds http://www.dslreports.com/forum/r28071070-How-to-Reddit-YouTube-firewall-rule-with-MI424wr Derek On Wed, Mar 6, 2013 at 5:56 PM, Rick Coloccia coloc...@geneseo.edu wrote: I'd like to help, too, I'm from a TWC business class site with 650 Mbps bandwidth and still regularly poor performance with YouTube. -Rick Sent from my iPhone 4S On Mar 6, 2013, at 4:10 PM, Christopher Morrow morrowc.li...@gmail.com wrote: On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter rcar...@network1.net wrote: - Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO space, not Google and not TWC space. Would you care to engage in some troubleshooting to help everyone out? :) I'll be happy to help troubleshoot in any way I can. excellent.. I'll arrange my ducks, let's chat offlist?
Re: Time Warner Cable YouTube throttling
I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms 2.167 ms 3 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.497 ms 14.767 ms 14.695 ms 4 0.xe-11-0-0.BR2.IAD8.ALTER.NET (152.63.38.169) 15.001 ms 15.074 ms 15.024 ms 5 144.232.8.209 (144.232.8.209) 118.582 ms 116.717 ms 113.669 ms 6 sl-st31-ash-0-4-0-3.sprintlink.net (144.232.3.169) 114.433 ms 117.698 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 115.981 ms 7 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 123.912 ms 124.402 ms 125.384 ms 8 208.117.251.47 (208.117.251.47) 30.591 ms 30.676 ms 29.528 ms Derek On 3/6/2013 8:31 PM, Grant Ridder wrote: Can any one provide traceroutes to youtube to see if there is any correlation between last mile providers? -Grant On Wed, Mar 6, 2013 at 6:37 PM, Derek Ivey de...@derekivey.com mailto:de...@derekivey.com wrote: I don't think it's just Time Warner. Definitely looks like XO. I have Verizon FiOS and it was pretty bad for me as well (not sure if it still is since I'm not home right now). There's also atleast two threads in the Verizon FiOS section on Broadband Reports: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds http://www.dslreports.com/forum/r28071070-How-to-Reddit-YouTube-firewall-rule-with-MI424wr Derek On Wed, Mar 6, 2013 at 5:56 PM, Rick Coloccia coloc...@geneseo.edu mailto:coloc...@geneseo.edu wrote: I'd like to help, too, I'm from a TWC business class site with 650 Mbps bandwidth and still regularly poor performance with YouTube. -Rick Sent from my iPhone 4S On Mar 6, 2013, at 4:10 PM, Christopher Morrow morrowc.li...@gmail.com mailto:morrowc.li...@gmail.com wrote: On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter rcar...@network1.net mailto:rcar...@network1.net wrote: - Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net mailto:rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time Warner Cable. Some searching on forums and such revealed a work around: Block 206.111.0.0/16 http://206.111.0.0/16 at the router. this was reported elsewhere... it seems odd, since that's XO
Re: Time Warner Cable YouTube throttling
3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms 2.167 ms 3 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.497 ms 14.767 ms 14.695 ms 4 0.xe-11-0-0.BR2.IAD8.ALTER.NET (152.63.38.169) 15.001 ms 15.074 ms 15.024 ms 5 144.232.8.209 (144.232.8.209) 118.582 ms 116.717 ms 113.669 ms 6 sl-st31-ash-0-4-0-3.sprintlink.net (144.232.3.169) 114.433 ms 117.698 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 115.981 ms 7 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 123.912 ms 124.402 ms 125.384 ms 8 208.117.251.47 (208.117.251.47) 30.591 ms 30.676 ms 29.528 ms Derek On 3/6/2013 8:31 PM, Grant Ridder wrote: Can any one provide traceroutes to youtube to see if there is any correlation between last mile providers? -Grant On Wed, Mar 6, 2013 at 6:37 PM, Derek Ivey de...@derekivey.com mailto:de...@derekivey.com wrote: I don't think it's just Time Warner. Definitely looks like XO. I have Verizon FiOS and it was pretty bad for me as well (not sure if it still is since I'm not home right now). There's also atleast two threads in the Verizon FiOS section on Broadband Reports: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds http://www.dslreports.com/forum/r28071070-How-to-Reddit-YouTube-firewall-rule-with-MI424wr Derek On Wed, Mar 6, 2013 at 5:56 PM, Rick Coloccia coloc...@geneseo.edu mailto:coloc...@geneseo.edu wrote: I'd like to help, too, I'm from a TWC business class site with 650 Mbps bandwidth and still regularly poor performance with YouTube. -Rick Sent from my iPhone 4S On Mar 6, 2013, at 4:10 PM, Christopher Morrow morrowc.li...@gmail.com mailto:morrowc.li...@gmail.com wrote: On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter rcar...@network1.net mailto:rcar...@network1.net wrote: - Original Message - On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter rcar...@network1.net mailto:rcar...@network1.net wrote: We have recently been having some serious speed issues with YouTube on our home connections, which are all Time
Re: Time Warner Cable YouTube throttling
The 1st one gets slow at XO and the 2nd and 3rd get slow at Sprint. Now the interesting one with XO is that it is routed in a /30 that is assigned to Google by XO. network:Class-Name:network network:ID:NET-XO-NET-d1302a54 network:Auth-Area:209.48.0.0/15 network:Network-Name:XO-NET-d1302a54 network:Organization;I:GOOGLE INC. (328874-1) network:IP-Network:209.48.42.84/30 network:Admin-Contact;I:XCIA-ARIN network:Tech-Contact;I:XCIA-ARIN network:Created:20120917 network:Updated:20121018 network:Updated-By:ipad...@eng.xo.com -Grant On Wed, Mar 6, 2013 at 8:25 PM, Min qiu.mi...@gmail.com wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms 2.167 ms 3 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.497 ms 14.767 ms 14.695 ms 4 0.xe-11-0-0.BR2.IAD8.ALTER.NET (152.63.38.169) 15.001 ms 15.074 ms 15.024 ms 5 144.232.8.209 (144.232.8.209) 118.582 ms 116.717 ms 113.669 ms 6 sl-st31-ash-0-4-0-3.sprintlink.net (144.232.3.169) 114.433 ms 117.698 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 115.981 ms 7 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 123.912 ms 124.402 ms 125.384 ms 8 208.117.251.47 (208.117.251.47) 30.591 ms 30.676 ms 29.528 ms Derek On 3/6/2013 8:31 PM, Grant Ridder wrote: Can any one provide traceroutes to youtube to see if there is any correlation between last mile providers? -Grant On Wed, Mar 6, 2013 at 6:37 PM, Derek Ivey de...@derekivey.com mailto:de...@derekivey.com wrote: I don't think it's just Time Warner. Definitely looks like XO. I have Verizon FiOS and it was pretty bad for me as well (not sure if it still is since I'm not home right now). There's also atleast two threads in the Verizon FiOS section on Broadband Reports: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds http://www.dslreports.com/forum/r28071070-How-to-Reddit-YouTube-firewall-rule-with-MI424wr Derek On Wed, Mar 6, 2013 at 5:56 PM, Rick Coloccia coloc...@geneseo.edu mailto:coloc...@geneseo.edu wrote: I'd like to help, too, I'm from a TWC
Re: Time Warner Cable YouTube throttling
One thing to keep in mind is that youtube may be anycast. Google's distributed file system is pretty amazing and it could be traffic to one specific datacenter that is possibly slow. -Grant On Wed, Mar 6, 2013 at 8:47 PM, Min qiu.mi...@gmail.com wrote: I use FIOS. In my case, I suspected two things. 1. congestion (my first hub appeared over subscribed) 2. packet out of order (high packet drop in alternet-google could be a symptom of multipath) Not sure which has bigger performance impact to youtube. Min On Wed, Mar 6, 2013 at 9:35 PM, Grant Ridder shortdudey...@gmail.com wrote: The 1st one gets slow at XO and the 2nd and 3rd get slow at Sprint. Now the interesting one with XO is that it is routed in a /30 that is assigned to Google by XO. network:Class-Name:network network:ID:NET-XO-NET-d1302a54 network:Auth-Area:209.48.0.0/15 network:Network-Name:XO-NET-d1302a54 network:Organization;I:GOOGLE INC. (328874-1) network:IP-Network:209.48.42.84/30 network:Admin-Contact;I:XCIA-ARIN network:Tech-Contact;I:XCIA-ARIN network:Created:20120917 network:Updated:20121018 network:Updated-By:ipad...@eng.xo.com -Grant On Wed, Mar 6, 2013 at 8:25 PM, Min qiu.mi...@gmail.com wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms 2.167 ms 3 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.497 ms 14.767 ms 14.695 ms 4 0.xe-11-0-0.BR2.IAD8.ALTER.NET (152.63.38.169) 15.001 ms 15.074 ms 15.024 ms 5 144.232.8.209 (144.232.8.209) 118.582 ms 116.717 ms 113.669 ms 6 sl-st31-ash-0-4-0-3.sprintlink.net (144.232.3.169) 114.433 ms 117.698 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 115.981 ms 7 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 123.912 ms 124.402 ms 125.384 ms 8 208.117.251.47 (208.117.251.47) 30.591 ms 30.676 ms 29.528 ms Derek On 3/6/2013 8:31 PM, Grant Ridder wrote: Can any one provide traceroutes to youtube to see if there is any correlation between last mile providers?
Re: Time Warner Cable YouTube throttling
I use FIOS. Here is my result: HostLoss% Snt Last Avg Best Wrst StDev 1. Wireless_Broadband_Router.home0.0% 165 285.1 563.9 68.2 2007. 376.1 2. L100.WASHDC-VFTTP-127.verizon-gn 0.0% 165 299.8 560.3 59.1 2021. 384.4 3. G0-9-4-1.WASHDC-LCR-22.verizon-g 0.6% 165 241.3 698.7 64.6 24918 1938. 4. so-14-0-0-0.RES-BB-RTR1.verizon- 0.0% 165 217.2 705.7 100.6 24817 1926. 5. 0.xe-4-1-0.XL4.IAD8.ALTER.NET 0.0% 165 308.0 714.6 109.8 24717 1920. 6. TenGigE0-7-2-0.GW7.IAD8.ALTER.NE 0.0% 165 265.3 722.6 103.5 24617 1911. TenGigE0-7-0-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-1.GW7.IAD8.ALTER.NET TenGigE0-7-1-0.GW7.IAD8.ALTER.NET TenGigE0-7-4-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-0.GW7.IAD8.ALTER.NET 7. google-gw.customer.alter.net 59.4% 165 281.3 982.9 162.3 24516 2940. 8. 216.239.46.2480.6% 164 247.3 726.7 112.2 24416 1903. 9. 72.14.238.173 0.0% 164 203.1 729.7 85.9 24315 1895. 10. iad23s05-in-f6.1e100.net 0.6% 164 343.2 712.9 35.1 24215 1890. In my case, I suspected two things. 1. congestion (verizon over subscribed) 2. packet out of order (high packet drops in alternet-google could be a symptom of multipath) Not sure which has bigger performance impact to youtube. Min On Wed, Mar 6, 2013 at 9:35 PM, Grant Ridder shortdudey...@gmail.com wrote: The 1st one gets slow at XO and the 2nd and 3rd get slow at Sprint. Now the interesting one with XO is that it is routed in a /30 that is assigned to Google by XO. network:Class-Name:network network:ID:NET-XO-NET-d1302a54 network:Auth-Area:209.48.0.0/15 network:Network-Name:XO-NET-d1302a54 network:Organization;I:GOOGLE INC. (328874-1) network:IP-Network:209.48.42.84/30 network:Admin-Contact;I:XCIA-ARIN network:Tech-Contact;I:XCIA-ARIN network:Created:20120917 network:Updated:20121018 network:Updated-By:ipad...@eng.xo.com -Grant On Wed, Mar 6, 2013 at 8:25 PM, Min qiu.mi...@gmail.com wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms 2.167 ms 3 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net
Re: Time Warner Cable YouTube throttling
Why are your response times so high at your first hop? Are you maxing out your connection or connected to your router over wireless? Derek On 3/6/2013 9:58 PM, Min wrote: I use FIOS. Here is my result: HostLoss% Snt Last Avg Best Wrst StDev 1. Wireless_Broadband_Router.home0.0% 165 285.1 563.9 68.2 2007. 376.1 2. L100.WASHDC-VFTTP-127.verizon-gn 0.0% 165 299.8 560.3 59.1 2021. 384.4 3. G0-9-4-1.WASHDC-LCR-22.verizon-g 0.6% 165 241.3 698.7 64.6 24918 1938. 4. so-14-0-0-0.RES-BB-RTR1.verizon- 0.0% 165 217.2 705.7 100.6 24817 1926. 5. 0.xe-4-1-0.XL4.IAD8.ALTER.NET 0.0% 165 308.0 714.6 109.8 24717 1920. 6. TenGigE0-7-2-0.GW7.IAD8.ALTER.NE 0.0% 165 265.3 722.6 103.5 24617 1911. TenGigE0-7-0-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-1.GW7.IAD8.ALTER.NET TenGigE0-7-1-0.GW7.IAD8.ALTER.NET TenGigE0-7-4-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-0.GW7.IAD8.ALTER.NET 7. google-gw.customer.alter.net 59.4% 165 281.3 982.9 162.3 24516 2940. 8. 216.239.46.2480.6% 164 247.3 726.7 112.2 24416 1903. 9. 72.14.238.173 0.0% 164 203.1 729.7 85.9 24315 1895. 10. iad23s05-in-f6.1e100.net 0.6% 164 343.2 712.9 35.1 24215 1890. In my case, I suspected two things. 1. congestion (verizon over subscribed) 2. packet out of order (high packet drops in alternet-google could be a symptom of multipath) Not sure which has bigger performance impact to youtube. Min On Wed, Mar 6, 2013 at 9:35 PM, Grant Ridder shortdudey...@gmail.com wrote: The 1st one gets slow at XO and the 2nd and 3rd get slow at Sprint. Now the interesting one with XO is that it is routed in a /30 that is assigned to Google by XO. network:Class-Name:network network:ID:NET-XO-NET-d1302a54 network:Auth-Area:209.48.0.0/15 network:Network-Name:XO-NET-d1302a54 network:Organization;I:GOOGLE INC. (328874-1) network:IP-Network:209.48.42.84/30 network:Admin-Contact;I:XCIA-ARIN network:Tech-Contact;I:XCIA-ARIN network:Created:20120917 network:Updated:20121018 network:Updated-By:ipad...@eng.xo.com -Grant On Wed, Mar 6, 2013 at 8:25 PM, Min qiu.mi...@gmail.com wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms
Re: Time Warner Cable YouTube throttling
yes, i'm use wireless at home. On Wed, Mar 6, 2013 at 10:03 PM, Derek Ivey de...@derekivey.com wrote: Why are your response times so high at your first hop? Are you maxing out your connection or connected to your router over wireless? Derek On 3/6/2013 9:58 PM, Min wrote: I use FIOS. Here is my result: HostLoss% Snt Last Avg Best Wrst StDev 1. Wireless_Broadband_Router.home0.0% 165 285.1 563.9 68.2 2007. 376.1 2. L100.WASHDC-VFTTP-127.verizon-gn 0.0% 165 299.8 560.3 59.1 2021. 384.4 3. G0-9-4-1.WASHDC-LCR-22.verizon-g 0.6% 165 241.3 698.7 64.6 24918 1938. 4. so-14-0-0-0.RES-BB-RTR1.verizon- 0.0% 165 217.2 705.7 100.6 24817 1926. 5. 0.xe-4-1-0.XL4.IAD8.ALTER.NET 0.0% 165 308.0 714.6 109.8 24717 1920. 6. TenGigE0-7-2-0.GW7.IAD8.ALTER.NE 0.0% 165 265.3 722.6 103.5 24617 1911. TenGigE0-7-0-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-1.GW7.IAD8.ALTER.NET TenGigE0-7-1-0.GW7.IAD8.ALTER.NET TenGigE0-7-4-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-0.GW7.IAD8.ALTER.NET 7. google-gw.customer.alter.net 59.4% 165 281.3 982.9 162.3 24516 2940. 8. 216.239.46.2480.6% 164 247.3 726.7 112.2 24416 1903. 9. 72.14.238.173 0.0% 164 203.1 729.7 85.9 24315 1895. 10. iad23s05-in-f6.1e100.net 0.6% 164 343.2 712.9 35.1 24215 1890. In my case, I suspected two things. 1. congestion (verizon over subscribed) 2. packet out of order (high packet drops in alternet-google could be a symptom of multipath) Not sure which has bigger performance impact to youtube. Min On Wed, Mar 6, 2013 at 9:35 PM, Grant Ridder shortdudey...@gmail.com wrote: The 1st one gets slow at XO and the 2nd and 3rd get slow at Sprint. Now the interesting one with XO is that it is routed in a /30 that is assigned to Google by XO. network:Class-Name:network network:ID:NET-XO-NET-d1302a54 network:Auth-Area:209.48.0.0/15 network:Network-Name:XO-NET-d1302a54 network:Organization;I:GOOGLE INC. (328874-1) network:IP-Network:209.48.42.84/30 network:Admin-Contact;I:XCIA-ARIN network:Tech-Contact;I:XCIA-ARIN network:Created:20120917 network:Updated:20121018 network:Updated-By:ipad...@eng.xo.com -Grant On Wed, Mar 6, 2013 at 8:25 PM, Min qiu.mi...@gmail.com wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to
Re: Time Warner Cable YouTube throttling
That looks like your problem right there. Have you tried connecting via ethernet instead and seeing how Youtube performs? On 3/6/2013 10:09 PM, Min wrote: yes, i'm use wireless at home. On Wed, Mar 6, 2013 at 10:03 PM, Derek Ivey de...@derekivey.com wrote: Why are your response times so high at your first hop? Are you maxing out your connection or connected to your router over wireless? Derek On 3/6/2013 9:58 PM, Min wrote: I use FIOS. Here is my result: HostLoss% Snt Last Avg Best Wrst StDev 1. Wireless_Broadband_Router.home0.0% 165 285.1 563.9 68.2 2007. 376.1 2. L100.WASHDC-VFTTP-127.verizon-gn 0.0% 165 299.8 560.3 59.1 2021. 384.4 3. G0-9-4-1.WASHDC-LCR-22.verizon-g 0.6% 165 241.3 698.7 64.6 24918 1938. 4. so-14-0-0-0.RES-BB-RTR1.verizon- 0.0% 165 217.2 705.7 100.6 24817 1926. 5. 0.xe-4-1-0.XL4.IAD8.ALTER.NET 0.0% 165 308.0 714.6 109.8 24717 1920. 6. TenGigE0-7-2-0.GW7.IAD8.ALTER.NE 0.0% 165 265.3 722.6 103.5 24617 1911. TenGigE0-7-0-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-1.GW7.IAD8.ALTER.NET TenGigE0-7-1-0.GW7.IAD8.ALTER.NET TenGigE0-7-4-0.GW7.IAD8.ALTER.NET TenGigE0-5-0-0.GW7.IAD8.ALTER.NET 7. google-gw.customer.alter.net 59.4% 165 281.3 982.9 162.3 24516 2940. 8. 216.239.46.2480.6% 164 247.3 726.7 112.2 24416 1903. 9. 72.14.238.173 0.0% 164 203.1 729.7 85.9 24315 1895. 10. iad23s05-in-f6.1e100.net 0.6% 164 343.2 712.9 35.1 24215 1890. In my case, I suspected two things. 1. congestion (verizon over subscribed) 2. packet out of order (high packet drops in alternet-google could be a symptom of multipath) Not sure which has bigger performance impact to youtube. Min On Wed, Mar 6, 2013 at 9:35 PM, Grant Ridder shortdudey...@gmail.com wrote: The 1st one gets slow at XO and the 2nd and 3rd get slow at Sprint. Now the interesting one with XO is that it is routed in a /30 that is assigned to Google by XO. network:Class-Name:network network:ID:NET-XO-NET-d1302a54 network:Auth-Area:209.48.0.0/15 network:Network-Name:XO-NET-d1302a54 network:Organization;I:GOOGLE INC. (328874-1) network:IP-Network:209.48.42.84/30 network:Admin-Contact;I:XCIA-ARIN network:Tech-Contact;I:XCIA-ARIN network:Created:20120917 network:Updated:20121018 network:Updated-By:ipad...@eng.xo.com -Grant On Wed, Mar 6, 2013 at 8:25 PM, Min qiu.mi...@gmail.com wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6):
Re: Time Warner Cable YouTube throttling
I've been seeing the same thing and was thinking it was me. Just to add to some of the results here... Verizon FIOS 132 ms 3 ms 5 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 233 ms 6 ms 7 ms g0-3-3-7.cmdnnj-lcr-22.verizon-gni.net [130.81.183.186] 322 ms22 ms21 ms xe-4-1-8-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.84] 422 ms21 ms21 ms 0.so-0-0-0.xt2.nyc4.alter.net [152.63.17.21] 558 ms24 ms24 ms tengige0-5-4-0.gw8.nyc4.alter.net [152.63.18.206] 6 * 76 ms76 ms google-gw.customer.alter.net [152.179.72.62] 725 ms21 ms24 ms 209.85.255.68 821 ms34 ms34 ms 209.85.252.242 930 ms28 ms31 ms 209.85.249.11 1031 ms29 ms29 ms 72.14.236.149 1138 ms36 ms36 ms 72.14.238.173 1231 ms29 ms31 ms iad23s05-in-f8.1e100.net [74.125.228.8] Comcast 133 ms15 ms25 ms 68.38.220.1 2 8 ms10 ms15 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 310 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 414 ms15 ms15 ms pos-3-6-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.92.161] 515 ms13 ms14 ms pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.26] 6 * 23 ms25 ms 75.149.231.62 717 ms15 ms14 ms 209.85.252.46 817 ms16 ms15 ms 72.14.238.173 917 ms15 ms16 ms iad23s05-in-f8.1e100.net [74.125.228.8] Our datacenter 11 ms1 ms1 ms static.razorinc.net [70.34.208.101] 21 ms1 ms1 ms 70.34.251.9 31 ms1 ms1 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
Re: Time Warner Cable YouTube throttling
On Mar 6, 2013, at 10:30 PM, Robert M. Enger en...@enger.us wrote: 1) You can use wireshark or other monitor to determine the IP address that your video stream is originating from. I just used the Developer Tools in Google Chrome to figure this out. 2) Upstream traceroutes to that address are probably not of that much interest. The downstream path (carrying the video from the server to your house) can follow a different path. Downstream traceroute is what is needed. Good point. 3) Before pointing fingers at anyone, you need to get your own house (literally) in order. Get off wifi, that is just muddying the water. Shutdown wifi so there are no other users. Get off MocA. You need to be all hard-wired and totally error free and reliable in your local LAN before you can cast stones at carriers and/or inter-carrier interconnection Agreed. My trace routes were straight from my pfsense firewall, which is connected to my ONT via ethernet (I specifically asked Verizon to turn the ethernet port on instead of MoCA when I had it setup over 2 years ago). Derek
Re: Time Warner Cable YouTube throttling
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 j...@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 132 ms 3 ms 5 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 233 ms 6 ms 7 ms g0-3-3-7.cmdnnj-lcr-22.verizon-gni.net [130.81.183.186] 322 ms22 ms21 ms xe-4-1-8-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.84] 422 ms21 ms21 ms 0.so-0-0-0.xt2.nyc4.alter.net [152.63.17.21] 558 ms24 ms24 ms tengige0-5-4-0.gw8.nyc4.alter.net [152.63.18.206] 6 * 76 ms76 ms google-gw.customer.alter.net [152.179.72.62] 725 ms21 ms24 ms 209.85.255.68 821 ms34 ms34 ms 209.85.252.242 930 ms28 ms31 ms 209.85.249.11 1031 ms29 ms29 ms 72.14.236.149 1138 ms36 ms36 ms 72.14.238.173 1231 ms29 ms31 ms iad23s05-in-f8.1e100.net [74.125.228.8] Comcast 133 ms15 ms25 ms 68.38.220.1 2 8 ms10 ms15 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 310 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 414 ms15 ms15 ms pos-3-6-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.92.161] 515 ms13 ms14 ms pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.26] 6 * 23 ms25 ms 75.149.231.62 717 ms15 ms14 ms 209.85.252.46 817 ms16 ms15 ms 72.14.238.173 917 ms15 ms16 ms iad23s05-in-f8.1e100.net [74.125.228.8] Our datacenter 11 ms1 ms1 ms static.razorinc.net [70.34.208.101] 21 ms1 ms1 ms 70.34.251.9 31 ms1 ms1 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
Re: Time Warner Cable YouTube throttling
1) You can use wireshark or other monitor to determine the IP address that your video stream is originating from. 2) Upstream traceroutes to that address are probably not of that much interest. The downstream path (carrying the video from the server to your house) can follow a different path. Downstream traceroute is what is needed. 3) Before pointing fingers at anyone, you need to get your own house (literally) in order. Get off wifi, that is just muddying the water. Shutdown wifi so there are no other users. Get off MocA. You need to be all hard-wired and totally error free and reliable in your local LAN before you can cast stones at carriers and/or inter-carrier interconnection 4) Run some speed-tests to COMPETENT speed test servers (not just the VZ, Time-warner or other in-house speed-test server, but COMPETENT 3rd-party servers). Run those tests during middle-of the night (idle) as well as evening (peak-use) periods. Compare the results. Make sure your ISP last-mile network isn't collapsing under evening (peak hour) load. After all is said and done, you probably still can't do anything except complain to Google. Without the downstream traceroute, you can't really point fingers at a carrier or interconnect. So far as I am aware, google/youtube does not provide a looking-glass or downstream traceroute from any of its (numerous) server sites. So Google staff would have to run the tests. They would have to be adequately staffed to provide that level of investigation and remediation. Google management would have to get involved. How is the consumer ever going to enjoy OTT video with image fidelity suitable for large-screen, lean-back viewing (HD cable-TV quality, if not Bluray quality), if even moderate-rate data flows cannot be sustained into the home when the flow crosses multiple providers? Cable/Satellite, networks, studios will continue to have monopoly on high fidelity lean-back viewing until such time as we can deliver high rates from a remote source into the home. *Clearly FTTH last-mile is not in itself sufficient to guarantee success.* The carriers have to bury the hatchet and start playing nice with one another. As long as they try to gouge money out of both direct customer (receiver) as well as the content provider (sender), this problem will likely not be resolved. Given the big bucks involved, it seems likely that the issue will persist in perpetuity. Regulators and legislators won't act. Their allegiance is not to the citizen consumer.
RE: Time Warner Cable YouTube throttling
Yup... This might be more helpful. I went to r19.sn-p5qlsm7d.c.youtube.com for better comparison. Verizon FIOS 1 8 ms 4 ms 4 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 2 9 ms 6 ms 7 ms g0-3-3-6.cmdnnj-lcr-22.verizon-gni.net [130.81.182.44] 310 ms 9 ms 9 ms xe-9-1-2-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.144] 4 8 ms 8 ms 9 ms 0.xe-3-1-0.br3.nyc4.alter.net [152.63.26.117] 523 ms24 ms24 ms 204.255.168.118 633 ms34 ms34 ms 144.232.4.93 722 ms22 ms22 ms sl-crs4-nyc-0-3-5-0.sprintlink.net [144.232.7.122] 825 ms22 ms24 ms sl-crs2-dc-0-4-0-2.sprintlink.net [144.232.8.164] 922 ms21 ms22 ms sl-st31-ash-0-2-0-0.sprintlink.net [144.232.25.15] 1050 ms49 ms49 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 1120 ms19 ms19 ms 208.117.251.184 Comcast 127 ms31 ms21 ms 68.38.220.1 2 8 ms 9 ms11 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 311 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 415 ms16 ms15 ms pos-4-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.93.233] 514 ms14 ms13 ms be-27-pe06.ashburn.va.ibone.comcast.net [68.86.82.174] 615 ms13 ms14 ms 144.232.6.97 715 ms14 ms15 ms sl-st31-ash-0-4-0-3.sprintlink.net [144.232.3.169] 834 ms32 ms31 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 930 ms31 ms31 ms 208.117.251.184 Our DC 11 ms1 ms1 ms static.razorinc.net [70.34.208.101] 21 ms1 ms1 ms mx1.razorinc.net [70.34.252.9] 31 ms1 ms1 ms xe-0-2-0.phi10.ip4.tinet.net [199.168.63.233] 4 3 ms 8 ms 3 ms xe-7-2-1.was14.ip4.tinet.net [89.149.181.174] 5 3 ms 3 ms 3 ms as2828.ip4.tinet.net [77.67.68.14] 6 3 ms 3 ms 3 ms 216.156.8.189.ptr.us.xo.net [216.156.8.189] 7 4 ms 4 ms 4 ms 209.48.42.86 8 4 ms 4 ms 4 ms 208.117.251.184 John
Re: Time Warner Cable YouTube throttling
I know only too well that Verizon's peering with Cogent in the DC/IAD area is beyond saturated. Looking at the traceroute you have below it would appear to be the same problem: 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms A handoff between Verizon and Sprint shouldn't incude a 100ms delay. Andy Andrew Fried andrew.fr...@gmail.com On 3/6/13 9:25 PM, Min wrote: 3 traces all indicated the last hub are 80~100ms faster than the second last hub. Interesting. Min On Wed, Mar 6, 2013 at 9:07 PM, Derek Ivey de...@derekivey.com wrote: I just got home and tested with quite a few 1080p videos. No issues over my Hurricane Electric IPv6 tunnel. I did notice frequent stops to buffer on my FiOS IPv4 connection. I have a 50 Mbps down connection and don't even come close to maxing it when watching Youtube videos. Here are a few traceroutes: [2.1-BETA0][root@pfsense]/root(1): traceroute r19---sn-p5qlsm7d.c.youtube.com traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.222 ms 1.348 ms 0.834 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.839 ms 2.589 ms 2.443 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.880 ms 14.614 ms 14.698 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.647 ms 14.696 ms 14.552 ms 5 0.xe-3-1-1.BR1.IAD8.ALTER.NET (152.63.37.141) 15.027 ms 15.004 ms 15.064 ms 6 te9-2-0d0.cir1.ashburn-va.us.xo.net (206.111.0.201) 38.517 ms 36.033 ms 34.816 ms 7 216.156.8.189.ptr.us.xo.net (216.156.8.189) 31.958 ms 30.994 ms 29.194 ms 8 209.48.42.86 (209.48.42.86) 124.931 ms 126.117 ms 124.303 ms 9 208.117.251.184 (208.117.251.184) 26.483 ms 27.792 ms 27.974 ms [2.1-BETA0][root@pfsense]/root(2): traceroute r15---sn-p5qlsm76.c.youtube.com traceroute to r15.sn-p5qlsm76.c.youtube.com (208.117.251.148), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.077 ms 0.863 ms 0.968 ms 2 G10-0-8-112.HRBGPA-LCR-01.verizon-gni.net (130.81.184.148) 2.429 ms 2.265 ms 2.456 ms 3 P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185) 14.788 ms 14.666 ms 14.643 ms 4 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.591 ms 14.479 ms 16.041 ms 5 0.xe-10-0-0.BR2.IAD8.ALTER.NET (152.63.38.165) 15.007 ms 15.109 ms 14.975 ms 6 144.232.8.209 (144.232.8.209) 187.038 ms 115.363 ms 117.669 ms 7 sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.263 ms sl-st31-ash-0-8-0-2.sprintlink.net (144.232.1.19) 116.491 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 116.934 ms 8 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 122.521 ms 122.780 ms 121.535 ms 9 208.117.251.148 (208.117.251.148) 33.669 ms 37.652 ms 38.478 ms [2.1-BETA0][root@pfsense]/root(6): traceroute r10---sn-p5qlsm7l.c.youtube.com traceroute to r10.sn-p5qlsm7l.c.youtube.com (208.117.251.47), 64 hops max, 40 byte packets 1 L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1) 1.159 ms 0.831 ms 0.806 ms 2 G9-0-4-212.HRBGPA-LCR-02.verizon-gni.net (130.81.139.126) 2.396 ms 2.435 ms 2.167 ms 3 so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254) 14.497 ms 14.767 ms 14.695 ms 4 0.xe-11-0-0.BR2.IAD8.ALTER.NET (152.63.38.169) 15.001 ms 15.074 ms 15.024 ms 5 144.232.8.209 (144.232.8.209) 118.582 ms 116.717 ms 113.669 ms 6 sl-st31-ash-0-4-0-3.sprintlink.net (144.232.3.169) 114.433 ms 117.698 ms sl-st31-ash-0-4-0-0.sprintlink.net (144.232.28.6) 115.981 ms 7 sl-googl10-584821-0.sprintlink.net (144.228.205.34) 123.912 ms 124.402 ms 125.384 ms 8 208.117.251.47 (208.117.251.47) 30.591 ms 30.676 ms 29.528 ms Derek On 3/6/2013 8:31 PM, Grant Ridder wrote: Can any one provide traceroutes to youtube to see if there is any correlation between last mile providers? -Grant On Wed, Mar 6, 2013 at 6:37 PM, Derek Ivey de...@derekivey.com mailto:de...@derekivey.com wrote: I don't think it's just Time Warner. Definitely looks like XO. I have Verizon FiOS and it was pretty bad for me as well (not sure if it still is since I'm not home right now). There's also atleast two threads in the Verizon FiOS section on Broadband Reports: http://www.dslreports.com/forum/r28027601-Horrible-youtube-speeds http://www.dslreports.com/forum/r28071070-How-to-Reddit-YouTube-firewall-rule-with-MI424wr Derek On Wed, Mar 6, 2013 at 5:56 PM, Rick Coloccia coloc...@geneseo.edu mailto:coloc...@geneseo.edu wrote: I'd like to help, too, I'm from a TWC business class site with 650 Mbps bandwidth and still regularly poor performance with YouTube. -Rick Sent from my iPhone 4S On Mar 6, 2013, at 4:10 PM, Christopher Morrow
RE: Time Warner Cable YouTube throttling
Jumping into the bandwagon here to help out. Here's the result from RIT to r19.sn-p5qlsm7d.c.youtube.com, going through at least 4 hops through XO territory. traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 30 hops max, 60 byte packets 1 rit-west1-gw-014-vlan453.rit.edu (129.21.153.254) 0.593 ms 0.584 ms 0.576 ms 2 rit-core1-pp-west2-vlan824.rit.edu (129.21.8.93) 1.938 ms 1.941 ms 2.116 ms 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 -MJ -Original Message- From: John Zettlemoyer [mailto:j...@razorservers.com] Sent: Wednesday, March 06, 2013 11:19 PM To: 'Derek Ivey' Cc: nanog@nanog.org Subject: RE: Time Warner Cable YouTube throttling Yup... This might be more helpful. I went to r19.sn-p5qlsm7d.c.youtube.com for better comparison. Verizon FIOS 1 8 ms 4 ms 4 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 2 9 ms 6 ms 7 ms g0-3-3-6.cmdnnj-lcr-22.verizon-gni.net [130.81.182.44] 310 ms 9 ms 9 ms xe-9-1-2-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.144] 4 8 ms 8 ms 9 ms 0.xe-3-1-0.br3.nyc4.alter.net [152.63.26.117] 523 ms24 ms24 ms 204.255.168.118 633 ms34 ms34 ms 144.232.4.93 722 ms22 ms22 ms sl-crs4-nyc-0-3-5-0.sprintlink.net [144.232.7.122] 825 ms22 ms24 ms sl-crs2-dc-0-4-0-2.sprintlink.net [144.232.8.164] 922 ms21 ms22 ms sl-st31-ash-0-2-0-0.sprintlink.net [144.232.25.15] 1050 ms49 ms49 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 1120 ms19 ms19 ms 208.117.251.184 Comcast 127 ms31 ms21 ms 68.38.220.1 2 8 ms 9 ms11 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 311 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 415 ms16 ms15 ms pos-4-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.93.233] 514 ms14 ms13 ms be-27-pe06.ashburn.va.ibone.comcast.net [68.86.82.174] 615 ms13 ms14 ms 144.232.6.97 715 ms14 ms15 ms sl-st31-ash-0-4-0-3.sprintlink.net [144.232.3.169] 834 ms32 ms31 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 930 ms31 ms31 ms 208.117.251.184 Our DC 11 ms1 ms1 ms static.razorinc.net [70.34.208.101] 21 ms1 ms1 ms mx1.razorinc.net [70.34.252.9] 31 ms1 ms1 ms xe-0-2-0.phi10.ip4.tinet.net [199.168.63.233] 4 3 ms 8 ms 3 ms xe-7-2-1.was14.ip4.tinet.net [89.149.181.174] 5 3 ms 3 ms 3 ms as2828.ip4.tinet.net [77.67.68.14] 6 3 ms 3 ms 3 ms 216.156.8.189.ptr.us.xo.net [216.156.8.189] 7 4 ms 4 ms 4 ms 209.48.42.86 8 4 ms 4 ms 4 ms 208.117.251.184 John smime.p7s Description: S/MIME cryptographic signature
Re: Time Warner Cable YouTube throttling
RIT is probably on a commercial circuit and from what i have seen on this chain so far, it is only affecting home/consumer users. At MSOE (msoe.edu) i dont show any latency but we are on TWTC. Anyone chime in if that is wrong. -Grant On Wed, Mar 6, 2013 at 10:46 PM, Mark Jeremy mej...@rit.edu wrote: Jumping into the bandwagon here to help out. Here's the result from RIT to r19.sn-p5qlsm7d.c.youtube.com, going through at least 4 hops through XO territory. traceroute to r19.sn-p5qlsm7d.c.youtube.com (208.117.251.184), 30 hops max, 60 byte packets 1 rit-west1-gw-014-vlan453.rit.edu (129.21.153.254) 0.593 ms 0.584 ms 0.576 ms 2 rit-core1-pp-west2-vlan824.rit.edu (129.21.8.93) 1.938 ms 1.941 ms 2.116 ms 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 -MJ -Original Message- From: John Zettlemoyer [mailto:j...@razorservers.com] Sent: Wednesday, March 06, 2013 11:19 PM To: 'Derek Ivey' Cc: nanog@nanog.org Subject: RE: Time Warner Cable YouTube throttling Yup... This might be more helpful. I went to r19.sn-p5qlsm7d.c.youtube.com for better comparison. Verizon FIOS 1 8 ms 4 ms 4 ms l100.cmdnnj-vfttp-27.verizon-gni.net [98.110.113.1] 2 9 ms 6 ms 7 ms g0-3-3-6.cmdnnj-lcr-22.verizon-gni.net [130.81.182.44] 310 ms 9 ms 9 ms xe-9-1-2-0.ny5030-bb-rtr2.verizon-gni.net [130.81.209.144] 4 8 ms 8 ms 9 ms 0.xe-3-1-0.br3.nyc4.alter.net [152.63.26.117] 523 ms24 ms24 ms 204.255.168.118 633 ms34 ms34 ms 144.232.4.93 722 ms22 ms22 ms sl-crs4-nyc-0-3-5-0.sprintlink.net [144.232.7.122] 825 ms22 ms24 ms sl-crs2-dc-0-4-0-2.sprintlink.net [144.232.8.164] 922 ms21 ms22 ms sl-st31-ash-0-2-0-0.sprintlink.net [144.232.25.15] 1050 ms49 ms49 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 1120 ms19 ms19 ms 208.117.251.184 Comcast 127 ms31 ms21 ms 68.38.220.1 2 8 ms 9 ms11 ms xe-11-3-0-0-sur01.burlington.nj.panjde.comcast.net [68.85.128.237] 311 ms 9 ms 9 ms xe-13-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.62.89] 415 ms16 ms15 ms pos-4-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.93.233] 514 ms14 ms13 ms be-27-pe06.ashburn.va.ibone.comcast.net [68.86.82.174] 615 ms13 ms14 ms 144.232.6.97 715 ms14 ms15 ms sl-st31-ash-0-4-0-3.sprintlink.net [144.232.3.169] 834 ms32 ms31 ms sl-googl10-584821-0.sprintlink.net [144.228.205.34] 930 ms31 ms31 ms 208.117.251.184 Our DC 11 ms1 ms1 ms static.razorinc.net [70.34.208.101] 21 ms1 ms1 ms mx1.razorinc.net [70.34.252.9] 31 ms1 ms1 ms xe-0-2-0.phi10.ip4.tinet.net [199.168.63.233] 4 3 ms 8 ms 3 ms xe-7-2-1.was14.ip4.tinet.net [89.149.181.174] 5 3 ms 3 ms 3 ms as2828.ip4.tinet.net [77.67.68.14] 6 3 ms 3 ms 3 ms 216.156.8.189.ptr.us.xo.net[216.156.8.189] 7 4 ms 4 ms 4 ms 209.48.42.86 8 4 ms 4 ms 4 ms 208.117.251.184 John
