Contributor
•
3 Messages
U-verse Latency Issue
Here is a few trace routes that I ran this morning. This was from a desktop computer connected directly to the modem. I have the NVG510. The wireless network was turned off and there was no other traffic on the connection other then the trace route. Any idea why i'm seeing such high latency to the first hop? I've check this other times and if it picks a different route there is no latency issues. Is there anything I can check on my end for this? It's causing issues for gaming. Thanks.
Tracing route to google.com [173.194.219.139] over a maximum of 5 hops: 1 <1 ms <1 ms <1 ms dsldevice.att.net [192.168.1.254] 2 1073 ms 1151 ms 1149 ms 108-243-24-2.lightspeed.tukrga.sbcglobal.net [108.243.24.2] 3 22 ms 20 ms 21 ms 76.201.208.226 4 23 ms 23 ms 23 ms 12.83.82.165 5 20 ms 20 ms 20 ms 12.122.29.205 Trace complete. Tracing route to google.com [74.125.196.102] over a maximum of 10 hops: 1 <1 ms <1 ms <1 ms dsldevice.att.net [192.168.1.254] 2 1126 ms 1133 ms 1137 ms 108-243-24-2.lightspeed.tukrga.sbcglobal.net [108.243.24.2] 3 20 ms 20 ms 20 ms 76.201.208.226 4 21 ms 24 ms 23 ms 12.83.82.161 5 77 ms 60 ms 90 ms 12.122.29.205 6 20 ms 20 ms 20 ms 12.252.63.10 7 21 ms 20 ms 21 ms 72.14.239.100 8 22 ms 21 ms 24 ms 66.249.94.24 9 21 ms 20 ms 21 ms 209.85.243.254 10 * * * Request timed out. Trace complete. Tracing route to google.com [173.194.46.99] over a maximum of 10 hops: 1 <1 ms <1 ms <1 ms dsldevice.att.net [192.168.1.254] 2 1195 ms 1139 ms 1138 ms 108-243-24-2.lightspeed.tukrga.sbcglobal.net [108.243.24.2] 3 21 ms 22 ms 20 ms 76.201.208.226 4 23 ms 71 ms 23 ms 12.83.82.161 5 45 ms 55 ms 29 ms 12.122.29.205 6 114 ms 119 ms 121 ms 12.252.63.10 7 545 ms 618 ms 762 ms 64.233.174.2 8 246 ms 273 ms 284 ms 209.85.142.140 9 57 ms 44 ms 363 ms 209.85.142.201 10 44 ms 109 ms 60 ms 216.239.50.237 Trace complete.
JefferMC
ACE - Expert
•
36K Messages
9 years ago
The latency to the first hop is because AT&T sets an extremely low priority in generating error responses to the expired-TTL ICMP messages that traceroute uses to map the network. Thus, by the time the first hop router receives the packet, recognizes the error, queues the packet for error processing, picks up the packet off the error queue, and finally responds, it has taken quite a few microseconds. Quite often it takes longer than the 2000 ms timeout and no response is received at all.
This is not indicative of any problem. It is not causing your gaming issues. There may be other latency problems actually causing gaming issues, but the tracert response of the first hop router is not.
0
0
kgrover79
Contributor
•
3 Messages
9 years ago
Ok, Thanks for the information on that. Do you have any other trouble shooting steps or any other information I can collect when I am having high latency issues?
I had no issues with my DSL connection and latency, but since I swtiched to U-verse I have had problems randomly with my latency.
0
0
JefferMC
ACE - Expert
•
36K Messages
9 years ago
The latency number that matters is your latency to the server(s) you're communicating with. You might want to do a "ping -t whatevertheservernameis" while you game and see what kind of numbers you're getting.
If you have control over your server, pick one physically close to you as that will lower latency. Latency issues can be caused by line errors. Have you checked the broadband statistics page of your NVG 510 at http://192.168.1.254 ?
0
0
mibrnsurg
Expert
•
20.4K Messages
9 years ago
Not so sure about this as my lightspeed jump is always about 22ms on tracets here, from the RG to the VRAD. Think the OP is having problems between the RG and VRAD causing his high times on this same jump.
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
0
0
JefferMC
ACE - Expert
•
36K Messages
9 years ago
My first hop is also low. Most U-verse users see this as a "no response asterisk" in the next two hops instead of this one. However, the fact remains that if there was an actual latency issue across his first hop, then it would also be included in the time that it takes at every subsequent hop. Since this is not demonstrated, it may be excluded (just as the asterisks in the second and third hop may be discounted if further hops respond).
This should be verifable by direct PING to this hop, assuming it responds.
0
0