Anyone else getting poor pings tonight?
Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=-15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=-16ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = -15ms, Average = 171798689ms
I am normally about 18 - 20ms but I assume all the negative values are false reporting of a too large a ping to display or something.
No problem's for me tonight. I don't ever recall seeing a ping return negative figures before so I can't advise. The positive figures look good but I assume you are having problems?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>ping idnet.net -n 20
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 11ms
C:\Users\zappaDPJ>
Never seen negative pings before, you should get a timeout (lost packet) before the number gets that big. Sounds like a router oddity, tried rebooting it?
Pings OK here (interleave is on):
ping -c 20 www.idnet.com
PING www.idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=26.503 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=26.461 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=25.901 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=26.414 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=26.030 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=26.509 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=26.223 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=26.704 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=26.437 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=25.860 ms
64 bytes from 212.69.36.10: icmp_seq=10 ttl=59 time=26.320 ms
64 bytes from 212.69.36.10: icmp_seq=11 ttl=59 time=26.471 ms
64 bytes from 212.69.36.10: icmp_seq=12 ttl=59 time=25.932 ms
64 bytes from 212.69.36.10: icmp_seq=13 ttl=59 time=26.065 ms
64 bytes from 212.69.36.10: icmp_seq=14 ttl=59 time=26.584 ms
64 bytes from 212.69.36.10: icmp_seq=15 ttl=59 time=25.515 ms
64 bytes from 212.69.36.10: icmp_seq=16 ttl=59 time=26.257 ms
64 bytes from 212.69.36.10: icmp_seq=17 ttl=59 time=26.428 ms
64 bytes from 212.69.36.10: icmp_seq=18 ttl=59 time=26.166 ms
64 bytes from 212.69.36.10: icmp_seq=19 ttl=59 time=25.860 ms
--- www.idnet.com ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 25.515/26.232/26.704/0.299 ms
Everything ok here :
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 13ms
Fine here as well
C:\Windows\system32>ping www.idnet.net -t
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 13ms, Average = 11ms
Control-C
^C
C:\Windows\system32>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.0.2
2 12 ms 13 ms 10 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 12 ms 12 ms 13 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 35 ms 248 ms 62 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 13 ms 13 ms 12 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 25 ms 12 ms 14 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Windows\system32>
I've never seen a negative ping either! I think a computer and router reboot are called for!
If the PC is running an AMD CPU there is a fix http://wiki.ljackson.us/Negative_Ping_Time