I just looked at all the pings being shown here and me with my connection in cambridgeshire its like being in another country.

ping -t bbc.co.uk

Pinging bbc.co.uk [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=49ms TTL=57
Reply from 151.101.128.81: bytes=32 time=64ms TTL=57
Reply from 151.101.128.81: bytes=32 time=42ms TTL=57
Reply from 151.101.128.81: bytes=32 time=50ms TTL=57
Reply from 151.101.128.81: bytes=32 time=56ms TTL=57
Reply from 151.101.128.81: bytes=32 time=41ms TTL=57
Reply from 151.101.128.81: bytes=32 time=41ms TTL=57
Reply from 151.101.128.81: bytes=32 time=48ms TTL=57
Reply from 151.101.128.81: bytes=32 time=42ms TTL=57
Reply from 151.101.128.81: bytes=32 time=46ms TTL=57
Reply from 151.101.128.81: bytes=32 time=49ms TTL=57
Reply from 151.101.128.81: bytes=32 time=45ms TTL=57

Ping statistics for 151.101.128.81:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 64ms, Average = 47ms


added trace

Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

1 3 ms 3 ms 4 ms TP-SHARE [10.0.0.1]
2 * * * Request timed out.
3 44 ms 43 ms 36 ms nrth-core-2a-xe-1001-0.network.virginmedia.net [80.1.202.173]
4 * * * Request timed out.
5 39 ms 62 ms 46 ms eislou2-ic-3-ae0-0.network.virginmedia.net [94.174.238.226]
6 48 ms 53 ms 43 ms 157.52.127.6
7 38 ms 42 ms 48 ms 151.101.0.81

Trace complete.

Edited by RR_The_IT_Guy (Mon 01-Nov-21 23:06:16)

I switched from VM to BT.

bbc averaged 22-25ms on VM.

Now:
PING bbc.co.uk (151.101.192.81): 56 data bytes
64 bytes from 151.101.192.81: seq=0 ttl=58 time=15.506 ms
64 bytes from 151.101.192.81: seq=1 ttl=58 time=15.580 ms
64 bytes from 151.101.192.81: seq=2 ttl=58 time=15.492 ms
64 bytes from 151.101.192.81: seq=3 ttl=58 time=15.526 ms
64 bytes from 151.101.192.81: seq=4 ttl=58 time=15.554 ms

--- bbc.co.uk ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 15.492/15.531/15.580 ms

In reply to a post by Pheasant:

Yes precisely. The CDNs are exceedingly optimised for that function.

Agreed.

In reply to a post by Pheasant:

In your pings above to bbc.co.uk and nytimes.com you're actually hitting Fastly's CDN (151.101.xxx.yyy) in both cases. From where I am, the times to both is effectively the same, and nytimes.com content on average (at the moment) is slightly faster (1.254 ms) than the beeb (1.278 ms) - but they are coming from the same delivery network (they had that rather 'spectacular' outage back in June..the 'OMG the internet is broken' outage)

I was about to say that they are via AS54113 - Fastly I just use those sites when others are using them to compare.
And yeah they was the exact same for both sites and so does twitch.tv

In reply to a post by Pheasant:

I don't know about the OP, but the folks that typically obsess over broadband ping times are invariably gamers. So they're looking at CDN perhaps where games and patches are hosted for download, but also standalone / independent servers etc often or not outside of the major CDN's and located far and wide, not just in Slough and the Docklands.

While I game a lot online and also do stream stuff now and then, latency doesn't need to be super low, but more of a stable one, I get about 8ms when I play on World of Warcraft EU Servers, so its fine for my needs.

Paul

In reply to a post by RR_The_IT_Guy:

I just looked at all the pings being shown here and me with my connection in cambridgeshire its like being in another country.

It's your provider rather than your county. Elon can get broadband from outer space in faster time

In reply to a post by PaulKirby:

... latency doesn't need to be super low, but more of a stable one

Agree. An often overlooked but very important signifier of connection quality and consistency, especially for all real time apps.

In reply to a post by Pheasant:

In reply to a post by PaulKirby:

... latency doesn't need to be super low, but more of a stable one

Agree. An often overlooked but very important signifier of connection quality and consistency, especially for all real time apps.

Yeah, I have played an online game with 1000ms (yes 1 second ping) but it was playable due to is was a very stable 1 second ping LOL

Paul

Is it possible if you can ping these and share your results?
qosping-aws-eu-west-2.ol.epicgames.com (london)
qosping-aws-eu-central-1.ol.epicgames.com (frankfurt)

Edited by E1234TJ (Tue 02-Nov-21 00:27:56)

In reply to a post by E1234TJ:

Is it possible if you can ping these and share your results?
qosping-aws-eu-west-2.ol.epicgames.com (london)
qosping-aws-eu-central-1.ol.epicgames.com (frankfurt)

Sure. Here you are:

[~] # ping qosping-aws-eu-west-2.ol.epicgames.com
PING qosping-aws-eu-west-2.ol.epicgames.com (52.56.149.83): 56 data bytes
64 bytes from 52.56.149.83: seq=0 ttl=27 time=4.021 ms
64 bytes from 52.56.149.83: seq=1 ttl=27 time=3.995 ms
64 bytes from 52.56.149.83: seq=2 ttl=27 time=3.922 ms
64 bytes from 52.56.149.83: seq=3 ttl=27 time=3.854 ms

[~] # ping qosping-aws-eu-central-1.ol.epicgames.com
PING qosping-aws-eu-central-1.ol.epicgames.com (35.158.209.186): 56 data bytes
64 bytes from 35.158.209.186: seq=0 ttl=48 time=15.700 ms
64 bytes from 35.158.209.186: seq=1 ttl=48 time=15.779 ms
64 bytes from 35.158.209.186: seq=2 ttl=48 time=17.364 ms
64 bytes from 35.158.209.186: seq=3 ttl=48 time=17.167 ms

They’re very solid results. I’ll post up some comparators.

In reply to a post by j0hn83:

…
BT Wholesale might have lower latency than Talktalk in City A but higher in City B.

In general though BT Wholesale has 1 of the lowest latencies over OpenReach.
Much of Talktalks backhaul network daisy chains from exchange to exchange, adding distance and latency.
…
There is likely less of a difference in latency between backhaul networks for anyone in London.

That was pretty much my experience moving from a BTW backed (Cerberus) to TTB - around a 1 to 2ms increase in baseline ping. Which for all intents makes no odds.