03-18-2012 6:36 AM
I've been having serioius latency problems for the last several days. It appears it is an problem in AT&Ts network:
C:\> tracert google.com
Tracing route to google.com [188.8.131.52]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms home [192.168.1.254]
2 20 ms 20 ms 21 ms 75-25-136-3.lightspeed.plalca.sbcglobal.net [75.
3 * * * Request timed out.
4 * * * Request timed out.
5 20 ms 19 ms 19 ms 184.108.40.206
6 22 ms 22 ms 22 ms 220.127.116.11
7 23 ms 22 ms 23 ms 18.104.22.168
8 28 ms 23 ms 23 ms 22.214.171.124
9 24 ms 23 ms 24 ms 126.96.36.199
10 23 ms 23 ms 23 ms nuq04s07-in-f4.1e100.net [188.8.131.52]
Where do I report this problem?
Solved! Go to Solution.
03-18-2012 8:04 AM
There is no problem with that tracert. You're getting 23ms on ping 10. If you were having a problem you wouldn't be getting anything.
03-18-2012 4:13 PM
Actually the only one you can use for Uverse latency is the lightspeed.plalca.sbcglobal.net figure. That is the connection to the internet and 20ms is average on Uverse and there is no excess routing and everything is in the 20's.
Ignore any request timeouts. the routers were probably set to not accept tracert pings. I usually see the next 2 the same on my tracerts, making a tracert not a great investigative tool.
Please NO SD stretch-o-vision or 480 SD HD Channels
1-800-288-2020, After he gets acct info, press # a bunch of times, get a menu from Mr. Voice recognition
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more
03-22-2012 11:47 AM
@mibrnsurg You're correct, routers on the U-verse Network are basically configured not to reply with "ICMP TTL Time Exceeded Messages" (See: http://en.wikipedia.org/wiki/ICMP_Time_Exceeded); hence the percieved "lanecy issue" on hops 3 and 4.
@oufanindallas Also, another great point that a lot of folks miss. In my opinion, a ping test should be ran first to determine average latency. If it's usually and consistently high, or you're getting dropped pings, a trace route can be ran to determine were the problem is. To get the most accurate results, it's advisable to check this against multiple destinations before assuming there's a issue.
08-20-2013 1:04 PM - edited 08-20-2013 1:07 PM
Just be glad you are not getting 1200 - 1500ms ping times as I'm getting since I started service a year ago but not realize it because I wasn't using it as much. The whole 12mb down uverse is more like 12mb download with tons of errors and horrible ping times to their own node which sits over 100 miles away. I've called and a tech came by said the line is fine from the outside, sure then why does it show that my ping times from your own modem sitting in my house showing seriously high latency times.
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.