What do you make of these ping and traceroute stats I've obtained, going from my PC to a well-known, well-used host? Would it be right for me to describe these response times (latency) as excessive? And would you say that the problem must lie on the Internet, out beyond my exchange, rather than anywhere on my actual machine?
I've been having this problem for over a week now. After the first day of erratic acquisition of my usual websites I reported it to my ISP. They maintained there was no issue but changed their mind soon after, when a number of others complained of similar. I sent them repeated pings and tracert reports and in the end they contacted BT about it - or at least, that's the story I was given. Last Monday morning my ISP told me in an e-mail that BT had found and fixed the problem. But I myself was still having the problem. It's still ongoing, and my ISP is no longer responding to any of my results or any comments from me.
I'm on ADSL (G.Dmt). Sync'ing between my Billion 8800NL router and my exchange is stable and reasonable. It's always been okay. I run both a Mac and a Windows PC on my home network and these tests from each one give similar, alarming results.
What's your candid opinion as to where the problem lies, and can BT be pressured into exploring the offending server(s) and properly solving this issue?
As far as my memory serves me, ping delays should normally lie in the range of about 20 - 30 milliseconds, not 20 times that amount! Some of the hop delays below are amounting to 600 milliseconds or more.
Obviously, I've tried all the usual things, like clearing caches and cookies from the respective browsers.
Would or could G.dmt operation give these results if my ISP has got me on ADSL2/+ instead?
Pinging http://www.bbc.net.uk [18.104.22.168] with 32 bytes of data:
Reply from 22.214.171.124: bytes=32 time=331ms TTL=55
Reply from 126.96.36.199: bytes=32 time=338ms TTL=55
Reply from 188.8.131.52: bytes=32 time=385ms TTL=55
Reply from 184.108.40.206: bytes=32 time=388ms TTL=55
Ping statistics for 220.127.116.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 331ms, Maximum = 388ms, Average = 360ms
Tracing route to http://www.bbc.net.uk [18.104.22.168]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 432 ms 435 ms 433 ms 22.214.171.124
3 404 ms 395 ms 460 ms edge.td.vispa.net.uk [126.96.36.199]
4 564 ms 463 ms 602 ms te-8-3-203.car2.Manchester1.Level3.net [195.50.1
5 462 ms 481 ms 480 ms ae-231-3607.edge4.London1.Level3.net [188.8.131.52
6 464 ms 464 ms 425 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
7 * * * Request timed out.
8 304 ms 288 ms 261 ms ae0.er01.telhc.bbc.co.uk [184.108.40.206]
9 280 ms 284 ms 261 ms 220.127.116.11
10 282 ms 266 ms 332 ms bbc-vip111.telhc.bbc.co.uk [18.104.22.168]