US Telco Support > AT&T > AT&T U-verse > Youtube sucks for me

Youtube sucks for me

I've had the issue since 14th of February. Just checked, still having the issue even just using 240 (and who watches youtube in 240 unless you are forced?!). It used to load fine using 720+ now it takes ages to load. Any ideas would be grand. I pinged www.youtube.com and received not sure if this helps.

bytes=32 time=57ms TTL=52
bytes=32 time=56ms TTL=52
bytes=32 time=57ms TTL=52
bytes=32 time=56ms TTL=52

same here. But i'm not sure if its a T problem. I have the same problem using a T1 by another provider/backbone. My problem though is that it doesn't buffer/load until you play and then is jittery.

reply to HelpPlz
Use a proxy to change route.

reply to HelpPlz
I was just about to post something similar. AT&T is definitely up to something regarding their routing to YouTube. I put a VPN on my server in Chicago and there are no lags at all, but as soon as I disconnect from that every video lags. Knock it off AT&T.

reply to HelpPlz
Me too. I can't play youtube at all... buffers endlessly plays 5 sec, buffers 3 minutes, rinse, repeat, etc.

Pingplot shows my 2nd hop 99.65.240.2.lightspeed.irvnca.sbcglobal.net with massive packet loss and average 1.33 seconds rt time.

Do we contact UVerse? or can we pass this along here? I'd just be satisfied knowing that they are aware and working on the problem.

It does affect web browsing some... ads are getting stuck loading, etc.

Netflix hesitates once, then somehow clears and is fine, the same with Vudu. Do they do some kind of auto-reroute within their playback apps?

This started for me on Feb 14 too.

reply to Forosnai
Where is the best place to find a proxy?

reply to HelpPlz
I don't understand how people can watch YouTube videos, but can't use Google for search?
»lifehacker.com/5940565/why-you-s···ur-needs

reply to AdamB
Maybe Google hasn't given into paying AT&T like they have other carriers.

reply to HelpPlz
I'm glad it isn't just us. Maybe they are trying to fix something, or they just hate us (they probably just hate us).

reply to Forosnai

Re: Youtube sucks for me

Runs fine for me

reply to AdamB
Do you know the YouTube streaming severs? I think I need to capture some packets to be certain I have identified the source, but a comparison trace from an AT&T connection would be interesting. I used to see a direct connection between 'sbcglobal.net' routers and YouTube; but I've not been an AT&T customer for a couple of years. I might try and catch a route from a friend's "at&t Yahoo! HSI Basic" connection. YouTube is painful to watch from a 768/384 connection, though (she won't pay more for faster).

Here is my current route from a Sonic.net connection:

Tracing route to nuq04s08-in-f4.1e100.net [74.125.224.100]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms     1 ms  192.168.42.1
  2    26 ms    25 ms    26 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    25 ms    24 ms    25 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    25 ms    24 ms    24 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    25 ms    24 ms    25 ms  0.xe-6-0-0.gw3.equinix-sj.sonic.net [64.142.0.185]
  6    26 ms    25 ms    26 ms  eqixsj-google-gige.google.com [206.223.116.21]
  7    27 ms    27 ms    26 ms  216.239.49.168
  8    27 ms    26 ms    27 ms  64.233.174.109
  9    26 ms    27 ms    26 ms  nuq04s08-in-f4.1e100.net [74.125.224.100]
 
Trace complete.
 

Here's one to that same IP from S. Louisiana:

Tracing route to nuq04s08-in-f4.1e100.net [74.125.224.100]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms     1 ms  homeportal [192.168.1.254]
  2    40 ms    23 ms    23 ms  99-55-68-2.lightspeed.nworla.sbcglobal.net [99.55.68.2]
  3    54 ms    25 ms    26 ms  99.179.205.28
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    25 ms    25 ms    26 ms  70.159.224.138
  7    26 ms    27 ms    27 ms  12.81.24.146
  8    24 ms    24 ms    25 ms  12.81.24.35
  9    25 ms    25 ms    24 ms  74.175.192.46
 10    37 ms    39 ms    40 ms  cr1.nwrla.ip.att.net [12.123.153.18]
 11    39 ms    39 ms    40 ms  cr2.attga.ip.att.net [12.122.18.1]
 12    37 ms    36 ms    36 ms  12.122.140.185
 13    37 ms    37 ms    37 ms  12.91.100.214
 14    38 ms    38 ms    37 ms  64.233.174.2
 15    38 ms    38 ms    38 ms  66.249.94.22
 16    78 ms    79 ms    79 ms  72.14.239.83
 17   113 ms    88 ms    87 ms  64.233.174.205
 18    91 ms   102 ms    91 ms  209.85.250.61
 19    88 ms    88 ms    88 ms  64.233.174.109
 20    88 ms    88 ms    88 ms  nuq04s08-in-f4.1e100.net [74.125.224.100]
 
Trace complete. 
 

A wire shark packet capture might help shine some light on any network issues. If anyone has the time or ability to capture one.

reply to HelpPlz

Tracing route to ord08s09-in-f5.1e100.net [74.125.225.133]
over a maximum of 30 hops:
 
  1     5 ms     3 ms     3 ms  192.168.0.1
  2     3 ms     3 ms     3 ms  home [192.168.1.254]
  3     *        *        *     Request timed out.
  4    27 ms   116 ms    35 ms  71.158.32.66
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    28 ms    26 ms    28 ms  12.83.38.9
  8    34 ms    33 ms    31 ms  ggr3.cgcil.ip.att.net [12.122.133.9]
  9     *        *        *     Request timed out.
 10    35 ms    34 ms    33 ms  209.85.254.128
 11    35 ms    34 ms    35 ms  209.85.240.152
 12    35 ms    33 ms    34 ms  ord08s09-in-f5.1e100.net [74.125.225.133]
 
Trace complete.
 

Here's mine.... not good.
Tracing route to youtube-ui.l.google.com [74.125.227.136]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.20.254]
2 51 ms 22 ms 23 ms 99-115-148-3.lightspeed.cicril.sbcglobal.net [99
.115.148.3]
3 * * * Request timed out.
4 * * 34 ms 71.145.64.70
5 * * * Request timed out.
6 26 ms 23 ms 24 ms 12.83.43.21
7 24 ms 24 ms 23 ms ggr3.cgcil.ip.att.net [12.122.132.9]
8 * * * Request timed out.
9 25 ms 26 ms 24 ms 209.85.254.128
10 26 ms 25 ms 24 ms 72.14.237.130
11 49 ms 49 ms 49 ms 72.14.239.15
12 52 ms 45 ms 46 ms 216.239.47.120
13 46 ms 45 ms 45 ms 72.14.237.216
14 51 ms 49 ms 49 ms 216.239.43.187
15 45 ms 48 ms 49 ms dfw06s17-in-f8.1e100.net [74.125.227.136]

Trace complete.

reply to HelpPlz
Same issue for me. Connected via cable or wifi the videos freeze and are all choppy. I connect to my work VPN and they play without issue. I think this is the final straw that I have been waiting for to change providers.

Edit: Spelling