What about a ping test "ping
www.google.com -w 1000 -t"
Press <control>+<c> to stop the command.
The 14% packet loss is no good.
--------------------------------------------
C:\>ping
www.google.com -w 1000 -t
Pinging
www.l.google.com [72.14.207.104] with 32 bytes of data:
Reply from 72.14.207.104: bytes=32 time=518ms TTL=231
Reply from 72.14.207.104: bytes=32 time=501ms TTL=231
Reply from 72.14.207.104: bytes=32 time=609ms TTL=231
Reply from 72.14.207.104: bytes=32 time=483ms TTL=231
Reply from 72.14.207.104: bytes=32 time=479ms TTL=231
Request timed out.
Request timed out.
Reply from 72.14.207.104: bytes=32 time=505ms TTL=231
Reply from 72.14.207.104: bytes=32 time=511ms TTL=231
Reply from 72.14.207.104: bytes=32 time=616ms TTL=231
Reply from 72.14.207.104: bytes=32 time=575ms TTL=231
Reply from 72.14.207.104: bytes=32 time=480ms TTL=231
Reply from 72.14.207.104: bytes=32 time=501ms TTL=231
Reply from 72.14.207.104: bytes=32 time=517ms TTL=231
Reply from 72.14.207.104: bytes=32 time=481ms TTL=231
Reply from 72.14.207.104: bytes=32 time=624ms TTL=231
Reply from 72.14.207.104: bytes=32 time=491ms TTL=231
Reply from 72.14.207.104: bytes=32 time=546ms TTL=231
Request timed out.
Reply from 72.14.207.104: bytes=32 time=503ms TTL=231
Reply from 72.14.207.104: bytes=32 time=650ms TTL=231
Ping statistics for 72.14.207.104:
Packets: Sent = 21, Received = 18, Lost = 3 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 479ms, Maximum = 650ms, Average = 456ms
