15 replies to this topic

[Lin]

We will be moving the DoD servers in about 3 weeks. We need to know how members will ping at the new locations, as Virginia is not available.

The available choices are:
Eff 03/17/2013 we have some new test IPs:

Atlanta 174.34.147.91

Buffalo NY 192.210.199.59

NY: 173.234.159.101

You can test your ping by going to a Command prompt (Start > Run > cmd) and type one of the following:

To obtain just your ping:
C:\Documents and Settings\username> ping 173.234.159.101

To check the hops between you and the potential server location (and get your ping):
C:\Documents and Settings\username> tracert 173.234.159.101

For best results, do this over the space of three days, and report here with the results of all three days. We all know there are times the innerwebs have issues, and a three-day report should give us enough information to ascertain what your average will be.

What we want to do is to determine the pings for our player demographics, and try to choose a server that will fit our demographics the best. While my guess would be Buffalo (so the EU players can play well), Chicago just might surprise us.

[Captain John H. Miller]

I think for Euro players the IP closest to the atlantic would be better for our ping.


C:\Users\Joep>ping 108.174.48.194

Pingen naar 108.174.48.194 met 32 bytes aan gegevens:
Antwoord van 108.174.48.194: bytes=32 tijd=116 ms TTL=112
Antwoord van 108.174.48.194: bytes=32 tijd=116 ms TTL=112
Antwoord van 108.174.48.194: bytes=32 tijd=117 ms TTL=112
Antwoord van 108.174.48.194: bytes=32 tijd=116 ms TTL=112

Ping-statistieken voor 108.174.48.194:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 116ms, Maximum = 117ms, Gemiddelde = 116ms

C:\Users\Joep>ping 198.12.65.18

Pingen naar 198.12.65.18 met 32 bytes aan gegevens:
Antwoord van 198.12.65.18: bytes=32 tijd=109 ms TTL=115
Antwoord van 198.12.65.18: bytes=32 tijd=107 ms TTL=115
Antwoord van 198.12.65.18: bytes=32 tijd=107 ms TTL=115
Antwoord van 198.12.65.18: bytes=32 tijd=108 ms TTL=115

Ping-statistieken voor 198.12.65.18:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 107ms, Maximum = 109ms, Gemiddelde = 107ms

[Sillyminion]

I checked my ping last night and this morning (will continue testing over the next few days to see if anything changes) but i do better in Chicago by about 10 ping. I think it's mostly a result of the fact that my internet provider sends me to Chicago before Buffalo, go figure.

[LeadPaint]

I'll try to edit these later. Just for a base I ping 45-50ms to Virginia.

Chicago~ Day 1:48ms Day 2:48ms Day 3:48ms

Buffalo~ Day 1:63ms Day 2:60ms Day 3:61ms

I still hesitate to go Chicago unless there is current backbone in the infrastructure that keeps bottlenecking in Chicago down. But I shudder at peak hours in the NY area as well. Surprised Buffalo only cuts Miller's ping by 10. I'm game either way, and may give me a good excuse later for all my deaths.

And be careful when you run these, I got some false pings in the first check on both today.

Edited by LeadPaint, 14 March 2013 - 01:43 PM.

[ski]

Ping 198.12.65.18
Average time over 10 pings: 34 ms 3/10
Average time over 10 pings: 40 ms 3/11
Average time over 10 pings: 39 ms 3/12


Ping 108.174.48.194
Average time over 10 pings: 13.7 ms 3/10
Average time over 10 pings: 12 ms 3/11
Average time over 10 pings: 10 ms 3/12

[Sillyminion]

Ping 198.12.65.18
Average time over 10 pings: 34 ms


Ping 108.174.48.194
Average time over 10 pings: 13.7 ms

Buffalo is looking better and better. . .

[Xianide]

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Skywithnolimit>ping 108.174.48.194

Pinging 108.174.48.194 with 32 bytes of data:
Reply from 108.174.48.194: bytes=32 time=61ms TTL=114
Reply from 108.174.48.194: bytes=32 time=59ms TTL=114
Reply from 108.174.48.194: bytes=32 time=59ms TTL=114
Reply from 108.174.48.194: bytes=32 time=59ms TTL=114

Ping statistics for 108.174.48.194:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 61ms, Average = 59ms

C:\Users\Skywithnolimit>

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Skywithnolimit>ping 198.12.65.18

Pinging 198.12.65.18 with 32 bytes of data:
Reply from 198.12.65.18: bytes=32 time=76ms TTL=117
Reply from 198.12.65.18: bytes=32 time=74ms TTL=117
Reply from 198.12.65.18: bytes=32 time=78ms TTL=117
Reply from 198.12.65.18: bytes=32 time=75ms TTL=117

Ping statistics for 198.12.65.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 78ms, Average = 75ms

C:\Users\Skywithnolimit>

[Captain John H. Miller]

Second one


Microsoft Windows [versie 6.1.7601]
Copyright © 2009 Microsoft Corporation. Alle rechten voorbehouden.

C:\Users\Joep>ping 108.174.48.194

Pingen naar 108.174.48.194 met 32 bytes aan gegevens:
Antwoord van 108.174.48.194: bytes=32 tijd=118 ms TTL=112
Antwoord van 108.174.48.194: bytes=32 tijd=116 ms TTL=112
Antwoord van 108.174.48.194: bytes=32 tijd=122 ms TTL=112
Antwoord van 108.174.48.194: bytes=32 tijd=118 ms TTL=112

Ping-statistieken voor 108.174.48.194:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 116ms, Maximum = 122ms, Gemiddelde = 118ms

C:\Users\Joep>ping 198.12.65.18

Pingen naar 198.12.65.18 met 32 bytes aan gegevens:
Antwoord van 198.12.65.18: bytes=32 tijd=108 ms TTL=115
Antwoord van 198.12.65.18: bytes=32 tijd=108 ms TTL=115
Antwoord van 198.12.65.18: bytes=32 tijd=107 ms TTL=115
Antwoord van 198.12.65.18: bytes=32 tijd=108 ms TTL=115

Ping-statistieken voor 198.12.65.18:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 107ms, Maximum = 108ms, Gemiddelde = 107ms

[Noir]

Lol, What's Wrong With This Picture. I live in Buffalo Yet I ping Better to Chicago, lol. By 20ms too.

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jamie>ping 108.174.48.194

Pinging 108.174.48.194 with 32 bytes of data:

Reply from 108.174.48.194: bytes=32 time=27ms TTL=114
Reply from 108.174.48.194: bytes=32 time=32ms TTL=114
Reply from 108.174.48.194: bytes=32 time=28ms TTL=114
Reply from 108.174.48.194: bytes=32 time=32ms TTL=114

Ping statistics for 108.174.48.194:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 32ms, Average = 29ms

C:\Documents and Settings\Jamie>ping 198.12.65.18

Pinging 198.12.65.18 with 32 bytes of data:

Reply from 198.12.65.18: bytes=32 time=50ms TTL=114
Reply from 198.12.65.18: bytes=32 time=45ms TTL=114
Reply from 198.12.65.18: bytes=32 time=56ms TTL=114
Reply from 198.12.65.18: bytes=32 time=45ms TTL=114

Ping statistics for 198.12.65.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 56ms, Average = 49ms


On a trace It looks like It goes from buffalo to chicago and back to buffalo, lol

[Red Dragon/Mushu]

for me, my ping is going to increase by about 20 .... on a good day

[Lin]

Eff 03/17/2013 we have some new test IPs:

Atlanta 174.34.147.91

Buffalo NY 192.210.199.59

NY: 173.234.159.101

[Captain John H. Miller]

C:\Users\hgebruiker>ping 174.34.147.91

Pingen naar 174.34.147.91 met 32 bytes aan gegevens:
Antwoord van 174.34.147.91: bytes=32 tijd=114 ms TTL=115
Antwoord van 174.34.147.91: bytes=32 tijd=113 ms TTL=115
Antwoord van 174.34.147.91: bytes=32 tijd=114 ms TTL=115
Antwoord van 174.34.147.91: bytes=32 tijd=113 ms TTL=115

Ping-statistieken voor 174.34.147.91:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 113ms, Maximum = 114ms, Gemiddelde = 113ms

C:\Users\hgebruiker>ping 192.210.199.59

Pingen naar 192.210.199.59 met 32 bytes aan gegevens:
Antwoord van 192.210.199.59: bytes=32 tijd=108 ms TTL=114
Antwoord van 192.210.199.59: bytes=32 tijd=109 ms TTL=114
Antwoord van 192.210.199.59: bytes=32 tijd=108 ms TTL=114
Antwoord van 192.210.199.59: bytes=32 tijd=107 ms TTL=114

Ping-statistieken voor 192.210.199.59:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 107ms, Maximum = 109ms, Gemiddelde = 108ms

C:\Users\hgebruiker>ping 173.234.159.101

Pingen naar 173.234.159.101 met 32 bytes aan gegevens:
Antwoord van 173.234.159.101: bytes=32 tijd=100 ms TTL=118
Antwoord van 173.234.159.101: bytes=32 tijd=100 ms TTL=118
Antwoord van 173.234.159.101: bytes=32 tijd=100 ms TTL=118
Antwoord van 173.234.159.101: bytes=32 tijd=100 ms TTL=118

Ping-statistieken voor 173.234.159.101:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 100ms, Maximum = 100ms, Gemiddelde = 100ms

[Xianide]

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Skywithnolimit>ping 174.34.147.91

Pinging 174.34.147.91 with 32 bytes of data:
Reply from 174.34.147.91: bytes=32 time=69ms TTL=118
Reply from 174.34.147.91: bytes=32 time=70ms TTL=118
Reply from 174.34.147.91: bytes=32 time=69ms TTL=118
Reply from 174.34.147.91: bytes=32 time=68ms TTL=118

Ping statistics for 174.34.147.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 70ms, Average = 69ms
----------
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Skywithnolimit>ping 192.210.199.59

Pinging 192.210.199.59 with 32 bytes of data:
Reply from 192.210.199.59: bytes=32 time=85ms TTL=115
Reply from 192.210.199.59: bytes=32 time=86ms TTL=115
Reply from 192.210.199.59: bytes=32 time=87ms TTL=115
Reply from 192.210.199.59: bytes=32 time=87ms TTL=115

Ping statistics for 192.210.199.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 87ms, Average = 86ms
--------
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Skywithnolimit>ping 173.234.159.101

Pinging 173.234.159.101 with 32 bytes of data:
Reply from 173.234.159.101: bytes=32 time=80ms TTL=117
Reply from 173.234.159.101: bytes=32 time=79ms TTL=117
Reply from 173.234.159.101: bytes=32 time=80ms TTL=117
Reply from 173.234.159.101: bytes=32 time=78ms TTL=117

Ping statistics for 173.234.159.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 80ms, Average = 79ms

[LeadPaint]

Just throwing this out there...

Atlanta 174.34.147.91
~28ms

Buffalo NY 192.210.199.59
~52ms

NY: 173.234.159.101
~43ms

[Moose Springsteen]

27th March 2013
C:\Users\Alex>ping 174.34.147.91

Pinging 174.34.147.91 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 174.34.147.91:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Alex>ping 192.210.199.59

Pinging 192.210.199.59 with 32 bytes of data:
Reply from 192.210.199.59: bytes=32 time=98ms TTL=118
Reply from 192.210.199.59: bytes=32 time=99ms TTL=118
Reply from 192.210.199.59: bytes=32 time=98ms TTL=118
Reply from 192.210.199.59: bytes=32 time=99ms TTL=118

Ping statistics for 192.210.199.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 99ms, Average = 98ms

C:\Users\Alex>tracert 192.210.199.59

Tracing route to host.colocrossing.com [192.210.199.59]
over a maximum of 30 hops:

1 9 ms 10 ms 12 ms cpc4-colc6-2-0-gw.7-4.cable.virginmedia.com [82.
26.96.1]
2 9 ms 6 ms 7 ms colc-core-1b-ae3-2094.network.virginmedia.net [2
13.107.225.181]
3 11 ms 19 ms 11 ms nrth-bb-1b-xe-206-0.network.virginmedia.net [212
.43.163.61]
4 16 ms 14 ms 15 ms leed-bb-1a-as2-0.network.virginmedia.net [62.253
.185.102]
5 40 ms 20 ms 19 ms tcl3-ic-1-ae0-0.network.virginmedia.net [212.43.
163.198]
6 16 ms 15 ms 19 ms ldn-b2-link.telia.net [213.248.93.69]
7 18 ms 19 ms 23 ms ldn-bb1-link.telia.net [80.91.250.225]
8 90 ms 90 ms 91 ms nyk-bb1-link.telia.net [80.91.249.249]
9 100 ms 98 ms 100 ms buf-b1-link.telia.net [80.91.246.36]
10 101 ms 98 ms 99 ms giglinx-ic-155660-buf-b1.c.telia.net [213.248.96
.42]
11 106 ms 99 ms 102 ms host.colocrossing.com [198.23.156.62]
12 117 ms 99 ms 99 ms host.colocrossing.com [192.210.199.59]

Trace complete.

C:\Users\Alex>ping 173.234.159.101

Pinging 173.234.159.101 with 32 bytes of data:
Reply from 173.234.159.101: bytes=32 time=91ms TTL=117
Reply from 173.234.159.101: bytes=32 time=93ms TTL=117
Reply from 173.234.159.101: bytes=32 time=94ms TTL=117
Reply from 173.234.159.101: bytes=32 time=92ms TTL=117

Ping statistics for 173.234.159.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 94ms, Average = 92ms

C:\Users\Alex>tracert 173.234.159.10

Tracing route to 173.234.159.10.rdns.ubiquityservers.com [173.234.159.10]
over a maximum of 30 hops:

1 16 ms 10 ms 11 ms cpc4-colc6-2-0-gw.7-4.cable.virginmedia.com [82.
26.96.1]
2 8 ms 7 ms 7 ms colc-core-1a-ae3-2094.network.virginmedia.net [2
13.107.225.53]
3 11 ms 11 ms 11 ms popl-bb-1b-xe-4111-0.network.virginmedia.net [21
2.43.163.57]
4 6 ms 11 ms 11 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.10
5.159.2]
5 19 ms 18 ms 19 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
6 21 ms 24 ms 33 ms ams-ix.ae1.cr1.ams2.nl.nlayer.net [195.69.145.21
9]
7 29 ms 35 ms 19 ms ae3-50g.cr1.ams2.nl.nlayer.net [69.22.139.238]
8 18 ms 19 ms 18 ms xe-4-3-1.cr1.lhr1.uk.nlayer.net [69.22.142.15]
9 99 ms 90 ms 91 ms xe-3-0-0.cr1.ewr1.us.nlayer.net [69.22.142.30]
10 91 ms 91 ms 91 ms ae2-70g.cr1.nyc2.us.nlayer.net [69.31.95.174]
11 101 ms 90 ms 92 ms 69.174.121.61
12 104 ms 92 ms 104 ms xe6-1.cr1.nyc3.us.packetexchange.net [216.193.25
5.210]
13 92 ms 90 ms 97 ms 68.64.145.202
14 92 ms 91 ms 90 ms 173.234.159.10.rdns.ubiquityservers.com [173.234
.159.10]

Hope this helps

[Moose Springsteen]

28th March 2013

Microsoft Windows [Version 6.2.9200]
© 2012 Microsoft Corporation. All rights reserved.

C:\Users\Alex>ping 174.34.147.91

Pinging 174.34.147.91 with 32 bytes of data:
Reply from 174.34.147.91: bytes=32 time=113ms TTL=116
Reply from 174.34.147.91: bytes=32 time=111ms TTL=116
Reply from 174.34.147.91: bytes=32 time=121ms TTL=116
Reply from 174.34.147.91: bytes=32 time=118ms TTL=116

Ping statistics for 174.34.147.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 121ms, Average = 115ms

C:\Users\Alex>ping 192.210.199.59

Pinging 192.210.199.59 with 32 bytes of data:
Reply from 192.210.199.59: bytes=32 time=101ms TTL=115
Reply from 192.210.199.59: bytes=32 time=100ms TTL=115
Reply from 192.210.199.59: bytes=32 time=100ms TTL=115
Reply from 192.210.199.59: bytes=32 time=110ms TTL=115

Ping statistics for 192.210.199.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 110ms, Average = 102ms

C:\Users\Alex>ping 173.234.159.101

Pinging 173.234.159.101 with 32 bytes of data:
Reply from 173.234.159.101: bytes=32 time=99ms TTL=117
Reply from 173.234.159.101: bytes=32 time=105ms TTL=117
Reply from 173.234.159.101: bytes=32 time=94ms TTL=117
Reply from 173.234.159.101: bytes=32 time=106ms TTL=117

Ping statistics for 173.234.159.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 106ms, Average = 101ms