我只在我的机器上测试过这个问题,但是在不同的地区和不同的 ISP 上。
当我 ping 服务器时,时间正常,但第 10 次尝试时仍不行。请看:
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
再举一个例子:
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
如你所见,对于我到目前为止尝试过的任何站点,ping 值在第 10 次尝试时就会跳升到一个很高的数字,然后下降。
为什么会发生这种情况?
我在玩网络游戏的时候,突然卡顿了一会儿,然后又恢复正常了,这跟这种ping跳动有关系吗?
我怎样才能解决这个问题?
答案1
它是免费下载管理器 5每隔 10 秒就会阻塞网络。当我关闭它时,一切都正常,当我重新打开它时,问题又出现了。