tracert -d 217.146.93.31
Tracing route to 217.146.93.31 over a maximum of 30 hops
1 1 ms <10 ms <10 ms 192.168.1.1
2 40 ms 42 ms 41 ms 62.3.83.20
3 41 ms 42 ms 42 ms 62.3.80.233
4 41 ms 41 ms 41 ms 193.189.130.26
5 53 ms 50 ms 52 ms 194.117.136.217
6 50 ms 52 ms 51 ms 194.117.136.178
7 51 ms 48 ms 51 ms 194.117.136.150
8 51 ms 72 ms 50 ms 194.117.136.166
9 133 ms 242 ms 211 ms 194.117.136.197
10 53 ms 195 ms 199 ms 194.117.147.66
11 117 ms 207 ms 218 ms 217.146.81.254
12 50 ms 49 ms 49 ms 217.146.93.31
Trace complete.
ping 217.146.93.31
Pinging 217.146.93.31 with 32 bytes of data:
Reply from 217.146.93.31: bytes=32 time=49ms TTL=120
Reply from 217.146.93.31: bytes=32 time=48ms TTL=120
Reply from 217.146.93.31: bytes=32 time=47ms TTL=120
Reply from 217.146.93.31: bytes=32 time=49ms TTL=120
Ping statistics for 217.146.93.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 49ms, Average = 48ms
On a line with interleaving on.
In reply to:Seems to contradict what you then say:you have done the tracer route at either first thing in the morning or gone 12 at night! Sorry but it's just no reliable to do it then. Re-do the test at around 8.30pm for a true result.
In reply to:I had solid pings with Nildram of 30-40 with nildram constant no matter what time of the day



Pages in this thread:
Print Thread
deleted