Foi o Free Download Manager 5 que estava bloqueando a rede a cada 10 segundos. Quando fechei, tudo funcionou bem e quando reabri o problema começou novamente.
Eu testei esse problema somente na minha máquina, mas em diferentes regiões e ISPs diferentes.
Quando faço ping em um servidor, o tempo está bom, mas não na 10ª tentativa. Olhe:
C:\Users\Aryan>ping google.com -t
Pinging google.com [216.58.205.238] with 32 bytes of data:
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44
Reply from 216.58.205.238: bytes=32 time=1232ms TTL=44 // HIGH TIME HERE
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44 // Ok 1
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44 // Ok 2
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44 // Ok 3
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44 // Ok 4
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44 // Ok 5
Reply from 216.58.205.238: bytes=32 time=167ms TTL=44 // Ok 6
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44 // Ok 7
Reply from 216.58.205.238: bytes=32 time=169ms TTL=44 // Ok 8
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44 // Ok 9
Reply from 216.58.205.238: bytes=32 time=951ms TTL=44 // NEXT HIGH TIME, on 10th
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44
Reply from 216.58.205.238: bytes=32 time=165ms TTL=44
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44
Reply from 216.58.205.238: bytes=32 time=900ms TTL=44 // AND NEXT
Reply from 216.58.205.238: bytes=32 time=166ms TTL=44
Reply from 216.58.205.238: bytes=32 time=164ms TTL=44
Como outro exemplo:
C:\Users\Aryan>ping blog.ir -t
Pinging blog.ir [91.99.101.242] with 32 bytes of data:
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=36ms TTL=53
Reply from 91.99.101.242: bytes=32 time=36ms TTL=53
Reply from 91.99.101.242: bytes=32 time=1045ms TTL=53 // HIGH TIME
Reply from 91.99.101.242: bytes=32 time=36ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=35ms TTL=53
Reply from 91.99.101.242: bytes=32 time=35ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=35ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=33ms TTL=53
Reply from 91.99.101.242: bytes=32 time=963ms TTL=53 // AND AGAIN
Reply from 91.99.101.242: bytes=32 time=33ms TTL=53
Reply from 91.99.101.242: bytes=32 time=39ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=33ms TTL=53
Reply from 91.99.101.242: bytes=32 time=33ms TTL=53
Reply from 91.99.101.242: bytes=32 time=36ms TTL=53
Reply from 91.99.101.242: bytes=32 time=34ms TTL=53
Reply from 91.99.101.242: bytes=32 time=35ms TTL=53
Reply from 91.99.101.242: bytes=32 time=893ms TTL=53 // AND AGAIN
Reply from 91.99.101.242: bytes=32 time=35ms TTL=53
Reply from 91.99.101.242: bytes=32 time=35ms TTL=53
Como você pode ver, para qualquer site que eu tenha tentado até agora, o ping em exatamente a 10ª tentativa salta para um número alto e, em seguida, fica inativo.
Por que isso está acontecendo?
Quando estou jogando um jogo on-line, tudo pára por um tempo e depois volta ao normal. Está relacionado a esse tipo de ping jumping?
Como posso corrigir isso?
Tags networking ping