Gameserver Location Thread

G

German Muscle

Supreme [H]ardness
Joined
Aug 2, 2005
Messages
6,943
In order to gather where the best place is for everyone on average is to test it physically instead of guessing.

People in the USA are not really needed as i know the backbone structure and interconnects within the USA and which locations are best. This is more for the outside of the USA people. Im sure the USA people will post anyway though. :cool:

Here is the information i need.

Your location:
Do a ping to each IP. Post the result here.
Ping to IP #1:
Ping to IP #2:
Ping to IP #3:
Ping to IP #4:

Do a tracert to each IP.
Hops to IP #1:
Hops to IP #2:
Hops to IP #3:
Hops to IP #4:
Click to expand...

Here are the IP Addresses.
IP#1: 8.17.252.68
IP#2: 65.99.193.162
IP#3: 208.122.48.110
IP#4: 205.234.153.68
 
Your location: New Albany, Indiana USA
Do a ping to each IP. Post the result here.
Ping to IP #1: 75ms
Ping to IP #2: 40ms
Ping to IP #3: 39ms
Ping to IP #4: 34ms

Do a tracert to each IP.
Hops to IP #1: 16 Hops
Hops to IP #2: 13 Hops
Hops to IP #3: 19 Hops
Hops to IP #4: 16 Hops
 
Your location: Fort Lauderdale, Florida
Ping to IP #1: 88ms
Ping to IP #2: 45ms
Ping to IP #3: 46ms
Ping to IP #4: 56ms

Hops to IP #1: 19 Hops
Hops to IP #2: 16 Hops
Hops to IP #3: 15 Hops
Hops to IP #4: 13 Hops
 
Your location: Friendswood, TX 77546
Do a ping to each IP. Post the result here.
Ping to IP #1: 58ms
Ping to IP #2: 18ms
Ping to IP #3: 54ms
Ping to IP #4: 61ms

Do a tracert to each IP.
Hops to IP #1: 18 hops
Hops to IP #2: 12 hops
Hops to IP #3: 21 hops
Hops to IP #4: 14 hops
 
Your location: Tracy, CA 95304, on a wireless (802.11b) ISP - our house is 3 miles from civilization, and 4 miles as the crow flies to the antenna tower
Do a ping to each IP. Post the result here.
Ping to IP #1: 9ms
Ping to IP #2: 52ms
Ping to IP #3: 84ms
Ping to IP #4: 64ms

Do a tracert to each IP. (These are *including* the hop through my router, and through the WISP's antenna)
Hops to IP #1: 10 hops
Hops to IP #2: 20 hops
Hops to IP #3: 16 hops
Hops to IP #4: 15 hops
 
Toledo, OH - SBC Uverse 25/3 package
Here are the IP Addresses.
IP#1: 8.17.252.68
Ping 78/78/78
14 hops

IP#2: 65.99.193.162
Ping: 63/64/63
13 hops

IP#3: 208.122.48.110
Ping 51/51/51
15 hops

IP#4: 205.234.153.68
26/28/26
12 hops
 
20/2 Mbit Road Runner Broadband Connection

West Coast, USA

8.17.252.68 (15 Hops)
65.99.193.162 (16 Hops)
208.122.48.110 (22 Hops)
205.234.153.68 (15 Hops)

Reply from 8.17.252.68: bytes=32 time=22ms TTL=117
Reply from 8.17.252.68: bytes=32 time=23ms TTL=117
Reply from 8.17.252.68: bytes=32 time=19ms TTL=117
Reply from 8.17.252.68: bytes=32 time=58ms TTL=117
Reply from 8.17.252.68: bytes=32 time=55ms TTL=117
Reply from 8.17.252.68: bytes=32 time=29ms TTL=117
Reply from 8.17.252.68: bytes=32 time=19ms TTL=117
Reply from 8.17.252.68: bytes=32 time=27ms TTL=117
Reply from 8.17.252.68: bytes=32 time=18ms TTL=117
Reply from 8.17.252.68: bytes=32 time=23ms TTL=117

Ping statistics for 8.17.252.68:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 58ms, Average = 29ms

Reply from 65.99.193.162: bytes=32 time=48ms TTL=115
Reply from 65.99.193.162: bytes=32 time=57ms TTL=115
Reply from 65.99.193.162: bytes=32 time=45ms TTL=115
Reply from 65.99.193.162: bytes=32 time=56ms TTL=115
Reply from 65.99.193.162: bytes=32 time=49ms TTL=115
Reply from 65.99.193.162: bytes=32 time=51ms TTL=115
Reply from 65.99.193.162: bytes=32 time=47ms TTL=115
Reply from 65.99.193.162: bytes=32 time=69ms TTL=115
Reply from 65.99.193.162: bytes=32 time=46ms TTL=115
Reply from 65.99.193.162: bytes=32 time=45ms TTL=115

Ping statistics for 65.99.193.162:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 69ms, Average = 51ms

Reply from 208.122.48.110: bytes=32 time=155ms TTL=110
Reply from 208.122.48.110: bytes=32 time=116ms TTL=110
Reply from 208.122.48.110: bytes=32 time=116ms TTL=110
Reply from 208.122.48.110: bytes=32 time=147ms TTL=110
Reply from 208.122.48.110: bytes=32 time=148ms TTL=110
Reply from 208.122.48.110: bytes=32 time=130ms TTL=110
Reply from 208.122.48.110: bytes=32 time=116ms TTL=110
Reply from 208.122.48.110: bytes=32 time=118ms TTL=110
Reply from 208.122.48.110: bytes=32 time=113ms TTL=110
Reply from 208.122.48.110: bytes=32 time=113ms TTL=110

Ping statistics for 208.122.48.110:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 155ms, Average = 127ms

Reply from 205.234.153.68: bytes=32 time=65ms TTL=114
Reply from 205.234.153.68: bytes=32 time=76ms TTL=114
Reply from 205.234.153.68: bytes=32 time=65ms TTL=114
Reply from 205.234.153.68: bytes=32 time=66ms TTL=114
Reply from 205.234.153.68: bytes=32 time=65ms TTL=114
Reply from 205.234.153.68: bytes=32 time=66ms TTL=114
Reply from 205.234.153.68: bytes=32 time=64ms TTL=114
Reply from 205.234.153.68: bytes=32 time=63ms TTL=114
Reply from 205.234.153.68: bytes=32 time=63ms TTL=114
Reply from 205.234.153.68: bytes=32 time=63ms TTL=114

Ping statistics for 205.234.153.68:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 76ms, Average = 65ms
 
Swift Current, Saskatchewan, Canada

IP 1: 90 ms 16 hops
IP 2: 91 ms 16 hops
IP 3: 66 ms 17 hops
IP 4: 68 ms 18 hops
 
I will totally do this when i get home. I'm interested to see results on my ADSL2+ line to these IP's over there.
 
this may be of some help to you....

UK - Northwest (100Mbps leased line)

IP1 17 hops
IP2 18 hops
IP3 18 hops
IP4 16 hops

IP1 ping 148ms
IP2 ping 118ms
IP3 ping 85ms
IP4 ping 107ms
 
Hell, just for shits and giggles I tested out my connection. (Two wi-fi routers + a satellite link. Yet 0.6 miles away is FIOS, it's so close I can almost taste it... Should be illegal to taunt you like that. :mad: )


Your location: Purcellville, VA

Do a ping to each IP. Post the result here.
Ping to IP #1: 993ms
Ping to IP #2: 939ms
Ping to IP #3: 944ms
Ping to IP #4: 880ms

Do a tracert to each IP.
Hops to IP #1: 25
Hops to IP #2: 22
Hops to IP #3: 28
Hops to IP #4: 24
 
Your location: Hertfordshire, UK (15Mb Down, 1Mb Up)

Ping to IP #1: Reply from 8.17.252.68: bytes=32 time=177ms TTL=115
Ping to IP #2: Reply from 65.99.193.162: bytes=32 time=142ms TTL=111
Ping to IP #3: Reply from 208.122.48.110: bytes=32 time=111ms TTL=117
Ping to IP #4: Reply from 205.234.153.68: bytes=32 time=128ms TTL=112

Do a tracert to each IP.
Hops to IP #1: 16
Hops to IP #2: 18
Hops to IP #3: 14
Hops to IP #4: 15
 
Last edited:
Mancelona Michigan

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Drasalax>ping 8.17.252.68

Pinging 8.17.252.68 with 32 bytes of data:
Reply from 8.17.252.68: bytes=32 time=1583ms TTL=110
Request timed out.
Reply from 8.17.252.68: bytes=32 time=1562ms TTL=110
Reply from 8.17.252.68: bytes=32 time=1618ms TTL=110

Ping statistics for 8.17.252.68:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1562ms, Maximum = 1618ms, Average = 1587ms

C:\Users\Drasalax>ping 65.99.193.162

Pinging 65.99.193.162 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 65.99.193.162: bytes=32 time=1573ms TTL=109
Reply from 65.99.193.162: bytes=32 time=1608ms TTL=109

Ping statistics for 65.99.193.162:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1573ms, Maximum = 1608ms, Average = 1590ms

C:\Users\Drasalax>ping ^V
Ping request could not find host ▬. Please check the name and try again.

C:\Users\Drasalax>ping 208.122.48.110

Pinging 208.122.48.110 with 32 bytes of data:
Request timed out.
Reply from 208.122.48.110: bytes=32 time=1774ms TTL=115
Reply from 208.122.48.110: bytes=32 time=1629ms TTL=115
Reply from 208.122.48.110: bytes=32 time=1632ms TTL=115

Ping statistics for 208.122.48.110:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1629ms, Maximum = 1774ms, Average = 1678ms

C:\Users\Drasalax>ping 205.234.153.68

Pinging 205.234.153.68 with 32 bytes of data:
Reply from 205.234.153.68: bytes=32 time=1470ms TTL=116
Reply from 205.234.153.68: bytes=32 time=1546ms TTL=116
Reply from 205.234.153.68: bytes=32 time=1637ms TTL=116
Reply from 205.234.153.68: bytes=32 time=1559ms TTL=116

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

C:\Users\Drasalax>tracert 8.17.252.68

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

1 3 ms <1 ms <1 ms 192.168.1.1
2 3 ms 2 ms 2 ms 216-245-235-1.wireless.coliinc.com [216.245.235.
1]
3 4 ms 8 ms 6 ms 216-245-227-153.wireless.coliinc.com [216.245.22
7.153]
4 7 ms 5 ms 5 ms 216-245-227-9.wireless.coliinc.com [216.245.227.
9]
5 14 ms 11 ms 12 ms host-121-74-23-65.ussignalcom.net [65.23.74.121]

6 * 53 ms 46 ms te7-0-0.pe02.grr.ussignalcom.net [64.186.63.206]

7 18 ms 60 ms 24 ms te1-0-0.pe01.dtw.ussignalcom.net [74.204.127.254
]
8 277 ms 191 ms 104 ms ge-6-11-137.car2.Detroit1.Level3.net [4.79.12.9]

9 28 ms 85 ms 21 ms ae-11-11.car1.Detroit1.Level3.net [4.69.133.245]

10 23 ms 39 ms 28 ms ae-8-8.ebr2.Chicago1.Level3.net [4.69.133.242]
11 45 ms 25 ms 35 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]
12 26 ms 23 ms 23 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

13 50 ms 47 ms 48 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
14 51 ms 51 ms 48 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

15 79 ms 138 ms 74 ms ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
16 * 74 ms * ae-82-82.csw3.SanJose1.Level3.net [4.69.153.26]

17 75 ms 109 ms 123 ms ae-3-80.edge8.SanJose1.Level3.net [4.69.152.148]

18 72 ms 74 ms 79 ms CWIE-LLC.edge8.SanJose1.Level3.net [4.53.30.114]

19 84 ms 79 ms 138 ms host.colocrossing.com [8.17.252.68]

Trace complete.

C:\Users\Drasalax>tracert 65.99.193.162

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 63 ms * 3 ms 216-245-235-1.wireless.coliinc.com [216.245.235.
1]
3 12 ms 4 ms 6 ms 216-245-227-153.wireless.coliinc.com [216.245.22
7.153]
4 13 ms 8 ms 7 ms 216-245-227-9.wireless.coliinc.com [216.245.227.
9]
5 * 12 ms 12 ms host-121-74-23-65.ussignalcom.net [65.23.74.121]

6 20 ms 24 ms 19 ms te7-0-0.pe02.grr.ussignalcom.net [64.186.63.206]

7 17 ms 18 ms 17 ms te1-0-0.pe01.dtw.ussignalcom.net [74.204.127.254
]
8 19 ms 33 ms 85 ms ge-6-11-137.car2.Detroit1.Level3.net [4.79.12.9]

9 29 ms 17 ms 23 ms ae-11-11.car1.Detroit1.Level3.net [4.69.133.245]

10 37 ms 37 ms 64 ms ae-8-8.ebr2.Chicago1.Level3.net [4.69.133.242]
11 28 ms 25 ms 31 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]
12 46 ms 53 ms 45 ms ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]

13 44 ms 48 ms 43 ms ae-91-91.csw4.Dallas1.Level3.net [4.69.151.161]

14 45 ms 42 ms 44 ms ae-41-90.car1.Dallas1.Level3.net [4.69.145.195]

15 44 ms 61 ms 56 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70]
16 41 ms 44 ms 46 ms 0610.aggr.dal.colocossing.com [96.8.115.250]
17 47 ms 42 ms 47 ms host.colocrossing.com [65.99.193.162]

Trace complete.

C:\Users\Drasalax>tracert 208.122.48.110

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 37 ms 7 ms 7 ms 216-245-235-1.wireless.coliinc.com [216.245.235.
1]
3 4 ms 14 ms 5 ms 216-245-227-153.wireless.coliinc.com [216.245.22
7.153]
4 61 ms 35 ms 5 ms 216-245-227-9.wireless.coliinc.com [216.245.227.
9]
5 13 ms 18 ms 11 ms host-121-74-23-65.ussignalcom.net [65.23.74.121]

6 18 ms 19 ms 16 ms te4-0-0.pe02.chi.ussignalcom.net [70.34.130.30]

7 18 ms 18 ms 23 ms te-8-0-0.pe01.chi.ussignalcom.net [70.34.130.25]

8 21 ms 28 ms 22 ms equinix-ix.ord1.us.voxel.net [206.223.119.107]
9 45 ms 37 ms 51 ms 910.te4-3.tsr1.lga3.us.voxel.net [208.122.44.133
]
10 * * * Request timed out.
11 39 ms 41 ms 65 ms 0.ae57.csr2.lga6.us.voxel.net [208.122.44.210]
12 * 49 ms 40 ms v70.esr2.lga6.us.voxel.net [208.122.44.166]
13 40 ms 37 ms 38 ms ge-0-2.nyc.colocrossing.com [208.122.43.122]
14 48 ms 47 ms 72 ms 12.9610.10.aggr.nyc.colocrossing.com [208.122.49
.242]
15 39 ms 47 ms 43 ms host.colocrossing.com [208.122.48.110]

Trace complete.

C:\Users\Drasalax>tracert 205.234.153.68

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 57 ms 8 ms 2 ms 216-245-235-1.wireless.coliinc.com [216.245.235.
1]
3 4 ms 3 ms 14 ms 216-245-227-153.wireless.coliinc.com [216.245.22
7.153]
4 8 ms 10 ms 5 ms 216-245-227-9.wireless.coliinc.com [216.245.227.
9]
5 18 ms 14 ms 12 ms host-121-74-23-65.ussignalcom.net [65.23.74.121]

6 * 53 ms 20 ms te4-0-0.pe02.chi.ussignalcom.net [70.34.130.30]

7 21 ms 123 ms 20 ms bboi-ussignal.bboi.net [64.127.128.141]
8 20 ms 20 ms 18 ms equinix.xe-1-3-0.cr2.ord1.us.nlayer.net [206.223
.119.61]
9 23 ms 27 ms 31 ms po6.ar2.ord1.us.scnet.net [69.31.111.6]
10 22 ms 21 ms 21 ms 62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
11 38 ms 21 ms 28 ms as36352.po4.ar2.ord6.us.scnet.net [204.93.192.19
0]
12 21 ms 38 ms 22 ms fw146.aggr.chi.colocrossing.com [205.234.152.254
]
13 24 ms 23 ms 21 ms host.colocrossing.com [205.234.153.68]

Trace complete.

C:\Users\Drasalax>
 
Your location: Chicago, IL
Do a ping to each IP. Post the result here.
Ping to IP #1: 81ms
Ping to IP #2: 45ms
Ping to IP #3: TIMEOUT
Ping to IP #4: 11ms
 
Do a tracert to each IP.
Hops to IP #1: 14 hops
Hops to IP #2: 13 hops
Hops to IP #3: TIMEOUT - made about 10 hops then timed out repeatedly
Hops to IP #4: 14 hops
 
Your location: Las Vegas, NV Cox Communications 50/5 service
Do a ping to each IP. Post the result here.
Ping to IP #1: 22ms average
Ping to IP #2: 47ms average
Ping to IP #3: 103ms average
Ping to IP #4: 70ms average

Do a tracert to each IP.
Hops to IP #1: 12
Hops to IP #2: 15
Hops to IP #3: 14 with 1 timeout
Hops to IP #4: 12


I will test again at my house later with my 25/2 service.
 
Your location: Hamilton, ON, Canada
Do a ping to each IP. Post the result here.
Ping to IP #1: 79ms
Ping to IP #2: 56ms
Ping to IP #3: 37ms
Ping to IP #4: 26ms

Do a tracert to each IP.
Hops to IP #1: 18
Hops to IP #2: 15
Hops to IP #3: 16
Hops to IP #4: 13
 
Your location: Misawa, Amori Prefecture, Japan
Do a ping to each IP. Post the result here.
Ping to IP #1: Min = 167, Max = 171, Avg = 168
Ping to IP #2: Min = 202, Max = 203, Avg = 202
Ping to IP #3: Min = 221, Max = 225, Avg = 223
Ping to IP #4: Min = 201, Max = 205, Avg = 202

Do a tracert to each IP.
Hops to IP #1: 12
Hops to IP #2: 20
Hops to IP #3: 19
Hops to IP #4: 15
 
Your location: Las Vegas, NV Cox 25/2 Service
Do a ping to each IP. Post the result here.
Ping to IP #1: 45ms average
Ping to IP #2: 85ms average
Ping to IP #3: 119ms average
Ping to IP #4: 84ms average

Do a tracert to each IP.
Hops to IP #1: 13
Hops to IP #2: 16
Hops to IP #3: 15
Hops to IP #4: 13
 
Ping and Routing traced in this order

#1: 8.17.252.68
#2: 65.99.193.162
#3: 208.122.48.110
#4: 205.234.153.68

My location: San Jose, CA

Ping to IP #1: 16ms
Ping to IP #2: 60ms
Ping to IP #3: 92ms
Ping to IP #4: 80ms

Hops to IP #1: 8
Hops to IP #2: 16
Hops to IP #3: 16
Hops to IP #4: 15
 
Last edited:
Location: Gurnee, IL
#1: 85ms
#2: 48ms
#3: 42ms
#4: 15ms

#1: 14 hops
#2: 13 hops
#3: 20 hops
#4: 14 hops
 
So far in this thread the average pings are:

IP #1: 78ms
IP #2: 72ms
IP #3: 85ms
IP #4: 68ms

I didn't include the two 1000ms+ latencies.
 
Location: Ontario, Canada

Ping to IP #1: 105ms
Ping to IP #2: 74ms
Ping to IP #3: 45ms
Ping to IP #4: 33ms

Do a tracert to each IP.
Hops to IP #1: 19
Hops to IP #2: 19
Hops to IP #3: 19
Hops to IP #4: 13
 
Your location: Boise, Idaho

Ping to IP #1: 64ms
Ping to IP #2: 61ms
Ping to IP #3: 92ms
Ping to IP #4: 70ms

Do a tracert to each IP.
Hops to IP #1: 13
Hops to IP #2: 14
Hops to IP #3: 17
Hops to IP #4: 12
 
I dont know what this is for but here you go.

Location: Vancouver, BC

Ping to IP #1: 38ms
Ping to IP #2: 90ms
Ping to IP #3: 110ms
Ping to IP #4: 64ms

Hops to IP #1: 11
Hops to IP #2: 16
Hops to IP #3: 18
Hops to IP #4: 14
 
You must log in or register to reply here.
Back
Top