I assume if it is a opendns rerouting thing, that eventually i will be back on the London server?

Pretty sure when ive done traceroutes to bbc before it hasnt gone to "ams1.vrsn.net" where the problem seems to be

Those two tracerts have essentially the same latency. (2ms difference). A high point in the middle of one indicates a router that is giving pings a low priority compared to data packets.

It's a high that then maintains the height for subsequent hops that points to a slow/congested router.

Edited by RobertoS (Tue 01-Dec-15 21:52:50)

BBC will have completely different routes generally, probably via private peering or over Linx or similar due to massive amounts of traffic. I can't tell as I don't have access to a native TT connection.

It may go back to the UK but it is controlled by OpenDNS mainly and to a lesser extent Talk Talk but either can influence traffic as they see fit.

Matt

Edited by uno (Tue 01-Dec-15 21:53:29)

Is there any pingtest that tests using data packets, rather than ICMP to give a more accurate result if a router is giving low priority to pings?

Although maybe the BMQ does this hence the pings are fine

BQM is ICMP echo

Probably not affected as the ping box is in a data centre in London

Ah thanks. Strange my traceroute of the bbc goes through a server in London, then to Amsterdam then back to BBC HQ is London again. Seems a long way around

Edit: Seems it must be some routing issue as google pings are back to normal. BBC still high but probably that pesky Amsterdam server

Edited by bobble_bob (Tue 01-Dec-15 23:26:51)