Pings & G.INP

[gymno]

Here's another good one i found, confirming it can't be my line or exchange.
Been pinging ccpgames.com (London) on & off for 2 days now & it's always:

56 bytes from 87.237.39.90: icmp_seq=0 ttl=250 time=15.1 ms
56 bytes from 87.237.39.90: icmp_seq=1 ttl=250 time=15.7 ms
56 bytes from 87.237.39.90: icmp_seq=2 ttl=250 time=16.1 ms
56 bytes from 87.237.39.90: icmp_seq=3 ttl=250 time=15.4 ms

[gymno]

Hmm all change again today.

bbc.co.uk is down 12ms, so back to normal now:
56 bytes from 212.58.241.131: icmp_seq=0 ttl=248 time=15.9 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=248 time=15.3 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=248 time=15.3 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=248 time=14.6 ms

google.com is up 6ms, 12ms overall now:
56 bytes from 173.194.34.130: icmp_seq=0 ttl=59 time=26.6 ms
56 bytes from 173.194.34.130: icmp_seq=1 ttl=59 time=27.0 ms
56 bytes from 173.194.34.130: icmp_seq=2 ttl=59 time=26.3 ms
56 bytes from 173.194.34.130: icmp_seq=3 ttl=59 time=26.6 ms

And ccpgames.com is up 12ms:
56 bytes from 87.237.39.90: icmp_seq=0 ttl=250 time=27.3 ms
56 bytes from 87.237.39.90: icmp_seq=1 ttl=250 time=26.9 ms
56 bytes from 87.237.39.90: icmp_seq=2 ttl=250 time=27.7 ms
56 bytes from 87.237.39.90: icmp_seq=3 ttl=250 time=26.7 ms

Results are consistent & repeatable.

[gymno]

Oops double post

[gymno]

The phenomenon is still occurring.

Take 6 random ip addresses.
At present they may be:
Address 1 - 15ms.
Address 2 - 15ms.
Address 3 - 21ms.
Address 4 - 21ms.
Address 5 - 27ms.
Address 6 - 27ms.
And that's how things will stay 24/7.

If i resync the line for a new ip address, or even if i don't & sky merely give me a new ip address without a resync, things will go something like this:

Address 1 - 27ms.
Address 2 - 21ms.
Address 3 - 15ms.
Address 4 - 27ms.
Address 5 - 15ms.
Address 6 - 21ms.

[gymno]

This issue appears to have been fixed, after some maintenance work done by sky.

bbc.co.uk
56 bytes from 212.58.241.131: icmp_seq=0 ttl=248 time=15.3 ms
ccpgames.com
56 bytes from 87.237.39.90: icmp_seq=0 ttl=250 time=15.4 ms
google.com
56 bytes from 173.194.34.78: icmp_seq=0 ttl=59 time=16.3 ms
random from reverse traceroute
56 bytes from 141.136.111.245: icmp_seq=0 ttl=62 time=15.8 ms
random from reverse traceroute
56 bytes from 4.69.137.73: icmp_seq=0 ttl=56 time=15.5 ms
random from reverse traceroute
56 bytes from 4.69.153.134: icmp_seq=0 ttl=57 time=15.5 ms

[gymno]

Spoke too soon.

bbc.co.uk
56 bytes from 212.58.241.131: icmp_seq=0 ttl=248 time=15.2 ms
ccpgames.com
56 bytes from 87.237.39.90: icmp_seq=0 ttl=250 time=26.8 ms
google.com
56 bytes from 173.194.34.78: icmp_seq=0 ttl=59 time=16.6 ms
random from reverse traceroute
56 bytes from 141.136.111.245: icmp_seq=0 ttl=62 time=21.0 ms
random from reverse traceroute
56 bytes from 4.69.137.73: icmp_seq=0 ttl=56 time=21.5 ms
random from reverse traceroute
56 bytes from 4.69.153.134: icmp_seq=0 ttl=57 time=21.2 ms

[gymno]

Strange blip back to normal at 5:45pm.



Since mid january when this weirdness started, latency would only ever change after being allocated a new ip address.
Now, since the major south east outage sky experienced a day or so ago, things seem far more interesting.

[gymno]

For anyone interested, this is still happening.

[gymno]

I just thought i'd post this final illustration of what's going on & then leave this thread until something significant changes.

This is up to 1pm today when i received a new ip address:
(Please ignore the variations - others experienced a similar phenomena with their monitors last night).


And this is how it's been since:


So proper evidence there of a jump from 15ms to 27ms.
Meanwhile, pings to other ip addresses have reduced by 6 or 12ms...

[Scubbie]

Stranger and stranger.

30ms is 'normal' for Sky ADSL Broadband, so even 27ms is technically alright.

15ms was exceptional.