Quote:
Originally Posted by qasdfdsaq
Ping statistics for 64.233.183.104:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 67ms, Average = 38ms
|
You can tell something isn't still quite right by the above. I use to get erratic results like those when I use having issues with oversubscription and now without any issues:
Code:
E:\Documents and Settings\Bob>ping 64.233.183.104 -n 20
Pinging 64.233.183.104 with 32 bytes of data:
Reply from 64.233.183.104: bytes=32 time=29ms TTL=242
Reply from 64.233.183.104: bytes=32 time=32ms TTL=242
Reply from 64.233.183.104: bytes=32 time=30ms TTL=242
Reply from 64.233.183.104: bytes=32 time=28ms TTL=242
Reply from 64.233.183.104: bytes=32 time=29ms TTL=242
Reply from 64.233.183.104: bytes=32 time=32ms TTL=242
Reply from 64.233.183.104: bytes=32 time=31ms TTL=242
Reply from 64.233.183.104: bytes=32 time=30ms TTL=242
Reply from 64.233.183.104: bytes=32 time=27ms TTL=242
Reply from 64.233.183.104: bytes=32 time=28ms TTL=242
Reply from 64.233.183.104: bytes=32 time=30ms TTL=242
Reply from 64.233.183.104: bytes=32 time=33ms TTL=242
Reply from 64.233.183.104: bytes=32 time=31ms TTL=242
Reply from 64.233.183.104: bytes=32 time=28ms TTL=242
Reply from 64.233.183.104: bytes=32 time=30ms TTL=242
Reply from 64.233.183.104: bytes=32 time=31ms TTL=242
Reply from 64.233.183.104: bytes=32 time=29ms TTL=242
Reply from 64.233.183.104: bytes=32 time=28ms TTL=242
Reply from 64.233.183.104: bytes=32 time=27ms TTL=242
Reply from 64.233.183.104: bytes=32 time=30ms TTL=242
Ping statistics for 64.233.183.104:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 33ms, Average = 29ms
Glad to see your speed is max though, fingers crossed for it stoping that way too. Quick you better touch some wood

.