From KY

ping -t 66.62.140.38

Pinging 66.62.140.38 with 32 bytes of data:
Reply from 66.62.140.38: bytes=32 time=110ms TTL=53
Reply from 66.62.140.38: bytes=32 time=99ms TTL=53
Reply from 66.62.140.38: bytes=32 time=102ms TTL=53
Reply from 66.62.140.38: bytes=32 time=100ms TTL=53
Reply from 66.62.140.38: bytes=32 time=97ms TTL=53
Reply from 66.62.140.38: bytes=32 time=95ms TTL=53
Reply from 66.62.140.38: bytes=32 time=105ms TTL=53
Reply from 66.62.140.38: bytes=32 time=93ms TTL=53
Reply from 66.62.140.38: bytes=32 time=93ms TTL=53
Reply from 66.62.140.38: bytes=32 time=97ms TTL=53
Reply from 66.62.140.38: bytes=32 time=111ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=106ms TTL=53
Reply from 66.62.140.38: bytes=32 time=100ms TTL=53
Reply from 66.62.140.38: bytes=32 time=92ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=92ms TTL=53
Reply from 66.62.140.38: bytes=32 time=93ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=91ms TTL=53
Reply from 66.62.140.38: bytes=32 time=103ms TTL=53

Ping statistics for 66.62.140.38:
Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 133ms, Average = 98ms