Before posting a new question, please check out our Internet / WiFi and Spectrum TV App troubleshooting pages for common issues, as well as useful information to include in your post.

Advanced Search Options


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.

Frequently Asked Questions


(Quick links to the current most searched topics)
How can I pause and rewind live TV using the Spectrum TV app?
Spectrum TV App Supported Devices

Higher Latency to Servers

TheDoughtTheDought Posts: 4 Spectator
in Connectivity Jan 04, 2023

Hello,

I have a few hosted VPS servers from google and in the last month my latency has gone from 50ms to 90ms. I've tried resetting everything but the issue comes down to Routing... I'm not sure why this is a constant issue.


Here is a vague example of my routing:

My location in MT -> Town nearby -> Denver, CO -> back up to town nearby -> back to Denver -> then to my server in Iowa.


The other routing goes through Seattle and gives me 80ms since it has to do so much back tracking. There was a time I had a contact that would help me diagnose and at least communicate troubleshooting steps. Not sure what I can do at this point.


Hopefully this can be resolved.

Tagged:

Replies

  • Jaleesa_FJaleesa_F Posts: 35 Moderator
    Jan 05, 2023

    Good morning and welcome to the Community!

    I'm sorry to hear that you're experiencing latency issues with your internet connection, I am happy to look into this for you. Are you wired or wireless? Are you only experiencing latency when hosting VPS servers?

  • TheDoughtTheDought Posts: 4 Spectator
    Jan 05, 2023

    I am wired. These are VPS hosted by Google.


    Let me know what other information would be helpful!


    Thanks!

  • Jaleesa_FJaleesa_F Posts: 35 Moderator
    Jan 05, 2023

    Are you wired to a router? Or directly to your modem? Have you tried testing your speeds? You can do that at speedtest.net.

  • TheDoughtTheDought Posts: 4 Spectator
    Jan 06, 2023

    Wired to a router. I am getting good results on my speed tests, at least within the range I would expect. It's unfortunate that higher speeds don't always mean good latency.


    Wish I could understand the logic behind my routing to servers and why a town nearby can have 30ms latency but I'm getting 80ms. The math doesn't add up to me.


    Appreciate your help so far!

  • William_MWilliam_M Posts: 535 Moderator
    Jan 06, 2023

    Will you please run a traceroute to your server and another such as water.com, and share your results?

  • TheDoughtTheDought Posts: 4 Spectator
    Jan 06, 2023

    Here are 2 Examples. First one is to a server I've had 40-50ms max to for the last 3 years until December.


    Tracing route to 141.213.192.35.bc.googleusercontent.com [35.192.213.141]

    over a maximum of 30 hops:


     1  <1 ms  <1 ms  <1 ms 192.168.1.1

     2   *    *    *   Request timed out.

     3  10 ms  10 ms   9 ms lag-63.hlnamt8901h.netops.charter.com [69.144.94.241]

     4   9 ms  10 ms  11 ms lag-26.crr01msslmt.netops.charter.com [69.144.26.222]

     5   9 ms  10 ms  11 ms lag-4.crr02msslmt.netops.charter.com [72.175.111.254]

     6  15 ms  15 ms  15 ms lag-23.msslmt33zp0.netops.charter.com [69.146.123.12]

     7  33 ms  23 ms  23 ms lag-702.bbr02sttlwa.netops.charter.com [69.144.130.200]

     8  26 ms  25 ms  26 ms lag-802.prr01sttlwa.netops.charter.com [96.34.3.39]

     9  26 ms  25 ms  25 ms 72.14.194.48

     10  67 ms  67 ms  69 ms 141.213.192.35.bc.googleusercontent.com [35.192.213.141]


    This is an example of how inefficient my routing is.


    Tracing route to 23.106.215.102 over a maximum of 30 hops


     1  <1 ms  <1 ms  <1 ms 192.168.1.1

     2   *    *    *   Request timed out.

     3  14 ms  17 ms  15 ms lag-63.hlnamt8901h.netops.charter.com [69.144.94.241]

     4  12 ms  20 ms  13 ms lag-26.crr01msslmt.netops.charter.com [69.144.26.222]

     5  26 ms  26 ms  28 ms lag-23.dnvtco56zp0.netops.charter.com [69.146.123.14]

     6  75 ms  83 ms  66 ms lag-11.msslmt33zp0.netops.charter.com [69.146.190.103]

     7  55 ms  55 ms  63 ms lag-702.bbr02sttlwa.netops.charter.com [69.144.130.200]

     8  58 ms  63 ms  59 ms lag-802.prr01sttlwa.netops.charter.com [96.34.3.39]

     9   *    *    *   Request timed out.

     10  55 ms  53 ms  48 ms ae12.cs2.sea1.us.eth.zayo.com [64.125.23.46]

     11  57 ms  56 ms  67 ms ae1.mcs2.sea1.us.eth.zayo.com [64.125.29.23]

     12  55 ms  50 ms  49 ms 64.124.184.118.IPYX-067818-930-ZYO.zip.zayo.com [64.124.184.118]

     13  85 ms  77 ms  79 ms po-2.ce01.sea-11.us.leaseweb.net [23.81.208.7]

     14  74 ms  79 ms  76 ms 23.106.215.102


    Finally to the water.com you recommended.


    Tracing route to water.com [128.136.252.75]

    over a maximum of 30 hops:


     1  <1 ms  <1 ms  <1 ms 192.168.1.1

     2   *    *    *   Request timed out.

     3  10 ms   9 ms   8 ms lag-63.hlnamt8901h.netops.charter.com [69.144.94.241]

     4  10 ms  10 ms  10 ms lag-26.crr01msslmt.netops.charter.com [69.144.26.222]

     5  11 ms   9 ms  11 ms lag-4.crr02msslmt.netops.charter.com [72.175.111.254]

     6  17 ms  44 ms  14 ms lag-23.msslmt33zp0.netops.charter.com [69.146.123.12]

     7  23 ms  23 ms  23 ms lag-702.bbr02sttlwa.netops.charter.com [69.144.130.200]

     8  26 ms  27 ms  38 ms lag-802.prr01sttlwa.netops.charter.com [96.34.3.39]

     9  22 ms  22 ms  22 ms be-205-pe01.seattle.wa.ibone.comcast.net [23.30.207.69]

     10  21 ms  23 ms  22 ms 23.30.206.10

     11  100 ms  100 ms  99 ms be22.bbrt02.sea01.flexential.net [148.66.238.158]

     12  99 ms  98 ms  99 ms be159.bbrt01.slc04.flexential.net [66.51.4.214]

     13  104 ms  104 ms  114 ms be150.bbrt02.slc09.flexential.net [66.51.9.126]

     14  107 ms  103 ms  103 ms be102.bbrt02.las03.flexential.net [66.51.5.42]

     15  99 ms  99 ms  98 ms be10.bbrt01.las03.flexential.net [66.51.7.89]

     16  99 ms  98 ms  99 ms be106.bbrt02.dal01.flexential.net [66.51.7.69]

     17  98 ms  98 ms  99 ms be10.bbrt01.dal01.flexential.net [66.51.7.41]

     18  104 ms  103 ms  104 ms be136.bbrt01.atl10.flexential.net [148.66.237.93]

     19  104 ms  103 ms  106 ms be10.bbrt02.atl10.flexential.net [148.66.236.253]

     20  98 ms  101 ms  99 ms be166.bbrt01.atl03.flexential.net [148.66.237.101]

     21  104 ms  106 ms  103 ms be31.crrt01.atl03.flexential.net [66.51.8.134]

     22  98 ms  99 ms  98 ms 148.66.237.161

     23   *    *    *   Request timed out.

     24   *    *    *   Request timed out.

     25   *    *    *   Request timed out.

     26   *    *    *   Request timed out.

     27   *    *    *   Request timed out.

     28   *    *    *   Request timed out.

     29   *    *    *   Request timed out.

     30   *    *    *   Request timed out.

  • William_MWilliam_M Posts: 535 Moderator
    Jan 06, 2023

    Thank you. Your first test shows a steady increase up to 25ms right until the last hop to the server where it spikes to 67ms at the googleusercontent.com server. In the second test I see your ping does increase more up to 49 ms, but then it spikes to 79ms at leaseweb.net. The last test also shows you are making it through our network in about 22ms. 

    Please keep in mind that a limitation of a traceroute is that it pings each hop and the primary function of a hop is to forward data to the next hop, it may delay responding to ping requests until it is less busy, or not respond at all. Even if an individual hop seems to show a high ping, if the increase does not carry to the following hops then it wasn't a problem. For example; On your secnd test we see hop 6-8 reporting 66,63,59ms ping, but then hop 10 and 12 which are off our network are only 48/49ms. If they could respond in only 48ms, every hop along the way must be forwarding your data in less time than that. 

    Overall I'm not really seeing any issues here with the routing or otherwise, the biggest spikes in ping are coming from the servers themselves which are adding 30-40ms of the delay, but even then 70ms is still within an acceptable range and really shouldn't cause any noticeable connection issues as that is only 0.07 seconds.

Sign In or Register to comment.