Quote:
|
Originally Posted by pem
It's ok from Nottingham but I take a totally different route.
From that trace it looks a little suspect on the NTL backbone, after hop 5. Perhaps JANoob could have a look for you - if he's around atm.  |
Tracert from another reading(ish) user...
Tracing route to bbc.co.uk [212.58.228.154]
over a maximum of 30 hops:
1 13 ms 18 ms 13 ms 10.152.103.254
2 15 ms 40 ms 34 ms rdng-t2cam1-b-ge95.inet.ntl.com [62.253.122.145]
3 10 ms 10 ms 15 ms winn-t2core-b-ge-wan61.inet.ntl.com [62.253.121.129]
4 10 ms 13 ms 13 ms winn-t2core-a-v99.inet.ntl.com [62.253.121.13]
5 10 ms 11 ms 15 ms win-bb-a-so-200-0.inet.ntl.com [62.253.184.113]
6 13 ms 11 ms 35 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
7 12 ms 15 ms 29 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
8 12 ms 15 ms 14 ms 212.58.239.217
9 23 ms 20 ms 13 ms pos6-0.rt1.mh.bbc.co.uk [212.58.239.231]
10 13 ms 17 ms 38 ms bogons.mh.bbc.co.uk [212.58.228.154]
Trace complete.
using same route it would appear - maybe they fixed it ....