Paul

Well like all things, it can depend on many factors, this is how it looks to me on my NTL connection atm;

C:\WINDOWS>ping 62.212.74.4 -t
Pinging 62.212.74.4 with 32 bytes of data:
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=40ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=27ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=26ms TTL=55
Ping statistics for 62.212.74.4:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 40ms, Average = 25ms

C:\WINDOWS>tracert 62.212.74.4
Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms W2K-PC [10.27.1.1]
2 11 ms 9 ms 10 ms 10.xxx.xxx.254
3 11 ms 8 ms 11 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46.201]
4 43 ms 7 ms 9 ms not-t2core-b-ge-wan64.inet.ntl.com [80.1.79.89]
5 13 ms 12 ms 11 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 23 ms 11 ms 11 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]
7 26 ms 15 ms 15 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 16 ms 16 ms 15 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
9 27 ms 25 ms 36 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]
10 24 ms 25 ms 24 ms ams-ix.leaseweb.nl [195.69.144.215]
11 24 ms 24 ms 25 ms gam20.gameservers.net [62.212.74.4]
Trace complete.