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

Youtube sucks for me

Anyone else experiencing crap playback?

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.

Use a proxy to change route.

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.

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.

Where is the best place to find a proxy?

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

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

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).

Re: Youtube sucks for me

delete

Runs fine for me

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.

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.

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

Here is a Traceroute. My wife noticed it maybe a week ago. It happens on pretty much every video site we visit.

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 25 ms 22 ms 24 ms 99-122-108-3.lightspeed.irvnca.sbcglobal.net [99.122.108.3]
3 28 ms 30 ms 30 ms 75.20.0.138
4 * * * Request timed out.
5 * * * Request timed out.
6 27 ms 32 ms 30 ms 12.83.38.133
7 38 ms 75 ms 43 ms 12.123.132.217
8 27 ms 26 ms 26 ms 12.91.217.158
9 26 ms 25 ms 27 ms 209.85.248.185
10 27 ms 26 ms 26 ms 64.233.174.188
11 36 ms 35 ms 35 ms 64.233.174.205
12 35 ms 44 ms 48 ms 209.85.250.65
13 38 ms 35 ms 35 ms 64.233.174.109
14 36 ms 35 ms 36 ms nuq04s08-in-f4.1e100.net [74.125.224.100]

Here is my tracert

Tracing route to youtube.com [173.194.37.128]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 30 ms 20 ms 21 ms 99-10-180-3.lightspeed.wepbfl.sbcglobal.net [99.
10.180.3]
3 44 ms 22 ms 27 ms 99.128.141.36
4 * * * Request timed out.
5 * * * Request timed out.
6 25 ms 25 ms 24 ms 70.159.201.244
7 26 ms 27 ms 26 ms 12.81.20.60
8 26 ms 26 ms 24 ms 12.81.104.2
9 24 ms 30 ms 22 ms 12.81.8.69
10 31 ms 29 ms 29 ms 74.175.192.174
11 35 ms 34 ms 34 ms cr81.fldfl.ip.att.net [12.122.106.94]
12 33 ms 31 ms 31 ms 12.122.155.177
13 33 ms 32 ms 32 ms 12.250.187.10
14 32 ms 30 ms 30 ms 209.85.253.118
15 32 ms 31 ms 31 ms 209.85.241.145
16 32 ms 31 ms 31 ms mia05s18-in-f0.1e100.net [173.194.37.128]

It seems to come and go for me. Depends. I figure it's just that peering between AT&T and YouTube sucks.

I've had Youtube issues on both Comcast and AT&T U-verse. Randomly once and awhile videos would be horribly slow loading and would constantly buffer even on 240p. It's on and off though and doesn't occur too often. So it's not a AT&T specific issue I believe.
Tracing route to youtube-ui.l.google.com [74.125.226.195]
over a maximum of 30 hops:

1 * * * Request timed out.
2 8 ms 9 ms 9 ms ----.-----.ct.-----.comcast.net
3 13 ms 10 ms 11 ms -----.----.ct.---.comcast.net
4 18 ms 15 ms 15 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.69]
5 24 ms 23 ms 23 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.93.185]
6 22 ms 22 ms 20 ms pos-0-0-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.87.122]
7 * * 79 ms 66.208.228.206
8 21 ms 19 ms 19 ms 209.85.248.178
9 20 ms 20 ms 20 ms 72.14.239.250
10 19 ms 20 ms 20 ms lga15s28-in-f3.1e100.net [74.125.226.195]

Trace complete.

Same here. It's been absolutely awful for a few days now. YouTube is unusable.

Edit: here's my traceroute:

Tracing route to youtube.com [173.194.77.93]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 23 ms 24 ms 23 ms 99-xxx-xxx.lightspeed.tulsok.sbcglobal.net [99.xxx.xxx.xxx]
3 31 ms 24 ms 24 ms 75.59.64.6
4 23 ms 23 ms 22 ms 75.59.64.27
5 22 ms 23 ms 22 ms 12.83.46.1
6 32 ms 39 ms 74 ms gar22.dlstx.ip.att.net [12.122.85.65]
7 28 ms 28 ms 27 ms 12.249.185.238
8 29 ms 29 ms 29 ms 72.14.233.67
9 29 ms 29 ms 28 ms 72.14.237.221
10 36 ms 35 ms 35 ms 209.85.243.178
11 36 ms 44 ms 35 ms 216.239.46.63
12 * * * Request timed out.
13 36 ms 35 ms 34 ms ob-in-f93.1e100.net [173.194.77.93]

YouTube has been absolutely unbearable since Friday the 15.

Here's my traceroute to youtube.com:

Tracing route to youtube.com [173.194.43.9]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms gw-condo.domain.home.bivek.net [192.168.1.1]
2 * * * Request timed out.
3 22 ms 22 ms 22 ms 99-104-124-2.lightspeed.sntcca.sbcglobal.net [99
.104.124.2]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 124 ms 166 ms 167 ms 12.83.39.149
8 178 ms 164 ms 141 ms 12.122.114.21
9 75 ms 74 ms * 12.249.231.14
10 25 ms 24 ms 24 ms 209.85.249.5
11 25 ms 24 ms 24 ms 209.85.250.63
12 71 ms 71 ms 71 ms 216.239.46.212
13 74 ms 74 ms 75 ms 72.14.239.48
14 77 ms 71 ms 71 ms 209.85.241.23
15 99 ms 98 ms 98 ms 216.239.46.216
16 98 ms 99 ms 98 ms 72.14.236.209
17 100 ms 102 ms 102 ms 72.14.237.252
18 99 ms 105 ms 100 ms lga15s34-in-f9.1e100.net [173.194.43.9]
--
Bivek Networks, LLC | Atlanta, Chicago, Dallas, Lenoir (NC), New York City, San Jose (CA) | AH.FM Online Radio USA Relays | Snapgr.am Free Image Hosting | FLV2audio.com Youtube-MP3 Converter and more...

As of right now (12:28 am PST) youtube.com works normally. About 11 pm PST it was very slow again. Web browsing is normal, downloading files is same, etc. It is just youtube that is giving the issue. check it out tracert www.youtube.com --

1 1 ms 1 ms 1 ms home [192.168.*.*]
2 26 ms 43 ms 21 ms 75-27-248-2.lightspeed.psdnca.sbcglobal.net [75.
27.248.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 22 ms 22 ms 23 ms 12.83.38.129
7 22 ms 21 ms 22 ms 12.123.132.173
8 23 ms 22 ms 22 ms 12.91.217.158
9 23 ms 24 ms 23 ms 209.85.248.185
10 23 ms 46 ms 66 ms 64.233.174.188
11 57 ms 57 ms 57 ms 64.233.174.143
12 56 ms 57 ms 57 ms 72.14.237.214
13 58 ms 57 ms 57 ms 209.85.250.77
14 56 ms 56 ms 56 ms dfw06s06-in-f5.1e100.net [74.125.227.37]

I can try one when I get home. I'm just afraid that if I do a capture now that too many secretes would be in the file

However yes I experienced it too. Sometimes doing something simple and stupid like reloading the page works! Over the weekend it took me over 5 minutes to watch a clip less than a minute long.

Here is mine.... Youtube is unbearable for me as well. (Columbia, SC)
At the bottom is from work... and it..... works

I am debating calling AT&T and complaining about it but I don't know if this is their problem or not.
My traceroutes SUCK here.... traffic spends forever and a day on the AT&T network.

UVerse:

1 1 ms 1 ms 1 ms 10.1.20.1
2 * * * Request timed out.
3 36 ms 29 ms 28 ms censored.lightspeed.clmasc.sbcglobal.net [x.x.x.x]
4 * * * Request timed out.
5 57 ms 28 ms 28 ms 99.131.77.16
6 * * * Request timed out.
7 28 ms 27 ms 27 ms 72.157.36.250
8 39 ms 39 ms 38 ms 12.81.40.32
9 39 ms 42 ms 38 ms 12.81.40.68
10 45 ms 39 ms 38 ms 12.81.105.75
11 40 ms 38 ms 60 ms 12.81.68.24
12 39 ms 38 ms 38 ms 12.81.104.71
13 41 ms 38 ms 41 ms 12.81.98.50
14 53 ms 39 ms 39 ms ixc00bct-pos-7-0.bellsouth.net [65.83.237.101]
15 40 ms 38 ms 40 ms 12.81.100.0
16 40 ms 42 ms 44 ms 12.81.104.210
17 40 ms 38 ms 39 ms 12.81.56.65
18 38 ms 41 ms 37 ms 65.83.238.186
19 49 ms 47 ms 47 ms cr2.rlgnc.ip.att.net [12.123.152.110]
20 51 ms 51 ms 50 ms cr1.wswdc.ip.att.net [12.122.3.170]
21 49 ms 46 ms 47 ms gar3.ascva.ip.att.net [12.122.113.25]
22 49 ms 70 ms 48 ms 12.250.33.6
23 48 ms 48 ms 49 ms 216.239.46.250
24 50 ms 49 ms 50 ms 72.14.238.253
25 49 ms 49 ms 49 ms iad23s08-in-f0.1e100.net [74.125.228.96]

Work: (where it "works" flawlessly :P)

1 censored (x.x.x.x) 0.870 ms 1.301 ms 1.534 ms
2 also censored (x.x.x.x) 5.821 ms 5.811 ms 6.166 ms
3 x.x.x.x (x.x.x.x) 6.823 ms 6.814 ms 7.163 ms
4 atl2-pr2-xe-0-0-0-0.us.twtelecom.net (66.192.243.146) 12.292 ms 13.116 ms 13.104 ms
5 72.14.213.45 (72.14.213.45) 28.145 ms 28.138 ms 28.539 ms
6 72.14.233.54 (72.14.233.54) 28.522 ms 26.890 ms 72.14.233.56 (72.14.233.56) 26.812 ms
7 66.249.94.24 (66.249.94.24) 27.920 ms 66.249.94.22 (66.249.94.22) 24.580 ms 66.249.94.24 (66.249.94.24) 25.487 ms
8 216.239.48.5 (216.239.48.5) 24.361 ms 24.338 ms 24.734 ms
9 72.14.235.11 (72.14.235.11) 23.072 ms 66.249.95.230 (66.249.95.230) 24.101 ms 24.385 ms
10 72.14.236.153 (72.14.236.153) 22.653 ms 72.14.236.147 (72.14.236.147) 24.047 ms 76.336 ms
11 72.14.238.253 (72.14.238.253) 23.971 ms 24.571 ms 23.906 ms
12 iad23s08-in-f6.1e100.net (74.125.228.102) 24.134 ms 23.444 ms 22.330 ms