Elcid Wrote:Try anyone of these from http://www.serverbeach.com/
East Coast US: Herndon, Virginia
64.34.160.92
West Coast US: Los Angeles, California
72.51.32.76
Central US: San Antonio, Texas
66.139.72.6
*note this is from school network since well.. i'm at school :O*
M:\>ping 64.34.160.92
Pinging 64.34.160.92 with 32 bytes of data:
Reply from 64.34.160.92: bytes=32 time=129ms TTL=54
Reply from 64.34.160.92: bytes=32 time=128ms TTL=54
Reply from 64.34.160.92: bytes=32 time=130ms TTL=54
Reply from 64.34.160.92: bytes=32 time=130ms TTL=54
Ping statistics for 64.34.160.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 128ms, Maximum = 130ms, Average = 129ms
M:\>ping 72.51.32.76
Pinging 72.51.32.76 with 32 bytes of data:
Reply from 72.51.32.76: bytes=32 time=201ms TTL=48
Reply from 72.51.32.76: bytes=32 time=202ms TTL=48
Reply from 72.51.32.76: bytes=32 time=203ms TTL=48
Reply from 72.51.32.76: bytes=32 time=202ms TTL=48
Ping statistics for 72.51.32.76:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 203ms, Average = 202ms
M:\>ping 66.139.72.6
Pinging 66.139.72.6 with 32 bytes of data:
Reply from 66.139.72.6: bytes=32 time=173ms TTL=51
Reply from 66.139.72.6: bytes=32 time=173ms TTL=51
Reply from 66.139.72.6: bytes=32 time=174ms TTL=51
Reply from 66.139.72.6: bytes=32 time=174ms TTL=51
Ping statistics for 66.139.72.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 174ms, Average = 173ms
Need Logs? PM Me.
Support Your Local Log-Dealer!
->
Mark Forums Read <-