Latency Test

[SPANKY]

64.34.160.92
Ping is about 32ms

67.212.163.50
Ping is about 19ms

72.51.32.76
Ping is about 75ms

66.226.72.172
Ping is about 81ms

South East Michigan.

[Waldo]

64.34.160.92
42ms average

67.212.163.50
48ms average

72.51.32.76
80ms average

66.226.72.172
82ms average

Minnesota

[malice-tg]

64.34.160.92
New Jersey

[azisza]

Sydney Australia

72.51.32.76 = 177ms.

Currently 350ms

[Kylock]

Current Server - 40ms
#1 avg 33ms
#2 avg 24ms
#3 avg 90ms
#4 avg 97ms

This is from Michigan

I'm from Detroit Michigan -- Current for me is about 80ms

#1 avg 55
#2 avg 54
#3 avg 118
#4 avg 98

[Locksmith]

Denmark (Europe)

#1 avg: 113 ms
#2 avg: 131 ms
#3 avg: 196 ms
#4 avg: 180 ms

[Satoshi57x]

Everett, Washington USA (north of Seattle by about 30 miles)
Verizon's standard DSL service

Ran tracert a few times each to make sure.


64.34.160.92 (SB-V) (80 Ping) 20 hops

67.212.163.50 (SH) (80 Ping) 16 hops
On many run throughs half the connection timed out after it got to us.nlayer.net. Same things happens when other IPs go through there.

72.51.32.76 (SB-LA) (36 Ping) 19 hops

66.226.72.172 (AP) (40 Ping) 21 hops


Voted for the bottom 2.

[Locksmith]

Sorry, forgot to mention amount of hops.

Denmark (Europe)
Cybercity ADSL (Broadband)

#1 avg: 113 ms -> 14 hops
#2 avg: 131 ms -> 17 hops
#3 avg: 196 ms -> 22 hops
#4 avg: 180 ms -> 21 hops

[kishih]

From near Amsterdam, Netherlands, Europe

#1 avg 121 ms
#2 avg 126 ms
#3 avg 189 ms
#4 avg 168 ms

[abtabdn]

Voted for 66.226.72.172. Located in Spokane, Washington State.

[orionsune]

Clayton, North Carolina (Cable) (Home)

64.34.160.92 18ms
67.212.163.50 50ms
72.51.32.76 84ms
66.226.72.172 85ms


Raleigh, North Carolina (OC-3) (Datacenter)

64.34.160.92 46ms
67.212.163.50 33ms
72.51.32.76 85ms
66.226.72.172 65ms

Equinix, Chicago (T-3) (Dissaster Recovery Datacenter)

64.34.160.92 20ms
67.212.163.50 0.7ms <-- (the same datacenter maybe?)
72.51.32.76 60ms
66.226.72.172 69ms


Strange how the cable-modem at my house gets better replies than the datacenter at my job. Then there is that one IP in our DR datacenter getting .7ms, wondering if by coincidence that IP, 67.212.163.50, is in the same datacenter...

[ChewY]

From Denmark, Europe

160 on the top ip.
the second ip i get the same ping, but 25% packet loss.

[trio]

UK

64.34.160.92 - 117ms
67.212.163.50 - 117ms
72.51.32.76 - 232ms
66.226.72.172 - 162ms

[Panama Red]

[64.34.160.92] best for me!

Tracing route to cachens2.iad2.serverbeach.com [64.34.160.92]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms c-98-235-6-94.hsd1.pa.comcast.net [98.235.6.94]

2 * * * Request timed out.
3 9 ms 9 ms 9 ms te-1-2-ur01.levittown.pa.panjde.comcast.net [68.
86.193.17]
4 148 ms 13 ms 9 ms po-90-ur01.newtown.pa.panjde.comcast.net [68.86.
208.98]
5 11 ms 10 ms 9 ms be-65-crs01.ivyland.pa.panjde.comcast.net [68.86
.208.102]
6 9 ms 12 ms 11 ms be-40-crs01.401nbroadst.pa.panjde.comcast.net [6
8.86.208.33]
7 15 ms 14 ms 14 ms pos-1-9-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.90.13]
8 15 ms 15 ms 14 ms xe-8-3-0.edge1.Washington1.Level3.net [63.210.62
.49]
9 14 ms 14 ms 14 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
10 15 ms 16 ms 14 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
11 16 ms 17 ms 15 ms 10ge.ten1-1.wdc-sp2-cor-1.peer1.net [216.187.116
.253]
12 15 ms 19 ms 15 ms 216.187.120.238
13 15 ms 14 ms 14 ms cachens2.iad2.serverbeach.com [64.34.160.92]

trace complete.

[bigcheez]

cant trace route anything because im on my schools connection but

from arizona
1st - 83ms
2nd - 53ms
3rd - 84ms
4th - 15ms


if you pick the 1st or 3rd option ill cry, thats like a 160ms in razor's -ping and i cant look at that. id have a better connection on dfi's european server

how about we just get a central server, dallas tx, like a normal person