Would some kind soul(s) trace / pathping this for me from their Idnet connections?
83.142.228.117
Am thinking of migrating in and this is my gaming clan's dedicated server, so it needs a good route ::)
Would also be interested into how people find IDnet to jolt, gameservers.net, multiplay etc etc etc
Thanks!
Thin
Tracing route to 83.142.228.117 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 * 846 ms 58 ms 212.69.63.41
3 27 ms 24 ms 24 ms 212.69.63.10
4 * * 25 ms 213.232.64.54
5 * * * Request timed out.
6 * 27 ms 29 ms 217.239.38.242
7 25 ms 26 ms * 217.239.39.230
8 * 26 ms * 217.6.48.238
9 * * * Request timed out.
10 26 ms 24 ms 26 ms 83.142.228.117
This is a trace to my fave CoD2 server, strange how 2 are fine and the other is cr*p.
Tracing route to 195.20.109.103 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 26 ms 23 ms 23 ms 212.69.63.41
3 29 ms 25 ms 27 ms 212.69.63.10
4 25 ms 25 ms 27 ms 193.203.5.134
5 28 ms 25 ms 24 ms 62.249.255.186
6 28 ms 26 ms 25 ms 217.146.81.254
7 26 ms 25 ms 24 ms 195.20.109.103
Tracing route to jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 25 ms 24 ms 24 ms 212.69.63.41
3 24 ms 27 ms 28 ms 212.69.63.10
4 56 ms 51 ms 53 ms 193.203.5.14
5 25 ms 24 ms 25 ms 62.72.137.9
6 25 ms 25 ms 24 ms 62.72.140.14
7 25 ms 25 ms 26 ms 212.241.241.14
8 27 ms 26 ms 28 ms 82.133.85.65
Cheers. I'd have thought that the hops not returning a response just don't reply to ICMP or give it a very low priority? - otherwise that looks pretty good to me
Have some pings on me :laugh:
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=25ms TTL=56
Reply from 83.142.228.117: bytes=32 time=25ms TTL=56
Reply from 83.142.228.117: bytes=32 time=25ms TTL=56
Reply from 83.142.228.117: bytes=32 time=28ms TTL=56
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 28ms, Average = 25ms
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=30ms TTL=56
Reply from 83.142.228.117: bytes=32 time=26ms TTL=56
Reply from 83.142.228.117: bytes=32 time=24ms TTL=56
Reply from 83.142.228.117: bytes=32 time=30ms TTL=56
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 30ms, Average = 27ms
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=28ms TTL=56
Reply from 83.142.228.117: bytes=32 time=25ms TTL=56
Reply from 83.142.228.117: bytes=32 time=25ms TTL=56
Reply from 83.142.228.117: bytes=32 time=33ms TTL=56
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 33ms, Average = 27ms
Here's some of mine to the same address;
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=16ms TTL=57
Reply from 83.142.228.117: bytes=32 time=17ms TTL=57
Reply from 83.142.228.117: bytes=32 time=18ms TTL=57
Reply from 83.142.228.117: bytes=32 time=17ms TTL=57
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 18ms, Average = 17ms
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=18ms TTL=57
Reply from 83.142.228.117: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 83.142.228.117: bytes=32 time=17ms TTL=57
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=18ms TTL=57
Reply from 83.142.228.117: bytes=32 time=18ms TTL=57
Reply from 83.142.228.117: bytes=32 time=18ms TTL=57
Reply from 83.142.228.117: bytes=32 time=17ms TTL=57
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms
;D
Tracing route to 83.142.228.117 over a maximum of 30 hops
1 77 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 31 ms 17 ms 13 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
3 14 ms 13 ms 13 ms 212.69.63.10
4 14 ms 13 ms 13 ms x-s-1.lon1.arbinet.net [213.232.64.54]
5 * * * Request timed out.
6 226 ms 128 ms 16 ms 217.239.38.242
7 14 ms 13 ms 13 ms 217.239.39.230
8 17 ms 16 ms 34 ms 217.6.48.238
9 14 ms 14 ms 15 ms ge-1-21_22.kit.sov.lon.rapidswitch.com [87.117.2
14.22]
10 14 ms 12 ms 12 ms 83.142.228.117
Trace complete.
Pinging 83.142.228.117 with 32 bytes of data:
Reply from 83.142.228.117: bytes=32 time=13ms TTL=56
Reply from 83.142.228.117: bytes=32 time=11ms TTL=56
Reply from 83.142.228.117: bytes=32 time=12ms TTL=56
Reply from 83.142.228.117: bytes=32 time=13ms TTL=56
Ping statistics for 83.142.228.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 13ms, Average = 12ms
Much appreciated all - doesn't look like I should have any problems by the looks of those :D