• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

[SOLVED] High Ping. Spectrum is my ISP.

Jun 14, 2020
2
0
10
I live in St.Petersburg, Florida and around 4 months ago my ping spiked to 75-100ms and hasn't gone down since. I have no other ISPs in my area to switch to so I really need this to get fixed.

Here is traceroute to Google's public DNS:

f1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]

2 11 ms 10 ms 20 ms 072-031-128-049.res.spectrum.com [72.31.128.49]

3 31 ms 10 ms 10 ms 071-046-023-111.res.spectrum.com [71.46.23.111]

4 13 ms 15 ms 15 ms bundle-ether25.tamp05-car2.bhn.net [72.31.117.146]

5 21 ms 19 ms 17 ms 072-031-003-170.res.spectrum.com [72.31.3.170]

6 23 ms 18 ms 18 ms bu-14-orld71-car2.bhn.net [71.44.1.215]

7 18 ms 15 ms 17 ms 072-031-188-176.res.spectrum.com [72.31.188.176]

8 89 ms 87 ms 87 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]

9 82 ms 86 ms 87 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]

10 85 ms 87 ms 88 ms 209-18-36-61.tbone.rr.com [209.18.36.61]

11 89 ms 85 ms 89 ms 108.170.225.166

12 86 ms 91 ms 86 ms 108.170.225.107

13 86 ms 89 ms 88 ms dns.google [8.8.8.8]

Here is a traceroute to a closer server in Miami, FL:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]

2 10 ms 14 ms 9 ms 072-031-128-049.res.spectrum.com [72.31.128.49]

3 10 ms 13 ms 10 ms 071-046-022-111.res.spectrum.com [71.46.22.111]

4 15 ms 11 ms 11 ms bundle-ether25.tamp05-car2.bhn.net [72.31.117.146]

5 13 ms 15 ms 11 ms 072-031-003-170.res.spectrum.com [72.31.3.170]

6 12 ms 15 ms 12 ms hun0-1-0-5-tamp20-cbr1.bhn.net [72.31.3.97]

7 82 ms 78 ms 79 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66.109.6.96]

8 81 ms 79 ms 87 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com [66.109.1.70]

9 76 ms 75 ms 77 ms ge-3-1-0.cr1.sea20.tbone.rr.com [66.109.6.90]

10 83 ms 76 ms 77 ms 66.109.5.121

11 86 ms 78 ms 79 ms 66.109.9.158

12 107 ms 110 ms 103 ms 94.142.98.35

13 128 ms 125 ms 126 ms 94.142.119.188

14 105 ms 102 ms 106 ms 84.16.8.37

15 * * 108 ms 173.44.32.250

16 107 ms 105 ms 104 ms 173.44.32.10



I was wondering what caused this and if there is any easy way to switch the way spectrum routes me through. I switched my DNS as well and that didn't change anything.

I have tried using a VPN or ExitLag to change my route and it did not help.
 
Last edited:
Solution
You can do nothing about the path data takes and the ISP does care enough about your small monthly fee to reconfigure their network.

The problem is in the handoff between spectrum and a ISP called road runner. Actually they are the same company but a lot of the inter connectivity between is based on historical connections that have not been changed even after all these years since road runner was purchased.

Not sure on the first trace but the second trace if you believe the router dns names appears to go though texas and then Seattle. The first one looks like it is passing through atlanta.

Still these times are very large for traffic within the USA. You should see maybe 40ms to servers in california and many times better...
You can do nothing about the path data takes and the ISP does care enough about your small monthly fee to reconfigure their network.

The problem is in the handoff between spectrum and a ISP called road runner. Actually they are the same company but a lot of the inter connectivity between is based on historical connections that have not been changed even after all these years since road runner was purchased.

Not sure on the first trace but the second trace if you believe the router dns names appears to go though texas and then Seattle. The first one looks like it is passing through atlanta.

Still these times are very large for traffic within the USA. You should see maybe 40ms to servers in california and many times better.

It seems you have found the only things you can actually try. It is a matter of finding a VPN provider that has connectivity to spectrum via some other ISP maybe in tampa. This is a very tedious process because most vpn do not have details on how they connect to their ISP. You generally have to find ones that have a data center near you and then test to see how they connect. If you can get blocks of IP used by the vpn company at the location you can run tracert to see the path between your machine and their data center.
 
Solution
You can do nothing about the path data takes and the ISP does care enough about your small monthly fee to reconfigure their network.

The problem is in the handoff between spectrum and a ISP called road runner. Actually they are the same company but a lot of the inter connectivity between is based on historical connections that have not been changed even after all these years since road runner was purchased.

Not sure on the first trace but the second trace if you believe the router dns names appears to go though texas and then Seattle. The first one looks like it is passing through atlanta.

Still these times are very large for traffic within the USA. You should see maybe 40ms to servers in california and many times better.

It seems you have found the only things you can actually try. It is a matter of finding a VPN provider that has connectivity to spectrum via some other ISP maybe in tampa. This is a very tedious process because most vpn do not have details on how they connect to their ISP. You generally have to find ones that have a data center near you and then test to see how they connect. If you can get blocks of IP used by the vpn company at the location you can run tracert to see the path between your machine and their data center.
OK thank you. I am going to spend some time testing different VPNs to see if anything works.