[SOLVED] High Ping on Every Hop

[Alex_482]

My ping should be 20-30ms on every hop but it is 120-200 on every hop. Restarting the modem fixes the problem for an hour or so but it always comes back. This problem h asbeen creeping in more and more frequently over the past week. Is this an ISP or a hardware issue? I know its not a problem with a specific device as I have tested this ping issue on multiple devices. Not to mention, my VPN is also reporting approximately equalivalent latency that my cmd does. If its a problem with my ISP (AT&T) how can i get them to fix it?

Tracing route to google.com [2607:f8b0:4000:814::200e]
over a maximum of 30 hops:

1 * * * Request timed out.
2 166 ms 154 ms 128 ms 2001:506:6000:11b:71:156:215:66
3 125 ms 135 ms 138 ms 2001:506:6000:1c:69:235:113:146
4 121 ms 146 ms 146 ms 2001:1890:ff:e0f3:12:83:39:145
5 116 ms 113 ms 121 ms 2001:1890:ff:ffff:12:122:119:210
6 143 ms 150 ms 125 ms 2001:1890:c01:a804::11e0:85a1
7 120 ms 129 ms 129 ms 2001:4860:0:1004::e
8 187 ms 192 ms 189 ms 2001:4860::c:4000:f2d3
9 159 ms 157 ms 167 ms 2001:4860::c:4000 207
10 168 ms 176 ms 181 ms 2001:4860::c:4000 611
11 180 ms 178 ms 199 ms 2001:4860::1:0:bf0c
12 160 ms 164 ms 161 ms 2001:4860:0:e03::1
13 187 ms 177 ms 186 ms 2001:4860:0:1::1519
14 161 ms 170 ms 171 ms dfw25s27-in-x0e.1e100.net [2607:f8b0:4000:814::200e]

Trace complete.

C:\Users\Owner>

 

[anotherdrew]

Ping time is cumulative, so this makes sense (ping to hop 3 equals ping to 1 + ping from 1 to 2 + ping from 2 to 3 + the route back). It would be nice to see the first hop (your router). I'm not sure why it's not responding to pings from inside the network (ignoring pings from outside is normal, but not inside). If the ping to your router was high, then the issue is your network. If the ping to your router is fine, but the 2nd hop (which I assume is an AT&T router in some CO on the other side of town) is high, then the issue is probably the phone line. You can also look at the error counts on your router .. this should give you an idea if the phone line is not up to snuff.

Another thought ... what does an IPv4 tracert look like. IPv6 is still not fully supported and that could be an issue.

 

[Alex_482]

IPv4 tracert gets a lot of timed out nodes... this is to google.com.

 

[anotherdrew]

Timeouts are not a problem. A lot of routers on the internet are set to ignore IPv4 ping (which is part ICMP). ICMP is an integral part of IPv6, so routers should not ignore IPv6 ping requests, but then not everyone follows the rules (go figure).

So, the big question still is ... what is the ping (IPv4 and IPv6) time to your first hop. If this is high then you have an issue with your network. If it is fine and the issue starts with the 2nd hop then your ISP (probably) has an issue.

 

[failboat]

From your modem -> your ISP should be fairly low. Something is going on.

To make sure the tests are valid you have to check that you're not swamping your down or up. If you can't see bandwidth usage in your router try testing directly on the modem with resource monitor up in Windows.

Do an ip lookup for some of the early hops to see if they are geographically close to you. a normal one would go from home to isp to a sorta direct route to the destination. if it's going from home to some where very far and back it's not a good sign.