So annoying, and shouldn't happen. It started last night. Here's a ping log:
Ping has started…
PING scratch.mit.edu (18.85.13.115): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 18.85.13.115: icmp_seq=1 ttl=48 time=60.541 ms
64 bytes from 18.85.13.115: icmp_seq=2 ttl=50 time=60.411 ms
64 bytes from 18.85.13.115: icmp_seq=3 ttl=48 time=60.521 ms
64 bytes from 18.85.13.115: icmp_seq=4 ttl=50 time=60.110 ms
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
64 bytes from 18.85.13.115: icmp_seq=7 ttl=50 time=63.517 ms
64 bytes from 18.85.13.115: icmp_seq=8 ttl=48 time=61.768 ms
64 bytes from 18.85.13.115: icmp_seq=9 ttl=48 time=60.543 ms
64 bytes from 18.85.13.115: icmp_seq=10 ttl=48 time=60.435 ms
64 bytes from 18.85.13.115: icmp_seq=11 ttl=48 time=62.445 ms
64 bytes from 18.85.13.115: icmp_seq=12 ttl=46 time=60.568 ms
Request timeout for icmp_seq 13
--- scratch.mit.edu ping statistics ---
15 packets transmitted, 10 packets received, 33.3% packet loss
round-trip min/avg/max/stddev = 60.110/61.086/63.517/1.060 ms
Offline
Mine:
64 bytes from 18.85.13.115: icmp_seq=0 ttl=250 time=35.160 ms
64 bytes from 18.85.13.115: icmp_seq=1 ttl=250 time=30.501 ms
64 bytes from 18.85.13.115: icmp_seq=2 ttl=250 time=30.398 ms
64 bytes from 18.85.13.115: icmp_seq=3 ttl=250 time=32.696 ms
64 bytes from 18.85.13.115: icmp_seq=4 ttl=250 time=30.090 ms
64 bytes from 18.85.13.115: icmp_seq=5 ttl=250 time=32.406 ms
64 bytes from 18.85.13.115: icmp_seq=6 ttl=250 time=32.259 ms
64 bytes from 18.85.13.115: icmp_seq=7 ttl=250 time=32.396 ms
64 bytes from 18.85.13.115: icmp_seq=8 ttl=250 time=32.008 ms
64 bytes from 18.85.13.115: icmp_seq=9 ttl=250 time=34.028 ms
64 bytes from 18.85.13.115: icmp_seq=10 ttl=250 time=28.643 ms
64 bytes from 18.85.13.115: icmp_seq=11 ttl=250 time=33.776 ms
64 bytes from 18.85.13.115: icmp_seq=12 ttl=250 time=28.402 ms
64 bytes from 18.85.13.115: icmp_seq=13 ttl=250 time=28.262 ms
64 bytes from 18.85.13.115: icmp_seq=14 ttl=250 time=31.233 ms
64 bytes from 18.85.13.115: icmp_seq=15 ttl=250 time=33.263 ms
64 bytes from 18.85.13.115: icmp_seq=16 ttl=250 time=33.097 ms
64 bytes from 18.85.13.115: icmp_seq=17 ttl=250 time=30.586 ms
64 bytes from 18.85.13.115: icmp_seq=18 ttl=250 time=30.406 ms
64 bytes from 18.85.13.115: icmp_seq=19 ttl=250 time=30.297 ms
64 bytes from 18.85.13.115: icmp_seq=20 ttl=250 time=32.328 ms
64 bytes from 18.85.13.115: icmp_seq=21 ttl=250 time=30.047 ms
--- scratch.mit.edu ping statistics ---
22 packets transmitted, 22 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 28.262/31.467/35.160/1.825 ms
Offline
My ISP said that their main server is down, no wonder why I get packet loss.
Offline