Post by Makzimia on May 4, 2004 17:08:03 GMT
I am informed by my provider cox that they and ALL other responsible ISPs have just locked into place some more filtering for the current run of virus's out there. I phoned them after someone told me they got a 800ms rate on Fredian while coming in on ADSL, which traditionally BTW suffers more under these circumstances than Cable, but anyway, as long as those viruses are around, you can look forward to ping times being up all over the place I would think. Once the filters are not having to work as hard, things should return to normal.
This incidentily is not something I can really determine locally for the server itself, I only see what my ping times are in and out, gamespy is seperate, your ISP's are seperate etc etc... so, don't shoot the messenger
Here is a sample of my return rates..
Pinging www.google.akadns.net [66.102.7.99] with 32 bytes of data:
Reply from 66.102.7.99: bytes=32 time=22ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=23ms TTL=242
Reply from 66.102.7.99: bytes=32 time=20ms TTL=242
Reply from 66.102.7.99: bytes=32 time=20ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=27ms TTL=242
Reply from 66.102.7.99: bytes=32 time=25ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=23ms TTL=242
Reply from 66.102.7.99: bytes=32 time=19ms TTL=242
Reply from 66.102.7.99: bytes=32 time=25ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=37ms TTL=242
Reply from 66.102.7.99: bytes=32 time=26ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Ping statistics for 66.102.7.99:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 37ms, Average = 22ms
Pinging www.google.akadns.net [66.102.7.99] with 1024 bytes of
Reply from 66.102.7.99: bytes=56 (sent 1024) time=33ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=25ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=28ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=29ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=33ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=30ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=22ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=38ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=22ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Ping statistics for 66.102.7.99:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 38ms, Average = 25ms
Makz.
This incidentily is not something I can really determine locally for the server itself, I only see what my ping times are in and out, gamespy is seperate, your ISP's are seperate etc etc... so, don't shoot the messenger
Here is a sample of my return rates..
Pinging www.google.akadns.net [66.102.7.99] with 32 bytes of data:
Reply from 66.102.7.99: bytes=32 time=22ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=23ms TTL=242
Reply from 66.102.7.99: bytes=32 time=20ms TTL=242
Reply from 66.102.7.99: bytes=32 time=20ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=27ms TTL=242
Reply from 66.102.7.99: bytes=32 time=25ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=23ms TTL=242
Reply from 66.102.7.99: bytes=32 time=19ms TTL=242
Reply from 66.102.7.99: bytes=32 time=25ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=37ms TTL=242
Reply from 66.102.7.99: bytes=32 time=26ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Reply from 66.102.7.99: bytes=32 time=21ms TTL=242
Ping statistics for 66.102.7.99:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 37ms, Average = 22ms
Pinging www.google.akadns.net [66.102.7.99] with 1024 bytes of
Reply from 66.102.7.99: bytes=56 (sent 1024) time=33ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=25ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=28ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=29ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=33ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=30ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=22ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=23ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=38ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=22ms TTL=242
Reply from 66.102.7.99: bytes=56 (sent 1024) time=24ms TTL=242
Ping statistics for 66.102.7.99:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 38ms, Average = 25ms
Makz.