In reply to a post by Woolwich:

Why do I get timeouts? ISTR someting about using a Mac? Anyways, am I on 22 and are folk saying thats a Bad Thing?

Last login: Wed Jan 5 09:14:49 on console
woolwich@SE18 ~ % traceroute bbc.co.uk
Its still running BTW!

If your from SE18 then yes, Also check if your on Fast path or interleaving as you should be near 5ms-9ms at most, However i have problem with IXN gateways thats on the .23 / .24 even thought im in Edgware, HA8 (north london

Im also connected via BTw WBC

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

1 <1 ms <1 ms <1 ms fritz,box [192.168.178.1]
2 19 ms 18 ms 19 ms vt1.cor1.lond2.ptn.zen.net.uk [51.148.72.24]
3 19 ms 19 ms 21 ms lag-7.p1.ixn-lon.zen.net.uk [51.148.73.186]
4 21 ms 19 ms 19 ms lag-2.p1.thn-lon.zen.net.uk [51.148.73.132]
5 20 ms 19 ms 19 ms lag-1.br1.thn-lon.zen.net.uk [51.148.73.153]
6 19 ms 19 ms 24 ms netconnex-gw.zen.net.uk [82.71.254.2]
7 19 ms 18 ms 19 ms po11-13.bdr-rt3.thdo.ncuk.net [80.249.97.22]
8 19 ms 19 ms 19 ms po4-31.core-rs4.thdo.ncuk.net [80.249.97.85]
9 18 ms 18 ms 18 ms pingbox1.thinkbroadband.com [80.249.99.164]

Seems like .21 is having pocket loss or has for a few weeks so now on .22 what seems fine but ping to .22 is up and down but still under 9ms

[francis@linux ~]$ traceroute www.bbc.co.uk
traceroute to www.bbc.co.uk (212.58.233.251), 30 hops max, 60 byte packets
1 _gateway (192.168.178.1) 0.332 ms 0.567 ms 0.557 ms
2 vt1.cor2.lond1.ptn.zen.net.uk (51.148.72.22) 36.814 ms 36.944 ms 37.223 ms
3 lag-9.p2.thn-lon.zen.net.uk (51.148.73.174) 9.799 ms lag-9.p1.thn-lon.zen.net.uk (51.148.73.160) 9.532 ms lag-9.p2.thn-lon.zen.net.uk (51.148.73.174) 9.710 ms
4 lag-2.br1.thn-lon.zen.net.uk (51.148.73.167) 9.690 ms 9.819 ms lag-1.br1.thn-lon.zen.net.uk (51.148.73.153) 9.849 ms
5 82.71.254.134 (82.71.254.134) 19.961 ms 20.493 ms 20.473 ms
6 132.185.248.51 (132.185.248.51) 9.571 ms 9.345 ms 10.186 ms
7 ae11.cr02.thdow.bbc.co.uk (132.185.254.166) 9.716 ms 8.237 ms 8.731 ms
8 * * *
9 ae2.er01.lbh.bbc.co.uk (132.185.249.7) 9.730 ms 9.444 ms 9.644 ms
10 132.185.252.126 (132.185.252.126) 27.468 ms 26.768 ms 19.875 ms

Edited by francisuk25 (Sun 06-Feb-22 20:41:31)

It all sounds like Plusnet gateways about ten years ago, when they started replacing their old gateways with better, faster more modern ones. The new ones frequently creating just such a problem.

The new ones didn't even support IPv6, whereas the old ones did! (As several of us on their pathetic IPv6 trial discovered).

In reply to a post by francisuk25:

If your from SE18

No, that's an old joke but well done for spotting. Regular listeners will know I moved north of the river.

I can answer my own question about traceroute, Mac punters need the -I flag.

So:

traceroute -I bbc.co.uk
traceroute: Warning: bbc.co.uk has multiple addresses; using 151.101.192.81
traceroute to bbc.co.uk (151.101.192.81), 64 hops max, 72 byte packets
1 fritz.box (192.168.178.1) 0.986 ms 0.457 ms 0.425 ms
2 vt1.cor1.lond1.ptn.zen.net.uk (51.148.72.21) 22.788 ms 16.726 ms 16.547 ms
3 lag-8.p2.thn-lon.zen.net.uk (51.148.73.172) 16.589 ms 16.776 ms 19.365 ms
4 lag-2.br1.thn-lon.zen.net.uk (51.148.73.167) 19.543 ms 17.111 ms 16.786 ms
5 ip81-59.fastly-gw1.lonap.net (5.57.81.59) 17.116 ms 16.699 ms 16.574 ms
6 151.101.192.81 (151.101.192.81) 16.816 ms 16.309 ms 15.768 ms

and

traceroute -I pingbox1.thinkbroadband.com
traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 64 hops max, 72 byte packets
1 fritz.box (192.168.178.1) 1.149 ms 0.460 ms 0.425 ms
2 vt1.cor1.lond1.ptn.zen.net.uk (51.148.72.21) 16.811 ms 16.579 ms 16.231 ms
3 lag-8.p1.thn-lon.zen.net.uk (51.148.73.158) 17.275 ms 16.475 ms 16.628 ms
4 lag-1.br1.thn-lon.zen.net.uk (51.148.73.153) 17.089 ms 16.520 ms 16.485 ms
5 netconnex-gw.zen.net.uk (82.71.254.2) 19.283 ms 16.605 ms 16.349 ms
6 po11-13.bdr-rt3.thdo.ncuk.net (80.249.97.22) 16.608 ms 16.314 ms 16.159 ms
7 po4-31.core-rs4.thdo.ncuk.net (80.249.97.85) 17.726 ms 17.464 ms 16.035 ms
8 pingbox1.thinkbroadband.com (80.249.99.164) 17.144 ms 18.059 ms 16.497 ms

What does that say?