Traceroute high ms on 7th/8th hop. ISP says it's not their fault.

Toggle sidebar Toggle sidebar
V

veratis26

Oct 19, 2018
4
0
10
I am trying to trace the source of my high ping issues. With a single device hardwired to my router, and with wifi turned off, I am getting a ping between 75-100ms to www.google.com.

My ISP came to diagnose the issue today, and said they had a ping of 35ms to www.google.com so the issue is on my end.

Here is my data from a traceroute, and I'm not sure how to interpret a high latency jump on the 8th hop (since I believe that is too far down the line for it to be my hardware). I did this test with my router broadcasting WiFi and with other devices connected, as I would normally have my network set up.

traceroute to www.google.com (172.217.12.68), 64 hops max, 72 byte packets
1 testwifi.here (192.168.86.1) 3.034 ms 1.469 ms 1.257 ms
2 10.80.214.25 (10.80.214.25) 9.453 ms 9.961 ms 9.771 ms
3 71-46-23-111.res.bhn.net (71.46.23.111) 10.275 ms 19.292 ms 10.333 ms
4 bundle-ether25.tamp05-car2.bhn.net (72.31.117.146) 10.521 ms 11.861 ms 11.505 ms
5 72-31-3-170.net.bhntampa.com (72.31.3.170) 15.584 ms 17.349 ms 18.800 ms
6 bu-14-orld71-car2.bhn.net (71.44.1.215) 18.969 ms 16.067 ms 17.128 ms
7 72-31-188-176.net.bhntampa.com (72.31.188.176) 16.945 ms 14.313 ms 16.094 ms
8 bu-ether44.tustca4200w-bcr00.tbone.rr.com (66.109.6.128) 84.369 ms 94.728 ms 88.081 ms
9 bu-ether18.atlngamq47w-bcr01.tbone.rr.com (66.109.1.72) 92.457 ms 87.330 ms 88.148 ms
10 107.14.19.21 (107.14.19.21) 84.325 ms 83.544 ms 84.818 ms
11 ix-ae-14-0.tcore1.a56-atlanta.as6453.net (64.86.113.37) 81.899 ms 83.505 ms 82.227 ms
12 209.85.173.168 (209.85.173.168) 93.267 ms 94.878 ms 92.769 ms
13 108.170.249.163 (108.170.249.163) 89.090 ms 87.517 ms 88.030 ms
14 209.85.250.96 (209.85.250.96) 87.740 ms 87.446 ms 88.234 ms
15 209.85.249.45 (209.85.249.45) 89.339 ms 85.138 ms 89.388 ms
16 108.170.228.78 (108.170.228.78) 84.476 ms 85.187 ms 85.203 ms
17 108.170.252.161 (108.170.252.161) 86.224 ms 85.744 ms 85.300 ms
18 108.170.226.109 (108.170.226.109) 83.846 ms 84.730 ms 85.814 ms
19 dfw28s05-in-f4.1e100.net (172.217.12.68) 84.523 ms 85.136 ms 86.099 ms

Any thoughts on what my issue might be?

Thank you in advance,
Spencer
 
Sort by date Sort by votes
clarkjd

clarkjd

Splendid
Dec 7, 2005
6,486
34
28,490

IDK why you take 19 hops to get to Google.com. What is your default DNS server?
 
Upvote 0 Downvote
V

veratis26

Oct 19, 2018
4
0
10


I'm not sure how to find that out. To my understanding it is whatever my ISP assigned me. (I apologize, I'm unfamiliar with a lot of these topics). Some googling suggested that using a public DNS could help?
 
Upvote 0 Downvote
failboat

failboat

Splendid
Feb 19, 2010
1,905
51
21,390
DNS would be separate. the IP is already resolved. Should find the ip of the game you are connecting to and check that. You might not get the same hops as to google.

I would suggest looking up the servers geographically and making sure it's not jumping around the world for no reason.
It's odd that it goes from Florida -> Cal. Some hops could be missing. The data is opt-in.
 
Upvote 0 Downvote
V

veratis26

Oct 19, 2018
4
0
10


My default DNS server is now Google: 8.8.8.8 and 8.8.4.4. Still no solution
 
Upvote 0 Downvote
V

veratis26

Oct 19, 2018
4
0
10


I did another tracert to a server in Miami, which is in the same state as me.

traceroute to 173.44.32.10 (173.44.32.10), 64 hops max, 72 byte packets
1 192.168.86.1 (192.168.86.1) 0.762 ms 0.409 ms 0.279 ms
2 10.80.214.25 (10.80.214.25) 7.754 ms 7.956 ms 7.958 ms
3 71-46-21-111.res.bhn.net (71.46.21.111) 10.411 ms 8.443 ms 7.101 ms
4 bundle-ether25.tamp05-car2.bhn.net (72.31.117.146) 8.831 ms 12.359 ms 10.588 ms
5 72-31-3-170.net.bhntampa.com (72.31.3.170) 10.190 ms 12.994 ms 10.945 ms
6 hun0-1-0-5-tamp20-cbr1.bhn.net (72.31.3.97) 11.513 ms 11.488 ms 12.398 ms
7 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96) 84.594 ms 87.165 ms 88.273 ms
8 bu-ether17.hstqtx0209w-bcr00.tbone.rr.com (66.109.1.70) 82.067 ms 87.446 ms 88.423 ms
9 107.14.19.49 (107.14.19.49) 84.777 ms 88.227 ms 79.806 ms
10 0.ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 78.990 ms 79.019 ms 78.019 ms
11 66.109.9.158 (66.109.9.158) 79.721 ms 84.437 ms 77.791 ms
12 94.142.98.37 (94.142.98.37) 111.575 ms 115.298 ms 108.811 ms
13 94.142.120.28 (94.142.120.28) 132.428 ms 129.313 ms 132.194 ms
14 213.140.37.13 (213.140.37.13) 131.073 ms 132.563 ms 132.390 ms
15 213.140.33.164 (213.140.33.164) 132.477 ms 140.720 ms 149.525 ms
16 84.16.8.37 (84.16.8.37) 105.263 ms 106.220 ms 105.612 ms
17 173.44.32.225 (173.44.32.225) 140.482 ms 107.782 ms 100.321 ms
18 unassigned.quadranet.com (173.44.32.254) 104.572 ms * *
19 173.44.32.10 (173.44.32.10) 110.526 ms 106.067 ms 104.491 ms

Same issue hitting the same server path as before.

I had spectrum support come out again and check all of my lines to the pole by the road and everything is fine according to them. When they ping google on their own device, they say they're getting 30ms.

Which led me to believe it is a device problem on my end, but even after swapping my new arris modem out for a new Netgear modem (and performing these test while wired directly to the modem), I am still getting the same issue.
 
Upvote 0 Downvote
failboat

failboat

Splendid
Feb 19, 2010
1,905
51
21,390
If it was on your end everything would be high from the start.

66.109.6.96 looks like it's still in FL and it's really high. You can't say for sure if it's that one, but after the prior one.
Servers can ignore your traceroute so you can't ping each hop since you don't know the ip.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom