Need help with your equipment?
stprovost's profile

Contributor

 • 

2 Messages

Friday, January 2nd, 2015 6:52 AM

Slow speed / 10% packet loss / Uverse 10Mbps

Hi everyone,

 

I've been using DSL for 10 years or so, most of the time with ATT U-verse, and I've been seeing terrible, TERRIBLE speeds over the past week or so. Nothing changed.

 

I tried speedtest on my android phone: I get 20 Mbps Down/10 Mbps Up on LTE, and I get 10 Mbps down (expected) and 0.49 Mbps up (not expected). If I run a continuous ping to 4.2.2.2, I get 10% packet loss (but a ping time of 40-50 ms, which is good).

 

Yes, I rebooted my Uverse gateway/wifi a few times, I made sure there's no other device using my service by turning off everything else, and nobody hacked my password. The packet loss is consistent and very irritating.

 

Hope I can get someone to check my line before I switch to 4G with Tmobile once and for all!

 

Thanks.

Expert

 • 

20.4K Messages

9 years ago

@stprovost Pings are not great for diagnostic as they can be ignored by many servers, just like tracerts are.  Just like your RG can not be pinged normally.

 

If slow speeds are wireless:

 

See SomeJoe's great wireless interference thread:

http://forums.att.com/t5/Features-and-How-To/How-to-Minimize-Wireless-Interference/m-p/2303003#M1138

Also see the SJ post:

Please Read for a Potential Solution

For many people, the DHCP problems with the 2Wire/Pace/Motorola routers can be solved by configuring the RG as follows:

1. Go to http://192.168.1.254/ and find the RG's wireless configuration page.

2. Change the setting "Wi-Fi Protected Setup" to Disabled.

3. Change the setting "Authentication Type" to WPA2-PSK (AES).

4. Click the "Save" button at the bottom.

5. This procedure may ask for your RG's password. The default password for your RG is printed on a sticker on the side of the RG (3600HGV, 3800HGV-B, 3801HGV and NVG589/510) or on a white sticker on the backup battery (i3812V).

Disabling WPS should help with the DHCP timeout issue and general wireless connection problems.

Setting authentication specifically to WPA2-PSK/AES improves connection reliability on Macs and other Apple products.

 

Good luck 😉

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

ACE - Expert

 • 

35K Messages

9 years ago


@stprovost wrote:

...

 

Hope I can get someone to check my line before I switch to 4G with Tmobile once and for all!

 

Thanks.


If you want someone to check your line, you need to click this AT&T logoU-verse Customer Service link to send a Private Message (PM) to the AT&T customer service team to help you resolve your request. You can expect a reply via return PM (the blue envelope envelope  in the upper right hand corner of this site, next to your name and avatar) in a business day or three.

This is a group of U-verse service specialists who are knowledgeable about U-verse and will stay with your problem until the end (instead of forgetting about it when the phone hits the cradle). Speed things up by including your Billing Account Number, and the best time and way to reach you.

Contributor

 • 

2 Messages

9 years ago

Hi,

 

Thanks but I tried those. WPS has never been enabled, I'm using WPA2 and I moved to a channel that is not used by neighboring WiFi's. DHCP is not my problem; it's latency. While ping is not the best tool, it is a good one, and I'm comparing my current bandwidth situation with past ones. When things were fine, ping never dropped and was below 50 ms. This is not the case now. Thanks.

Tutor

 • 

6 Messages

9 years ago

In regards to tracert and ping, while the destination servers will often (for good reason) ignore icmp echo requests, the backbone doesn't and there have been plenty of backbone issues lately. This is just one of many such traces I've run tonight while attempting to enjoy my first day off since New Years eve. It's quite frustrating to know I've done absolutely everything humanly possible to improve my end and there's absolutely no impact on the situation because the backbone itself is falling apart.

 

 

Tracing route to blizzard.com [12.129.242.30]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms dslrouter [192.168.1.254]
2 * 245 ms * 70.159.198.21
3 126 ms 110 ms 138 ms 70.159.216.82
4 146 ms 155 ms 89 ms 12.81.48.56
5 * * * Request timed out.
6 243 ms * * 12.81.38.60
7 * * 120 ms 12.81.24.66
8 133 ms 173 ms 151 ms 12.81.24.95
9 * * 140 ms 74.175.192.50
10 200 ms * 316 ms cr1.nwrla.ip.att.net [12.123.153.18]
11 177 ms * 166 ms cr1.hs1tx.ip.att.net [12.122.1.141]
12 54 ms 49 ms 67 ms cr2.dlstx.ip.att.net [12.122.2.121]
13 236 ms 192 ms 120 ms 12.123.249.221

ACE - Expert

 • 

35K Messages

9 years ago


@demos606 wrote:

In regards to tracert and ping, while the destination servers will often (for good reason) ignore icmp echo requests, the backbone doesn't and there have been plenty of backbone issues lately. ...

 

 


What is this "backbone" you speak of.  There is no single Internet backbone.  Your ping times go south at the very first hop outside your house.  (245ms).  Once you see that, you pretty much quit looking at the hops beyond and try to figure out why your first link has such poor latency.

 

I can think of two likely reasons:

  1. Serious line communication issues
  2. Too much traffic for your bandwidth tier (especially upstream).

Try http://ufix.att.com to see if it can identify communication issues.  Make sure there isn't any P2P or online backup software (or malware) filling up your connection.  Click the link from several posts back to contact AT&T to check your line if needed.

 

I've discounted wireless as a potential issue because your ping time to your RG is fine (<1 ms), but the next hop is a doozy.

 

 

Tutor

 • 

6 Messages

9 years ago

In this case, I'm refering to the AT&T network backbone since the traffic in question doesn't leave the AT&T network according to whois lookups on the addresses provided by this trace.  As for the hops outside the house, I've been in contact with AT&T support dozens of times trying to get these issues fixed to no avail as they're sporadic as evidenced by the following trace from a few moments ago (almost identical network traffic to the previous trace as well, note the wildly difference in the first times outside the house)

 

1 <1 ms <1 ms <1 ms dslrouter [192.168.1.254]
2 9 ms 9 ms 8 ms 70.159.198.21
3 336 ms 97 ms 52 ms 70.159.216.82
4 19 ms 32 ms 20 ms 12.81.48.56
5 * 20 ms 20 ms 12.81.104.237
6 226 ms 25 ms 73 ms 12.81.38.60
7 36 ms 23 ms 23 ms 12.81.24.66
8 567 ms 317 ms 276 ms 12.81.24.95
9 156 ms 26 ms 19 ms 74.175.192.50
10 68 ms * 208 ms cr1.nwrla.ip.att.net [12.123.153.18]
11 37 ms 35 ms 35 ms cr1.hs1tx.ip.att.net [12.122.1.141]
12 37 ms * 55 ms cr2.dlstx.ip.att.net [12.122.2.121]
13 742 ms 269 ms 280 ms 12.123.249.221

 

Honestly, I'm more concerned with the steady timeouts at New Orleans, Houston and Dallas than I am the issues I know the physical lines and relays here in the Mississippi country side have. I've long since accepted that the equipment out here won't get fixed or replaced promptly until it's more profitable to do so than risk losing a few customers to inferior satellite service. If I lived a few more miles further from "town" I wouldn't be able to get dsl at all and it's only been in the last decade or so that dsl has even become available here. For that matter, cable service (and coincidentally, Uverse) still isn't available here.

ACE - Expert

 • 

35K Messages

9 years ago

Reading this last traceroute, you're getting good times as far away as TX:

 

11 37 ms 35 ms 35 ms cr1.hs1tx.ip.att.net [12.122.1.141]
12 37 ms * 55 ms cr2.dlstx.ip.att.net [12.122.2.121]

 

And sporadic bad times all along the route.  Yes, maybe that first tracert was a fluke to have all that latency on the first hop, but... have you checked your line for errors using the RG's own diagnostic pages yet?

 

 

Tutor

 • 

6 Messages

9 years ago

I've used just about every diagnostic tool in existance to eliminate issues from my end. The AT&T tools say there's no issue, tracert always shows Houston, Dallas and/or New Orleans as trouble sites and about as often as not, I'll have something timing out in the 3rd or 4th and 7th or 8th hops. I've been chasing this problem for over 5 years and had techs out several times to replace wiring when something did actually fail - once because the wiring was simply laid on the ground and my neighbor ran it over with a bush hog (I wish I were joking).

ACE - Expert

 • 

35K Messages

9 years ago

Ok.  You just want to vent.  Fine.  I'll quit trying.

 

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.