How to read a tracert?

Question

Hello,

I have been having latency issues since yesterday and I was wondering if it was on my end of the ISP's end. While on command prompt, I did "ping google.com -t" and my results ranged from 50-1000+. 50 ms is usually my regular ping and anything 100+ is bad. Sometimes when I ping google on commandprompt, it goes to a constant 600 ms and I start to lag. I tried tracert google.com but I'm not sure how to read it.


Tracing route to google.com [74.125.224.34]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms home [192.168.1.254]
2 216 ms 192 ms 156 ms adsl-69-225-143-254.dsl.irvnca.pacbell.net [6
25.143.254]
3 223 ms 203 ms 188 ms 12.83.83.9
4 227 ms 93 ms 74 ms 12.123.132.173
5 * * 65 ms 12.91.217.158
6 * * * Request timed out.
7 449 ms 529 ms 621 ms 209.85.252.149
8 1542 ms 1604 ms 1104 ms lax17s01-in-f2.1e100.net [74.125.224.34]


I have tried contacting my ISP, but they have been no help, so I'm wondering if this is on my end or their end.

Answer 1

The problem is definitely on your ISP's end. The 2nd line on your tracert is the connection from your modem/router to your ISP, and the time should only be slightly higher than the time from the previous line.



The time from the first hop (2ms) to the second hop (216ms) is abnormally high. On a good quality connection, you would normally see a few milliseconds added to the time of the first hop.



The problem is going to be getting in touch with a technician or support person who can help you resolve the problem. You can use the ping and tracert statistics to support your claim, and continue to contact them until the issue is fixed.

Answer 2

You have a local issue! When your router, second listing, takes 216ms to respond to your local machine everything down stream from that will be bad!

Try rebooting the router, pull power from it, wait 30 - 60 seconds, reconnect power and wait for the reboot. Check it then. If you still see high response times, replace the router! You might check to see if there are any firmware updates for your router.

The numbers there are simply BAD!

Answer 3

set up multiple ping -t's to each of those addresses in the tracert.



The 2nd hop from your router (192.168.1.254) to your ISP (6.25.143.254?) looks very suspect though.



I can't ping that, or the 12.x.x.x's, or 209.85.252.149



I can ping 69.225.143.254 = 164ms



I can ping 74.125.224.34 = 157ms to 198ms



This is from the UK by the way.





edit: i see the 6.25.143.254 thing was the 69.225.143.254.



Just wondering if that is your WAN IP (your internet public IP of your home router).



If you don't know, you can go to www.whatismyip.com and see.



If is IS your public IP, then the huge time to ping it suggests an issue with your home router.