Does anybody know the current IP addresses of the servers? I have just abandoned all hope when I experienced this today: Just to be sure, I checked my connection, getting good local pings and good pings to germany so not my end.
Yeah, I had the same ping problems. It went up to 45k at one point. I gave up when I was sent back to the warpgate after being in a gal over an objective four regions away.
Cobalt actually... How did you get the IP? The ones that have previously been published seem to be wrong.
Ah, either way, it looks like this is what you want to trace as you can't go past it: sony.customer.am3.eu.equinix.net (5.175.82.94)
Oh not to worry, I know perfectly well how to check my connection - I was just not sure of the server IP addresses. It gets displayed in Windows with a resolved address (amspsn-liv-gw04.planetside2.com), but for some reason whilst they have a PTR record there is no A record. Go figure. Anyway, for the benefit of the thread. traceroute to 69.174.194.165 (69.174.194.165), 30 hops max, 60 byte packets 1 xxxxxxxxxxxxxxxxxxx 0.220 ms 0.232 ms 0.310 ms 2 losubs.subs.dsl3.th-lon.zen.net.uk (62.3.84.25) 8.268 ms 8.277 ms 8.335 ms 3 ge-2-1-0-131.cr2.th-lon.zen.net.uk (62.3.84.253) 8.275 ms 8.307 ms 8.427 ms 4 linx-224.bg2.ld2.eu.equinix.net (195.66.224.187) 9.653 ms 9.754 ms 9.616 ms 5 po3.bg1.ld2.eu.equinix.net (80.69.1.221) 9.238 ms 9.670 ms 9.548 ms 6 po9-1405.bg1.am1.eu.equinix.net (89.187.106.154) 16.003 ms 16.347 ms 16.336 ms 7 po7.bg1.am3.eu.equinix.net (94.103.16.86) 16.326 ms 16.197 ms 16.194 ms 8 po2.bg2.am3.eu.equinix.net (94.103.16.122) 16.349 ms 16.463 ms 16.415 ms 9 sony.customer.am3.eu.equinix.net (5.175.82.94) 14.992 ms 14.687 ms 14.881 ms 10 * * * You won't get a response past the edge server.
Did you let it go for about 10-15 hops after it started timing out? For Example: Tracing route to amspsn-liv-gw01.planetside2.com [69.174.194.165] over a maximum of 30 hops: 1 <1 ms <1 ms 1 ms car1.napshome.local [10.0.1.3] 2 4 ms 5 ms 6 ms gpon-local.xlr8bb.com [10.40.0.1] 3 3 ms 2 ms 2 ms gpon-local.xlr8bb.com [172.16.1.2] 4 9 ms 11 ms 10 ms 38.122.47.121 5 8 ms 17 ms 10 ms te0-7-0-5.ccr21.atl04.atlas.cogentco.com [154.54.85.234] 6 7 ms 10 ms 10 ms level3.atl04.atlas.cogentco.com [154.54.12.138] 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 112 ms 103 ms 106 ms ae-238-3614.edge6.amsterdam1.level3.net [4.69.162.246] 15 112 ms 106 ms 107 ms sony-online.edge6.amsterdam1.level3.net [212.72.46.190] 16 104 ms 107 ms 106 ms amspsn-liv-gw01.planetside2.com [69.174.194.165] Trace complete.
That only works for ICMP instead of UDP traces, the latter being more useful for game traffic! arthur:~ # traceroute -I 69.174.194.168 traceroute to 69.174.194.168 (69.174.194.168), 30 hops max, 60 byte packets 1 xxxxxxxxxxxxxxxx 0.239 ms 0.308 ms 0.391 ms 2 losubs.subs.dsl3.th-lon.zen.net.uk (62.3.84.25) 8.316 ms 8.322 ms 8.407 ms 3 ge-0-0-0-117.cr2.th-lon.zen.net.uk (62.3.84.197) 8.649 ms 8.783 ms 8.786 ms 4 linx-224.bg2.ld2.eu.equinix.net (195.66.224.187) 9.814 ms 10.009 ms 10.435 ms 5 po3.bg1.ld2.eu.equinix.net (80.69.1.221) 10.085 ms 10.505 ms 10.506 ms 6 po9-1405.bg1.am1.eu.equinix.net (89.187.106.154) 44.121 ms 44.005 ms 44.199 ms 7 po7.bg1.am3.eu.equinix.net (94.103.16.86) 17.369 ms 16.211 ms 16.262 ms 8 po2.bg2.am3.eu.equinix.net (94.103.16.122) 16.831 ms 16.655 ms 16.553 ms 9 sony.customer.am3.eu.equinix.net (5.175.82.94) 14.962 ms 15.144 ms 15.032 ms 10 amspsn-liv-gw04.planetside2.com (69.174.194.168) 15.866 ms 15.605 ms 15.787 ms
Neither are "more useful for game traffic", they both give the same information notice your latency are identical, only sometimes one is blocked and other is not, as you found out.
