Here's the currently active BQM box in the subnet:

80.249.99.164

Here's my latest snapshot: https://imgur.com/a/c2hVH6U

Looks a lot better. It seems that latency is specific to TBB's box, as I get 4ms to Google.

Definitely need better routing.

On the old HeyBB ASN there was only one peer, Since the move to the F&W ASN, just 2 peers. A lot of room for improvement.

Can confirm I'm seeing the same.

The small bit of packet loss showing on the TBB BQM seems limited purely to them. The tracking on my OPNSense box shows a very minimal amount of packet loss <1% since the announcement that it was fixed.

Since yesterday afternoon, my automation shows consistent downstream and upstream throughput at all times now. The 2am / 2pm disruption is gone and the evening peak time has no slowdown at all. Latency is 3-5ms to 1.1.1.1 and 8.8.8.8. The service is very stable. Packet loss is <1%

As far as I'm concerned, the problem is resolved.

Edited by nofappingway (Thu 11-May-23 10:54:02)

No doubt it has improved materially.

I am still seeing packet loss (outside of BQM) to a few locations and that isnt as it was before the maintenance that broke it. Neither is it as it should be.

Is anyone monitoring packet loss (aside from via BQM)?

I'm not seeing much packet loss at all in SL9. What are you testing against and how are you measuring it?

I had some Teams video call break-up and the poor network quality message popped up.

I then started a recursive ping to bbc.co.uk and 8.8.8.8, let it run for maybe 5 hours, stopped it, and saw ~2% loss.

Of course very aware that the destination matters...

Was wondering if anyone had any more scientific and repeatable / sustainable method....

This is my OPNSense monitoring to 8.8.8.8 for the past 60 hours:
https://i.imgur.com/7xtsxDg.png

There's still <1% occasional packet loss (and I agree, there should be zero), but it's a lot better than it was.

Edited by NeoLojik (Thu 11-May-23 12:40:08)

Check your BQMs guys - last 15min - better latency and zero loss!!!

Fingers crossed....

AND... Also, no Teams issues for me just now

Edited by Henry8 (Thu 11-May-23 13:41:30)

The routing has changed:

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

1 <1 ms <1 ms <1 ms xxxx.xxxxxxxx.co.uk [192.168.1.1]
2 3 ms 3 ms 3 ms 31.214.156.3
3 3 ms 3 ms 3 ms 172.16.245.2
4 3 ms 3 ms 3 ms 194.35.42.12
5 4 ms 4 ms 4 ms lonap-gw1.thdo.ncuk.net [5.57.80.142]
6 4 ms 3 ms 4 ms ae11-11.edge-rt5.thdo.ncuk.net [80.249.97.21]
7 5 ms 5 ms 4 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]
8 6 ms 4 ms 4 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90]
9 4 ms 4 ms 4 ms pingbox1.thinkbroadband.com [80.249.99.164]