![]() |
The good tracerts!
I dont see many positive posts on this forum so i thought i might spread some joy :). Dont be shy show us yours :P.
(yes my ntl is in full power at 5am :p) tracert posting time! Tracing route to jolt.co.uk [82.133.85.65] over a maximum of 30 hops: 1 6 ms 7 ms 7 ms 10.153.183.254 2 10 ms 8 ms 7 ms nott-t2cam1-b-v129.inet.ntl.com [80.4.47.229] 3 15 ms 8 ms 9 ms nott-t2core-b-ge-wan71.inet.ntl.com [80.1.79.185] 4 11 ms 10 ms 10 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37] 5 15 ms 16 ms 20 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14] 6 14 ms 13 ms 15 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86] 7 15 ms 13 ms 14 ms lon1-10.nildram.net [213.208.106.169] 8 14 ms 14 ms 24 ms 84.12.225.130 9 14 ms 13 ms 13 ms jolt-gw.nildram.net [195.149.20.126] 10 14 ms 13 ms 16 ms 82.133.85.65 Trace complete. C:\Documents and Settings\Omars>ping jolt.co.uk Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data: Reply from 82.133.85.65: bytes=32 time=13ms TTL=54 Reply from 82.133.85.65: bytes=32 time=13ms TTL=54 Reply from 82.133.85.65: bytes=32 time=14ms TTL=54 Reply from 82.133.85.65: bytes=32 time=15ms TTL=54 Ping statistics for 82.133.85.65: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 15ms, Average = 13ms |
Re: The good tracerts!
these are my results from Swansea via a wireless router :)
Code:
Tracing route to jolt.co.uk [82.133.85.65] |
Re: The good tracerts!
Tracing route to jolt.co.uk [82.133.85.65] over a maximum of 30 hops:
1 <10 ms 1 ms <10 ms XX.XX.XX.XX 2 7 ms 7 ms 8 ms 10.16.32.1 3 14 ms 7 ms 14 ms bagu-t2cam1-b-ge-wan53-124.inet.ntl.com [80.5.162.225] 4 8 ms 7 ms 8 ms bagu-t2core-b-ge-wan64.inet.ntl.com [80.5.161.141] 5 9 ms 9 ms 8 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29] 6 9 ms 9 ms 9 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185] 7 13 ms 15 ms 14 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238] 8 14 ms 14 ms 15 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78] 9 15 ms 17 ms 15 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86] 10 16 ms 17 ms 18 ms lon1-10.nildram.net [213.208.106.169] 11 16 ms 16 ms 16 ms 84.12.225.130 12 15 ms 16 ms 16 ms jolt-gw.nildram.net [195.149.20.126] 13 15 ms 16 ms 18 ms 82.133.85.65 Trace Complete. Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data: Reply from 82.133.85.65: bytes=32 time=15ms TTL=51 Reply from 82.133.85.65: bytes=32 time=16ms TTL=51 Reply from 82.133.85.65: bytes=32 time=16ms TTL=51 Reply from 82.133.85.65: bytes=32 time=15ms TTL=51 Ping statistics: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Minimum = 15ms, Maximum = 16ms, Average = 15ms damn stupid thing routing me through leeds costs me an extra 2/3ms :) |
Re: The good tracerts!
Sorry-no offence, but there's no disccusion going on here, & posting Trace Routes is simply pointless unless soneone has a problem.
The thread will be closed/removed shortly. |
| All times are GMT. The time now is 23:58. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum