Quoted: Hey, do me a favor:
Go to a command prompt and type: ping www.google.com /n 25
and post the output. I'd love to see the ping times, since I'm a little concerned about latency. Pretty please?
|
You got it...latency was not that big of a concern, not a gamer here but my son while happy with the service does like to play games and this doesn't resolve his sadness
C:\>ping www.google.com /n 25
Pinging www.l.google.com [216.239.37.104] with 32 bytes of data:
Reply from 216.239.37.104: bytes=32 time=666ms TTL=233
Reply from 216.239.37.104: bytes=32 time=642ms TTL=233
Reply from 216.239.37.104: bytes=32 time=694ms TTL=233
Reply from 216.239.37.104: bytes=32 time=650ms TTL=233
Reply from 216.239.37.104: bytes=32 time=753ms TTL=232
Reply from 216.239.37.104: bytes=32 time=722ms TTL=232
Reply from 216.239.37.104: bytes=32 time=664ms TTL=233
Reply from 216.239.37.104: bytes=32 time=1065ms TTL=233
Reply from 216.239.37.104: bytes=32 time=1009ms TTL=232
Reply from 216.239.37.104: bytes=32 time=689ms TTL=232
Reply from 216.239.37.104: bytes=32 time=679ms TTL=233
Reply from 216.239.37.104: bytes=32 time=623ms TTL=233
Reply from 216.239.37.104: bytes=32 time=725ms TTL=232
Reply from 216.239.37.104: bytes=32 time=697ms TTL=232
Reply from 216.239.37.104: bytes=32 time=677ms TTL=233
Reply from 216.239.37.104: bytes=32 time=632ms TTL=233
Reply from 216.239.37.104: bytes=32 time=729ms TTL=232
Reply from 216.239.37.104: bytes=32 time=700ms TTL=232
Reply from 216.239.37.104: bytes=32 time=677ms TTL=232
Reply from 216.239.37.104: bytes=32 time=643ms TTL=232
Reply from 216.239.37.104: bytes=32 time=740ms TTL=233
Reply from 216.239.37.104: bytes=32 time=719ms TTL=233
Reply from 216.239.37.104: bytes=32 time=671ms TTL=232
Reply from 216.239.37.104: bytes=32 time=622ms TTL=232
Reply from 216.239.37.104: bytes=32 time=708ms TTL=233
Ping statistics for 216.239.37.104:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 622ms, Maximum = 1065ms, Average = 711ms