I'm up near Rotherham, about 160 miles from London, and get 8 or 9 ms from BBC.co.uk

On Cerberus networks FTTP connected via Amvia:

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=8ms TTL=60
Reply from 151.101.0.81: bytes=32 time=9ms TTL=60
Reply from 151.101.0.81: bytes=32 time=8ms TTL=60
Reply from 151.101.0.81: bytes=32 time=8ms TTL=60

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 9ms, Average = 8ms

I'm in South East London (Orpington area), using TalkTalk via OpenReach.

Ping results:
[~] # ping bbc.co.uk
PING bbc.co.uk (151.101.0.81): 56 data bytes
64 bytes from 151.101.0.81: seq=0 ttl=59 time=2.449 ms
64 bytes from 151.101.0.81: seq=1 ttl=59 time=2.263 ms
64 bytes from 151.101.0.81: seq=2 ttl=59 time=2.173 ms
64 bytes from 151.101.0.81: seq=3 ttl=59 time=2.127 ms

[~] # ping apple.com
PING apple.com (17.253.144.10): 56 data bytes
64 bytes from 17.253.144.10: seq=0 ttl=59 time=2.684 ms
64 bytes from 17.253.144.10: seq=1 ttl=59 time=2.106 ms
64 bytes from 17.253.144.10: seq=2 ttl=59 time=2.621 ms
64 bytes from 17.253.144.10: seq=3 ttl=59 time=1.878 ms

Looks like you’re hitting their CDN’s. Try the nytimes.com. It will ping faster than the beeb 🤣

Surely info about your current provider is useful to others too Paul ?

In reply to a post by Pheasant:

Looks like you’re hitting their CDN’s. Try the nytimes.com. It will ping faster than the beeb 🤣

Surely the point of CDN's is that they're 'local' caches of the content to be delivered...so they *should* be low latency (assuming that one's DNS setup picks up the relevant 'local' IP)

Anyway...not so fast on this one...

[~] # ping nytimes.com
PING nytimes.com (151.101.193.164): 56 data bytes
64 bytes from 151.101.193.164: seq=0 ttl=59 time=3.151 ms
64 bytes from 151.101.193.164: seq=1 ttl=59 time=3.262 ms
64 bytes from 151.101.193.164: seq=2 ttl=59 time=3.088 ms
64 bytes from 151.101.193.164: seq=3 ttl=59 time=2.994 ms

In reply to a post by E1234TJ:

What is the lowest latency openreach FTTP ISP?

There is no single answer to that question.
Different backhaul networks can and do have lower latency in 1 City compared to another city.
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.

Up here in Edinburgh I get a minimum 13.9ms to London via BT Wholesale (over OpenReach FTTP).
On the same line I get 16.1ms to London over Talktalk backhaul.
I've no personal experience of Sky or Vodafones networks from my location.

There is likely less of a difference in latency between backhaul networks for anyone in London.

Here is mine gfast with talktalk business (unchainedisp)

Microsoft Windows [Version 10.0.22000.282]
(c) Microsoft Corporation. All rights reserved.

C:\Users\PC>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=8ms TTL=59
Reply from 151.101.0.81: bytes=32 time=8ms TTL=59
Reply from 151.101.0.81: bytes=32 time=8ms TTL=59
Reply from 151.101.0.81: bytes=32 time=8ms TTL=59

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 8ms, Average = 8ms

C:\Users\PC>

This is what I get on Community Fibre at the moment (I am just over 5km birds eye from Telehouse)

Ping

ping -4 bbc.co.uk

Pinging bbc.co.uk [151.101.64.81] with 32 bytes of data:
Reply from 151.101.64.81: bytes=32 time=1ms TTL=59
Reply from 151.101.64.81: bytes=32 time=1ms TTL=59
Reply from 151.101.64.81: bytes=32 time=1ms TTL=59
Reply from 151.101.64.81: bytes=32 time=1ms TTL=59

Ping statistics for 151.101.64.81:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Trace Route

tracert -4 bbc.co.uk

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

  1    <1 ms    <1 ms    <1 ms  yazoo [192.168.2.253]
  2     1 ms     1 ms     1 ms  x.x.x.x
  3     2 ms     2 ms     2 ms  94.177.138.59
  4     2 ms     1 ms     1 ms  94.177.138.170
  5     1 ms     1 ms     1 ms  195.66.225.91
  6     1 ms     1 ms     1 ms  151.101.0.81

Trace complete.

But if I recall I got about the same with BT when I last did a test on it.

Paul

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

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 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.

In reply to a post by Zarjaz:

Surely info about your current provider is useful to others too Paul ?

Yeah, I posted a Ping and Traceroute to the BBC Site in a previous reply.

As my sig (assuming people have it display it) says, I am now with Community Fibre on their GIGAFAST package, along with TBB IPv4, IPv6 and Ookla Speedtest Results along with TBB BQM.

I still have BT (MikroTik Tik Router not connected to anything) but just waiting for the contract to run out for the broadband and will then only use BT as a Phone service until we get around to port the number.

Ping to BBC Site

ping -4 bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=1ms TTL=59
Reply from 151.101.0.81: bytes=32 time=1ms TTL=59
Reply from 151.101.0.81: bytes=32 time=1ms TTL=59
Reply from 151.101.0.81: bytes=32 time=1ms TTL=59

Ping statistics for 151.101.0.81:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Traceroute to BBC Site

tracert -4 bbc.co.uk

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

  1     1 ms    <1 ms    <1 ms  yazoo [192.168.2.253]
  2     1 ms     1 ms     1 ms  x.x.x.x
  3     1 ms     2 ms     1 ms  94.177.138.59
  4     1 ms     2 ms     1 ms  94.177.138.170
  5    <1 ms     1 ms    <1 ms  195.66.225.91
  6     1 ms     1 ms     1 ms  151.101.0.81

Trace complete.

---

Ping to TBB BQM Server

ping pingbox1.thinkbroadband.com

Pinging pingbox1.thinkbroadband.com [80.249.99.164] with 32 bytes of data:
Reply from 80.249.99.164: bytes=32 time=1ms TTL=57
Reply from 80.249.99.164: bytes=32 time=1ms TTL=57
Reply from 80.249.99.164: bytes=32 time=1ms TTL=57
Reply from 80.249.99.164: bytes=32 time=1ms TTL=57

Ping statistics for 80.249.99.164:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Traceroute to TBB BQM Server

tracert pingbox1.thinkbroadband.com

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  yazoo [192.168.2.253]
  2     1 ms     1 ms     1 ms  x.x.x.x
  3     1 ms     2 ms     2 ms  94.177.138.59
  4     1 ms     1 ms     2 ms  94.177.138.170
  5     1 ms     1 ms     1 ms  185.59.125.153
  6     1 ms     1 ms     1 ms  po11-13.bdr-rt3.thdo.ncuk.net [80.249.97.22]
  7     1 ms     1 ms    <1 ms  po4-31.core-rs4.thdo.ncuk.net [80.249.97.85]
  8     1 ms     1 ms     1 ms  pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

I can do more tests if anyone wants any more information.

Paul