Long (and consistent) PING responses

[MikeFlint]

Hi,

So I've been on Sky BB for over a year. All quite fine. But for the last week or so, I've been getting really long ping responses. Download speeds are fine, it's just PING that seems long ... and I'm getting really laggy SSH sessions (which I feel is connected?)

For example, bbc:


64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=17 ttl=55 time=403 ms
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=18 ttl=55 time=275 ms
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=19 ttl=55 time=1036 ms
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=20 ttl=55 time=1030 ms
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=21 ttl=55 time=1030 ms
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=22 ttl=55 time=1030 ms
64 bytes from bbc-vip115.telhc.bbc.co.uk (212.58.244.70): icmp_seq=23 ttl=55 time=1030 ms

And a server that's just around the corner from me (literally):

64 bytes from 91.215.184.101: icmp_seq=5 ttl=54 time=1042 ms
64 bytes from 91.215.184.101: icmp_seq=6 ttl=54 time=1041 ms
64 bytes from 91.215.184.101: icmp_seq=7 ttl=54 time=1042 ms
64 bytes from 91.215.184.101: icmp_seq=8 ttl=54 time=1042 ms
64 bytes from 91.215.184.101: icmp_seq=9 ttl=54 time=1041 ms
64 bytes from 91.215.184.101: icmp_seq=10 ttl=54 time=1041 ms
64 bytes from 91.215.184.101: icmp_seq=11 ttl=54 time=1041 ms
64 bytes from 91.215.184.101: icmp_seq=12 ttl=54 time=1041 ms
64 bytes from 91.215.184.101: icmp_seq=13 ttl=54 time=1041 ms
64 bytes from 91.215.184.101: icmp_seq=14 ttl=54 time=1035 ms

What strikes me is how consistent these times are - it's almost like someone is taking a reasonable PING time and adding a second to it.

Is this something Sky could have added? I don't play games, so not on a gaming profile (I hope) - I thought that generally reduced ping times, but potentially hit download speed? Either way, I wouldn't expect a consistent >1 sec ping.

Any ideas? It's only recently started. Last year all was reasonable.

[MikeFlint]

Sorted. Clearly my router had got tired of several months of constant performance, so introduced a delay to encourage me to restart it.

Now I get:


64 bytes from bbc-vip014.cwwtf.bbc.co.uk (212.58.246.93): icmp_seq=4 ttl=56 time=36.8 ms
64 bytes from bbc-vip014.cwwtf.bbc.co.uk (212.58.246.93): icmp_seq=5 ttl=56 time=30.9 ms
64 bytes from bbc-vip014.cwwtf.bbc.co.uk (212.58.246.93): icmp_seq=6 ttl=56 time=31.3 ms
64 bytes from bbc-vip014.cwwtf.bbc.co.uk (212.58.246.93): icmp_seq=7 ttl=56 time=30.5 ms
64 bytes from bbc-vip014.cwwtf.bbc.co.uk (212.58.246.93): icmp_seq=8 ttl=56 time=30.0 ms

The classic "switching it off, then on again" works once more.