Openreach FTTP Ping

From where, to where? Openreach get your FTTP connection back to a handover exchange and that's it. If an ISP put their equipment next door to that exchange and hosted a Speedtest server then your ping would be 1ms or lower.
 
I think 7-8ms is satisfactory

Mines come down over the year and with some internal changes 4.5 is the best I can get currently

Code: 
root@r1:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=120 time=4.505 ms
64 bytes from 8.8.8.8: seq=1 ttl=120 time=4.740 ms
64 bytes from 8.8.8.8: seq=2 ttl=120 time=4.562 ms
64 bytes from 8.8.8.8: seq=3 ttl=120 time=4.625 ms
64 bytes from 8.8.8.8: seq=4 ttl=120 time=4.593 ms
64 bytes from 8.8.8.8: seq=5 ttl=120 time=4.698 ms
64 bytes from 8.8.8.8: seq=6 ttl=120 time=4.581 ms
64 bytes from 8.8.8.8: seq=7 ttl=120 time=4.663 ms
64 bytes from 8.8.8.8: seq=8 ttl=120 time=4.567 ms
64 bytes from 8.8.8.8: seq=9 ttl=120 time=4.733 ms
64 bytes from 8.8.8.8: seq=10 ttl=120 time=4.506 ms
^C
--- 8.8.8.8 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 4.505/4.615/4.740 ms
 
Bit of light entertainment It takes 0.3ms to my router 10ms to my backbone and a further 18ms to get to Edingburgh from Brighton
Code: 
                         My traceroute  [v0.95]
               45.92.46.33 (45.92.462025-12-03T12:11:24+0000
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                               Packets               Pings
 Host                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.88.254            0.0%    73    0.3   0.3   0.2   0.6   0.0
 2. (waiting for reply)
 3. 80.255.193.30             0.0%    72    8.1  11.6   3.8  39.9   7.0
 4. (waiting for reply)
 5. (waiting for reply)
 6. 62.254.42.174             0.0%    72   14.9  18.2  13.6  80.6   9.1
 7. (waiting for reply)
 8. 84.116.136.98             0.0%    72   16.2  21.2  10.1  94.0  14.3
 9. 129.250.66.101            0.0%    72   15.3  17.5  12.0  50.1   5.6
10. 83.231.146.135            0.0%    72   21.5  18.5  15.8  24.4   1.5
11. (waiting for reply)
12. (waiting for reply)
13. (waiting for reply)
14. 45.92.46.33               0.0%    72   28.0  27.6  25.1  33.2   1.8

Pendant Mode: RTT there and back
 
Last edited:
I get the following on an FTTP 1.6Gb line from Zen.

Code: 
Pinging bbc.co.uk [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=3ms TTL=60
Reply from 151.101.128.81: bytes=32 time=2ms TTL=60
Reply from 151.101.128.81: bytes=32 time=2ms TTL=60
Reply from 151.101.128.81: bytes=32 time=2ms TTL=60

Ping statistics for 151.101.128.81:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms
 
Ping to what exactly, and where?

The answer is similar to ‘How long is a bit of string?’ in that nobody can tell you exactly without measuring the string.

It depends on where you are pinging, what the peering and routing set-up is, the load of any link to/network between you and the destination, if they have an on-network presence or where the servers are physically located. In very broad terms, much of the UK’s hosting is done down south (it gets progressively less the further north you go until about Edinburgh, so the physical time to get packets from Glasgow to London and back is likely the biggest issue, and one you can’t do much about. The already suggested 16-18ms is probably the right kind of number in general for Google/Facebook/MS services or assuming the destinations off network, but if we are talking EU services for example, it may well be higher depending on where you are pinging, just as you may get quicker results if say Netflix has an on-network presence for your ISP (usually larger ISP’s will do this).
 
You must log in or register to reply here.
Back
Top Bottom