Time Warner Cable YouTube throttling

Thu Mar 7 03:09:16 UTC 2013

yes, i'm use wireless at home.

On Wed, Mar 6, 2013 at 10:03 PM, Derek Ivey <derek at 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:
>>
>>   Host                                Loss%   Snt   Last   Avg  Best  Wrst
>> StDev
>>   1. Wireless_Broadband_Router.home    0.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.248                    0.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 <shortdudey123 at 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:ipadmin at eng.xo.com
>>>
>>> -Grant
>>>
>>> On Wed, Mar 6, 2013 at 8:25 PM, Min <qiu.min98 at 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 <derek at 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 at 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 at 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 at 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 <derek at derekivey.com
>>>>>> <mailto:derek at 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
>>>>>>      <coloccia at geneseo.edu <mailto:coloccia at 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.lists at gmail.com <mailto:morrowc.lists at gmail.com>>
>>>>>>      > wrote:
>>>>>>      >
>>>>>>      > > On Wed, Mar 6, 2013 at 3:34 PM, Randy Carpenter
>>>>>>      <rcarpen at network1.net <mailto:rcarpen at network1.net>>
>>>>>>      > wrote:
>>>>>>      > >>
>>>>>>      > >> ----- Original Message -----
>>>>>>      > >>> On Wed, Mar 6, 2013 at 3:11 PM, Randy Carpenter
>>>>>>      > >>> <rcarpen at network1.net <mailto:rcarpen at 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
>>>>>>      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?
>>>>>>      > >
>>>>>>      >
>>>>>>      >
>>>>>>
>>>>>>
>>>
>