anyone?
---------- Post added at 19:33 ---------- Previous post was at 18:27 ----------
tracert
www.bbc.co.uk
Tracing route to
www.bbc.net.uk [212.58.253.72]
over a maximum of 30 hops:
1 79 ms 89 ms 97 ms glfd-bam-1.inet.ntl.com [194.145.148.4]
2 68 ms 64 ms 62 ms glfd-t2core-b-ge-wan63.inet.ntl.com [195.182.179
.153]
3 77 ms 79 ms 85 ms gfd-bb-b-so-530-0.inet.ntl.com [213.105.174.157]
4 85 ms 81 ms 81 ms redb-ic-1-as0-0.inet.ntl.com [62.253.185.78]
5 91 ms 106 ms 89 ms 212.58.238.189
6 71 ms 82 ms 77 ms 212.58.238.133
7 107 ms 121 ms 98 ms fe0-0.rt0-frontpost.prodgw.bbc.co.uk [212.58.239
.222]
8 77 ms 87 ms 93 ms www3.cwwtf.bbc.co.uk [212.58.253.72]
Trace complete.
Pinging
www.bbc.net.uk [212.58.224.115] with 32 bytes of data:
Reply from 212.58.224.115: bytes=32 time=60ms TTL=247
Reply from 212.58.224.115: bytes=32 time=89ms TTL=247
Reply from 212.58.224.115: bytes=32 time=87ms TTL=247
Reply from 212.58.224.115: bytes=32 time=70ms TTL=247
Ping statistics for 212.58.224.115:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 89ms, Average = 76ms
That might help identify the problem.