All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Are large ping spikes normal?
Hi,
I'm seeing large spikes in ping to a machine that never used to exhibit this issue and it's causing me problems when trying to use the server. I've been told that it can be due to load & network conditions etc but this seems too consistent and abnormal for me to consider it an anomaly. It happens when I ping the machine from multiple locations.
Ping 1 (USA):
64 bytes from IP_REDACTED: icmp_seq=1 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=2 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=3 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=4 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=5 ttl=59 time=290 ms
64 bytes from IP_REDACTED: icmp_seq=6 ttl=59 time=533 ms
64 bytes from IP_REDACTED: icmp_seq=7 ttl=59 time=326 ms
64 bytes from IP_REDACTED: icmp_seq=8 ttl=59 time=400 ms
64 bytes from IP_REDACTED: icmp_seq=9 ttl=59 time=790 ms
64 bytes from IP_REDACTED: icmp_seq=11 ttl=59 time=331 ms
64 bytes from IP_REDACTED: icmp_seq=12 ttl=59 time=374 ms
64 bytes from IP_REDACTED: icmp_seq=13 ttl=59 time=375 ms
64 bytes from IP_REDACTED: icmp_seq=14 ttl=59 time=314 ms
64 bytes from IP_REDACTED: icmp_seq=15 ttl=59 time=160 ms
64 bytes from IP_REDACTED: icmp_seq=16 ttl=59 time=74.1 ms
64 bytes from IP_REDACTED: icmp_seq=17 ttl=59 time=75.7 ms
64 bytes from IP_REDACTED: icmp_seq=18 ttl=59 time=74.3 ms
64 bytes from IP_REDACTED: icmp_seq=19 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=20 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=21 ttl=59 time=74.2 ms
64 bytes from IP_REDACTED: icmp_seq=22 ttl=59 time=74.1 ms
Ping 2 (UK, same as the server in question):
64 bytes from IP_REDACTED: icmp_seq=1 ttl=58 time=10.2 ms
64 bytes from IP_REDACTED: icmp_seq=2 ttl=58 time=9.27 ms
64 bytes from IP_REDACTED: icmp_seq=3 ttl=58 time=9.21 ms
64 bytes from IP_REDACTED: icmp_seq=4 ttl=58 time=9.06 ms
64 bytes from IP_REDACTED: icmp_seq=5 ttl=58 time=8.93 ms
64 bytes from IP_REDACTED: icmp_seq=6 ttl=58 time=231 ms
64 bytes from IP_REDACTED: icmp_seq=7 ttl=58 time=9.25 ms
64 bytes from IP_REDACTED: icmp_seq=8 ttl=58 time=9.14 ms
64 bytes from IP_REDACTED: icmp_seq=9 ttl=58 time=19.3 ms
64 bytes from IP_REDACTED: icmp_seq=10 ttl=58 time=325 ms
64 bytes from IP_REDACTED: icmp_seq=11 ttl=58 time=90.2 ms
64 bytes from IP_REDACTED: icmp_seq=12 ttl=58 time=292 ms
64 bytes from IP_REDACTED: icmp_seq=13 ttl=58 time=261 ms
64 bytes from IP_REDACTED: icmp_seq=14 ttl=58 time=257 ms
64 bytes from IP_REDACTED: icmp_seq=16 ttl=58 time=13.6 ms
64 bytes from IP_REDACTED: icmp_seq=17 ttl=58 time=26.7 ms
64 bytes from IP_REDACTED: icmp_seq=18 ttl=58 time=9.11 ms
64 bytes from IP_REDACTED: icmp_seq=19 ttl=58 time=9.29 ms
64 bytes from IP_REDACTED: icmp_seq=20 ttl=58 time=9.49 ms
64 bytes from IP_REDACTED: icmp_seq=21 ttl=58 time=8.96 ms
64 bytes from IP_REDACTED: icmp_seq=22 ttl=58 time=8.82 ms
64 bytes from IP_REDACTED: icmp_seq=23 ttl=58 time=8.98 ms
64 bytes from IP_REDACTED: icmp_seq=24 ttl=58 time=9.63 ms
64 bytes from IP_REDACTED: icmp_seq=25 ttl=58 time=9.34 ms
64 bytes from IP_REDACTED: icmp_seq=26 ttl=58 time=9.19 ms
64 bytes from IP_REDACTED: icmp_seq=27 ttl=58 time=504 ms
64 bytes from IP_REDACTED: icmp_seq=28 ttl=58 time=294 ms
64 bytes from IP_REDACTED: icmp_seq=29 ttl=58 time=316 ms
64 bytes from IP_REDACTED: icmp_seq=31 ttl=58 time=319 ms
64 bytes from IP_REDACTED: icmp_seq=32 ttl=58 time=266 ms
64 bytes from IP_REDACTED: icmp_seq=33 ttl=58 time=344 ms
64 bytes from IP_REDACTED: icmp_seq=34 ttl=58 time=480 ms
64 bytes from IP_REDACTED: icmp_seq=35 ttl=58 time=284 ms
What are your thoughts? Thanks
Comments
Considering how low it appears your actual pings are...
I would do a MTR or traceroute and see what network congestion if any is happening.
MTR will show that easier.
If using windows you can download WinMTR from https://sourceforge.net/projects/winmtr/
Otherwise look at the system loads on your VPS/Machine. Is your machine being overloaded and/or saturating the "pipe"?
I thought this too, traceroute looks like this, so to me the issue seems to be on their side, but I'm no networking expert. There's no load on the server, maybe I should reinstall it though. Same ping results if I go the other way too.
traceroute to REDCTED (REDACTED), 30 hops max, 60 byte packets
1 _gateway (192.168.1.1) 0.620 ms 0.917 ms 1.170 ms
2 REDACTED (REDACTED) 75.444 ms 75.450 ms 75.476 ms
3 ae50-ner002.thw.as13285.net (78.144.1.3) 10.274 ms 10.282 ms 8.546 ms
4 ae50-scr102.thw.as13285.net (78.144.1.2) 8.931 ms 9.135 ms 9.372 ms
5 ae60-scr101.thw.as13285.net (78.144.1.110) 9.871 ms 23.517 ms 23.622 ms
6 et1-1-0-to-linx-peer.mx0thn2.as42831.net (195.66.225.162) 11.363 ms 5.555 ms 6.109 ms
7 mx1.cov205-from-mx0.cov205.as42831.net (78.110.170.17) 12.837 ms 12.844 ms 10.068 ms
8 SERVER IP (SERVER IP) 319.384 ms 319.609 ms 319.658 ms
Not normal, seems like congestion.
Unless I'm missing something, the high latency in this arises at the last hop (your server). Verify you're not exhausting resources on your server, that's frequently a cause of high latency at the destination but nowhere else in the trace.
You could also try MTRing to another IP in the same range as your destination to see if this issue appears across more than just one device.
Thanks, I'll try this, I just reinstalled the VPS with a fresh OS and the issue persists
I would bet that the congestion is on your provider VPS node's uplink, and that your VPS has some noisy neighbors.
MTR the other way back to your IP or something close like 78.144.1.3 (hop 3)
If it starts at the server outbound, and continues back to that IP, you have your answer.
Keep an mtr running the other way and look for where it starts and 'follows down' the entire way. Likely on the VPS / server side back.
pick a second ip in the same subnet as your server.
then
mtr -c 100
for both addresses.
Next pick a second place you can ping from. Repeat the experiment. let us know what the results are.
So based on the below, I'm guessing the issue is on their end?
Host Loss% Snt Last Avg Best Wrst StDev
1. no.rdns.ukservers.com 15.8% 20 865.5 142.1 0.4 865.5 265.5
2. mx140.thw-from-mx0.thn2.as42831.net 5.3% 20 1695. 622.6 3.8 1695. 562.3
3. ae31.cr10-lon1.ip4.gtt.net 5.3% 20 781.4 267.9 4.0 1059. 374.2
4. ae1.cr2-nyc4.ip4.gtt.net 5.3% 19 930.8 356.2 74.0 1204. 418.4
5. ip4.gtt.net 10.5% 19 1327. 301.3 74.2 1327. 406.4
6.REDACTED 11.1% 19 873.3 239.0 74.2 873.3 285.1
Yup, no question. 11% packet loss that follows down the entire way back, way worse than what your side of the ping showed. 865ms to your first hop, that's beyond overloaded (not sure at hypervisor or network level)
EDIT: Is this taken from the server that's having high latency? Whatever server you took that second MTR on (UkServers) is having the network issue.
Yeah, so the vps that I'm having trouble with is indeed the cause of the issue. Bit of a shame really as it has been fine for almost a year. I'll try and get somewhere with support but they're not being very useful at the minute.
Thank you for your help.
Those ping fluctuations don't seem to originate from a malfunctioning OS. I think something(s) in your network is creating temporary congestions.