Augustus, can you tell from a trace route?
(this is the game server which pings 69ms from the command line yet gives pings in-game of 300 plus without fail, every time. So the fact the command line ping is decent, is a red herring.)
Tracing route to 217-14-14-189-dhcp-osl.bbse.no [217.14.14.189]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 20 ms 22 ms 20 ms lns1.uan.thn.uk.murphx.net [89.145.254.69]
3 22 ms 20 ms 20 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 21 ms 21 ms 23 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.169]
5 21 ms 21 ms 21 ms ge0-1-1.tr1.core.thn.uk.murphx.net [89.145.254.138]
6 22 ms 22 ms 21 ms xe-11-2-0-18.lon10.ip4.tinet.net [213.200.77.9]
7 23 ms 21 ms 21 ms 213.200.77.234
8 62 ms 62 ms 62 ms bahnhof.ar1.arn3.gblx.net [64.214.141.10]
9 67 ms 64 ms 64 ms sto-cr3.ore-cr1.bahnhof.net [85.24.151.197]
10 69 ms 69 ms 69 ms ore-cr1.osl-rr1.bahnhof.net [85.24.151.17]
11 68 ms 67 ms 68 ms pronea-ve-gw.bahnhof.net [85.24.153.57]
12 69 ms 68 ms 69 ms 217-14-14-189-dhcp-osl.bbse.no [217.14.14.189]
Trace complete.
(this is the game server which pings 69ms from the command line yet gives pings in-game of 300 plus without fail, every time. So the fact the command line ping is decent, is a red herring.)

