A little earlier than planned (for a change lol) but Miami versus is online. So we cover about the entire USA right now 199.16.204.57:27015 Please post test results here! Thanks!
wow miami you going there anywhere soon Marvel? as i could join you for moral support and carry around your bagges
Ping from Salt Lake City, Utah, approximately 2500 miles away. PING 199.16.204.57 (199.16.204.57): 56 data bytes 64 bytes from 199.16.204.57: icmp_seq=0 ttl=48 time=81.861 ms 64 bytes from 199.16.204.57: icmp_seq=1 ttl=48 time=81.133 ms 64 bytes from 199.16.204.57: icmp_seq=2 ttl=48 time=81.862 ms 64 bytes from 199.16.204.57: icmp_seq=3 ttl=48 time=81.152 ms 64 bytes from 199.16.204.57: icmp_seq=4 ttl=48 time=84.340 ms 64 bytes from 199.16.204.57: icmp_seq=5 ttl=48 time=81.445 ms 64 bytes from 199.16.204.57: icmp_seq=6 ttl=48 time=89.887 ms 64 bytes from 199.16.204.57: icmp_seq=7 ttl=48 time=81.588 ms 64 bytes from 199.16.204.57: icmp_seq=8 ttl=48 time=81.747 ms 64 bytes from 199.16.204.57: icmp_seq=9 ttl=48 time=81.266 ms --- 199.16.204.57 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 81.133/82.628/89.887/2.575 ms
Good to hear! Here are my ping results from Chile. Code: Pinging 199.16.204.57 with 32 bytes of data: Reply from 199.16.204.57: bytes=32 time=139ms TTL=51 Reply from 199.16.204.57: bytes=32 time=139ms TTL=51 Reply from 199.16.204.57: bytes=32 time=139ms TTL=51 Reply from 199.16.204.57: bytes=32 time=142ms TTL=51 Ping statistics for 199.16.204.57: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 139ms, Maximum = 142ms, Average = 139ms
Ping results from Peru Pinging 199.16.204.57 with 32 bytes of data: Reply from 199.16.204.57: bytes=32 time=114ms TTL=53 Reply from 199.16.204.57: bytes=32 time=113ms TTL=53 Reply from 199.16.204.57: bytes=32 time=100ms TTL=51 Reply from 199.16.204.57: bytes=32 time=100ms TTL=52 Ping statistics for 199.16.204.57: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 100ms, Maximum = 114ms, Average = 106ms
Well, Marvel was with me when I was testing the server, and he knows the result. Anyway, my ping average was 250ms (I'm from South-Brazil), but no packet loss or lag. Although the high ping, the server is better than the last Brazil server. The only thing that sucks is the emptiness on the server.
Don't see how pinging the server shows the real ping. I normally get the lowest ping around 80 on the EU VS/Coop servers but when i pinged the EU VS server, the result was: Pinging 83.149.71.78 with 32 bytes of data: Reply from 83.149.71.78: bytes=32 time=29ms TTL=56 Reply from 83.149.71.78: bytes=32 time=30ms TTL=56 Reply from 83.149.71.78: bytes=32 time=34ms TTL=56 Reply from 83.149.71.78: bytes=32 time=30ms TTL=56 Ping statistics for 83.149.71.78: Packets: Sent = 4, Received = 4, Lost = 0 (0% lo Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 34ms, Average = 30ms So my average ping should be 30 but i can understand, why it is close to three times higher so my point is, pinging the server from the cmd prompt doesn't show how good your ping will be ..
Ping from Toronto, Ontario, Canada! Reply from 199.16.204.57: bytes=32 time=62ms TTL=53 Reply from 199.16.204.57: bytes=32 time=50ms TTL=53 Reply from 199.16.204.57: bytes=32 time=61ms TTL=53 Reply from 199.16.204.57: bytes=32 time=52ms TTL=53 Reply from 199.16.204.57: bytes=32 time=53ms TTL=53 Reply from 199.16.204.57: bytes=32 time=51ms TTL=53 Reply from 199.16.204.57: bytes=32 time=59ms TTL=53 Reply from 199.16.204.57: bytes=32 time=53ms TTL=53 Reply from 199.16.204.57: bytes=32 time=59ms TTL=53 Reply from 199.16.204.57: bytes=32 time=66ms TTL=53