A tracert tells me it's somewhere in TX....Is that the case? Also, pinging the server gives me some serious inconsistency...who's the provider, Chuy? Looks like they're hosed in the first place...See below ping:
Pinging 72.36.222.172 with 32 bytes of data:
Reply from 72.36.222.172: bytes=32 time=65ms TTL=100
Reply from 72.36.222.172: bytes=32 time=65ms TTL=100
Reply from 72.36.222.172: bytes=32 time=65ms TTL=100
Reply from 72.36.222.172: bytes=32 time=77ms TTL=100
Reply from 72.36.222.172: bytes=32 time=65ms TTL=100
Reply from 72.36.222.172: bytes=32 time=156ms TTL=100
Reply from 72.36.222.172: bytes=32 time=64ms TTL=100
Reply from 72.36.222.172: bytes=32 time=528ms TTL=100
Reply from 72.36.222.172: bytes=32 time=66ms TTL=100
Reply from 72.36.222.172: bytes=32 time=143ms TTL=100
Reply from 72.36.222.172: bytes=32 time=66ms TTL=100
Reply from 72.36.222.172: bytes=32 time=397ms TTL=100
Reply from 72.36.222.172: bytes=32 time=229ms TTL=100
Reply from 72.36.222.172: bytes=32 time=879ms TTL=100
Reply from 72.36.222.172: bytes=32 time=72ms TTL=100
Reply from 72.36.222.172: bytes=32 time=626ms TTL=100
Reply from 72.36.222.172: bytes=32 time=326ms TTL=100
Reply from 72.36.222.172: bytes=32 time=429ms TTL=100
Reply from 72.36.222.172: bytes=32 time=918ms TTL=100
Reply from 72.36.222.172: bytes=32 time=971ms TTL=100
Reply from 72.36.222.172: bytes=32 time=88ms TTL=100
Ping statistics for 72.36.222.172:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 971ms, Average = 299ms
Anywhere from 65ms to 900+...what's the deal with that? No wonder I don't play on it....probably shows up as 700 or so when I search...hit the provider, and ask what the dealio is...IMHO.
Cup
(Security/Network Engineer, BTW...) Questions? Hit me up at
[email protected]Edit - My bad...son was uploading...66ms...you're good. (ignore the asshat giving bogus info...)
Last edited by Capt.CupoNoodles (2006-07-20 07:36:11)