15ms to London from Lancashire doesn't seem entirely unreasonable. I reckon you're on fastpath already but the first hop visible on the traceroute isn't a local one.

I get around 6ms first hop on Infinity in London - so assuming you were the same, that'd be about 9ms from Lancashire to London. I think it makes sense?

Edited by deleted (Thu 30-Aug-12 15:08:18)

Ah, I see now, so what makes my ping 7ms higher than other users? The routing? The MSAN? I wouldn't of thought the distance of fibre would add any ping, well at least within the UK. I suspect if it was the MSAN then changing ISP would make a difference.

As the link says, any instability on a "fastpath" line will result in increased latency.

I remember pinging bbc 5-7ms from college a couple of years ago and that's about a mile from here.

Very roughly (looking at a map) the distance from Lancashire to London looks about the same as the distance from London to Paris. London to Paris latency is a touch under 10ms? So 15ms to London for you seems about right, I think.

In reply to a post by Anonymous:

I remember pinging bbc 5-7ms from college a couple of years ago and that's about a mile from here.

I can't speak for a few years ago but a traceroute from a VPS in London to www.lancs.ac.uk shows roughly 8-9ms from London to Lancs

I know someone who lives in Durham and he pings 9ms to the bbc so I really can't see how the distance makes a difference.

Everyone has focused on the fibre and is ignoring the switches that link all the bits of fibre, these are where most of the latency impact is and Sky may not even be showing a big portion of their network.

Hopefully someone on FTTC who gets a ping of around 8-9ms could check to see if it says the depth is 1 (D: 1).

least how it works on sky if the cabinet detects you line working perfectly with no errors it will love you over to fastpath.

Sky can't change it, or even check it directly, found this out in passing when talking to the sky network team to try and resolve a speed issue problem