Skip to main content
Header
Kilobyte
March 28, 2023
Respondido

ping is unstable

Hello, the last few days I experience the issues with the network latency. That makes it impossible to play real-time online video games. The network delay is jumping from tens of milliseconds to hundreds or sometimes even thousands. This behavior can be easily noticed using https://www.meter.net/ping-test/ (see the screenshot below)

That happens to ALL network connections. I’ve already tried to reset the router. Can this be fixed somehow?

 

Melhor resposta por Bruno Aleixo

ISP’s dont work ping complaints since that can be related with rounting to a specific server. 

Try leaving the router turned off for a couple hours. 

good luck with that 

 

15 Comentários

GriefAutor
Kilobyte
March 28, 2023

ping 8.8.8.8


PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=26.7 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=82.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=26.5 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=59 time=514 ms

64 bytes from 8.8.8.8: icmp_seq=5 ttl=59 time=26.3 ms

64 bytes from 8.8.8.8: icmp_seq=6 ttl=59 time=237 ms

64 bytes from 8.8.8.8: icmp_seq=7 ttl=59 time=28.7 ms

64 bytes from 8.8.8.8: icmp_seq=8 ttl=59 time=143 ms

64 bytes from 8.8.8.8: icmp_seq=9 ttl=59 time=26.2 ms

64 bytes from 8.8.8.8: icmp_seq=10 ttl=59 time=29.0 ms

64 bytes from 8.8.8.8: icmp_seq=11 ttl=59 time=30.2 ms

64 bytes from 8.8.8.8: icmp_seq=12 ttl=59 time=25.1 ms

64 bytes from 8.8.8.8: icmp_seq=13 ttl=59 time=55.6 ms

64 bytes from 8.8.8.8: icmp_seq=14 ttl=59 time=25.1 ms

64 bytes from 8.8.8.8: icmp_seq=15 ttl=59 time=57.9 ms

64 bytes from 8.8.8.8: icmp_seq=16 ttl=59 time=27.9 ms

64 bytes from 8.8.8.8: icmp_seq=17 ttl=59 time=44.9 ms

64 bytes from 8.8.8.8: icmp_seq=18 ttl=59 time=33.5 ms

64 bytes from 8.8.8.8: icmp_seq=19 ttl=59 time=281 ms

64 bytes from 8.8.8.8: icmp_seq=20 ttl=59 time=27.1 ms

64 bytes from 8.8.8.8: icmp_seq=21 ttl=59 time=248 ms

64 bytes from 8.8.8.8: icmp_seq=22 ttl=59 time=31.0 ms

64 bytes from 8.8.8.8: icmp_seq=23 ttl=59 time=23.0 ms

64 bytes from 8.8.8.8: icmp_seq=24 ttl=59 time=27.5 ms

64 bytes from 8.8.8.8: icmp_seq=25 ttl=59 time=25.0 ms

64 bytes from 8.8.8.8: icmp_seq=26 ttl=59 time=42.8 ms

64 bytes from 8.8.8.8: icmp_seq=27 ttl=59 time=25.3 ms

64 bytes from 8.8.8.8: icmp_seq=28 ttl=59 time=36.9 ms

64 bytes from 8.8.8.8: icmp_seq=29 ttl=59 time=24.1 ms

64 bytes from 8.8.8.8: icmp_seq=30 ttl=59 time=56.2 ms

64 bytes from 8.8.8.8: icmp_seq=31 ttl=59 time=26.1 ms

64 bytes from 8.8.8.8: icmp_seq=32 ttl=59 time=130 ms

64 bytes from 8.8.8.8: icmp_seq=33 ttl=59 time=25.8 ms

64 bytes from 8.8.8.8: icmp_seq=34 ttl=59 time=584 ms

64 bytes from 8.8.8.8: icmp_seq=35 ttl=59 time=27.0 ms

64 bytes from 8.8.8.8: icmp_seq=36 ttl=59 time=428 ms

64 bytes from 8.8.8.8: icmp_seq=37 ttl=59 time=25.7 ms

64 bytes from 8.8.8.8: icmp_seq=38 ttl=59 time=371 ms

 

Guimas
Super User
Super User
March 28, 2023

fiber or satelite service? Conection threw cable to your pc?

GriefAutor
Kilobyte
March 28, 2023

Hello @Guimas It’s a fiber connected to nos router 5.0 v2 which in its turn is connected via ethernet cable to the notebook.

I’ve tried to do factory reset on router, but that didn’t help either: latency is still jumping to hunderds of ms almost every two seconds:

What are the clues I have:

  1. There are strange errors in router’s logs:
    1. There were strange errors in the web interface:

       

Bruno Aleixo
Super User
Bruno AleixoSuper UserResposta
Super User
March 28, 2023

ISP’s dont work ping complaints since that can be related with rounting to a specific server. 

Try leaving the router turned off for a couple hours. 

good luck with that 

 

O amigo Bruno ajuda
GriefAutor
Kilobyte
March 29, 2023

@Bruno Aleixo your advice seems to help me. Muito obrigado!

I did some trace routing yesterday, but unfortunately did not save the results. What I remember is that there were a plenty of nodes on the way to 8.8.8.8 and the ip which was responding with the unreliable time was 89.153.53.101.

Today, after leaving the router turned off for the night, there is no such ip in the route and the path seems to be much shorter:

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max
1 192.168.1.1 4.771ms 3.800ms 2.320ms
2 * * *
3 10.137.232.49 15.777ms 14.377ms 11.122ms
4 10.255.48.82 19.343ms 15.554ms 14.941ms
5 72.14.209.204 17.952ms 15.939ms 14.879ms
6 * * *
7 8.8.8.8 25.829ms 23.485ms 21.228ms

 

Bruno Aleixo
Super User
Super User
March 29, 2023

Glad it worked out @Grief ! it usualy does 

if it starts happening too ofthen the more permanent solution is getting a VPN connection to bypass those problematic routings! 🤙

O amigo Bruno ajuda
João H.
Gestor da comunidade
March 29, 2023

Hello @Grief,

Thank you for reaching out to us, and to @Bruno Aleixo for sharing some good tips regarding this matter.

Please let us know if the situation persists.

Thank you 

Ajude a comunidade a encontrar informação relevante. Marque como "Melhor Resposta" e faça "Like" nos melhores comentários. Siga os perfis da moderação, através da opção "Seguir", para estar sempre a par das ultimas novidades.
GriefAutor
Kilobyte
March 29, 2023

@João H. Yes, unfortunately the problem reappear again :( That might be that it was unrelated to the turning the router off and just wasn’t happening during the first half of the day. Now I see the same spiky latency as yesterday, online games are unplayable

 

João H.
Gestor da comunidade
March 30, 2023

Hello @Grief,

Thank you for your feedback.

 Please send us a private message to the @Fórum profile with your NOS Costumer Number.

Thank you 

Ajude a comunidade a encontrar informação relevante. Marque como "Melhor Resposta" e faça "Like" nos melhores comentários. Siga os perfis da moderação, através da opção "Seguir", para estar sempre a par das ultimas novidades.
GriefAutor
Kilobyte
March 31, 2023

@João H. messages on the forum seem not to work either :(