| Latency improving Latency is improving on Unplugged's network. This is pinging www.mplayer.com I got 2 spikes but 111ms and 130ms spikes aren't bad. The rest are excellent in the 20's. The second set I pulled a few minutes later and added them here. They're a little worse but still I would consider them pretty good.
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=26ms TTL=51
Reply from 207.38.1.157: bytes=32 time=61ms TTL=51
Reply from 207.38.1.157: bytes=32 time=22ms TTL=51
Reply from 207.38.1.157: bytes=32 time=22ms TTL=51
Reply from 207.38.1.157: bytes=32 time=56ms TTL=49
Reply from 207.38.1.157: bytes=32 time=111ms TTL=49
Reply from 207.38.1.157: bytes=32 time=22ms TTL=51
Reply from 207.38.1.157: bytes=32 time=23ms TTL=51
Reply from 207.38.1.157: bytes=32 time=37ms TTL=49
Reply from 207.38.1.157: bytes=32 time=130ms TTL=49
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 130ms, Average = 51ms
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=64ms TTL=49
Reply from 207.38.1.157: bytes=32 time=52ms TTL=51
Reply from 207.38.1.157: bytes=32 time=43ms TTL=51
Reply from 207.38.1.157: bytes=32 time=65ms TTL=49
Reply from 207.38.1.157: bytes=32 time=85ms TTL=49
Reply from 207.38.1.157: bytes=32 time=130ms TTL=51
Reply from 207.38.1.157: bytes=32 time=72ms TTL=51
Reply from 207.38.1.157: bytes=32 time=54ms TTL=49
Reply from 207.38.1.157: bytes=32 time=41ms TTL=49
Reply from 207.38.1.157: bytes=32 time=50ms TTL=51
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 130ms, Average = 65ms
[text was edited by author 2002-07-01 23:55:59] |
