I've just been told the upstream issues I was experiencing should now be resolved. I will monitor and report back

Edited by nofappingway (Wed 10-May-23 17:28:34)

In reply to a post by NeoLojik:

so I wonder if it's specific to the route between Hey/F&W and the TBB BQM server.

Exactly my thinking...
Routes from Hey to 8.8.8.8 and bbc.co.uk are 'normal'.
Im wondering whether it's only the route to TBB BQM that's bad or whether there are others. I suspect there will be others....

Had exactly the same email. I highly doubt anything has changed as I'm still seeing low levels of packet loss, but the next few hours should tell for sure.

In reply to a post by NeoLojik:

Oddly, my ping to bbc.co.uk is just fine, as low as it always has been, so I wonder if it's specific to the route between Hey/F&W and the TBB BQM server

I think the same. My ingame pings after the BQM jump are the same as they always have been.

I got this email from them an hour ago, will see how the connection fares this evening...

The connectivity issue you have been experiencing should now be sorted.

It goes without saying, making sure you always have full-fibre connectivity is our top priority and we’re doing everything we can to improve this ongoing.

If you’re still experiencing connectivity issues, please email our Technical Customer Service Team at [email protected].

If we don’t hear from you within the next 24 hours, we’ll assume your connection is fine and close your ticket. Once again, we apologise for the inconvenience this has caused you.

The Hey!Broadband Team

I also got the Great news - The problem's been fixed! email, hopefully that's done the trick now

Fingers crossed eh

Still seeing some packet loss on BQM but it's in a slightly more acceptable range of 1-5% (I can barely notice it gaming/doing other things) as apposed to the 15-20% we were all seeing in the last 2 weeks.

Edited by smithy93 (Wed 10-May-23 18:43:20)

I haven't had the message, but it certainly looks like it may be significantly better:

https://www.thinkbroadband.com/broadband/monitoring/...

TC

For a FTTP provider I’m seeing alot of red. My FTTC connection with talk talk never shows any red. I’m waiting for it to roll out here but these monitors are not too good. I’m also getting 8ms ping where I’m seeing double that ping with hey.

https://www.thinkbroadband.com/broadband/monitoring/...

Edited by Magicuk27 (Wed 10-May-23 20:04:55)

It's certainly better, but there really shouldn't be any packet loss.

Does anyone know the IP of the box which performs the BQM graphs? I'd love to traceroute to it and see why the minimum latency is so high.

100% agree - there shouldnt be any loss at all. I have none on my FTTC line (and the latency is much much lower too).

BQM is @ 80.249.99.160/28


PS: And to add, i have been doing a recursive ping to 8.8.8.8 and bbc.co.uk over the last 2hrs and zero losses, unlike the BQM... I suspect there is an issue on the route from Hey to BQM - impacting latency and loss. Of course, as above, we dont know which other routes are also 'bad'.

Edited by Henry8 (Wed 10-May-23 20:20:32)

Thanks!

Here's a traceroute over both my Hey connection, as well as AAISP:

HeyB:

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 * * * Request timed out.
5 5 ms 5 ms 5 ms be3487.ccr41.lon13.atlas.cogentco.com [154.54.60.5]
6 5 ms 5 ms 5 ms be2348.rcr21.b023101-0.lon13.atlas.cogentco.com [130.117.51.74]
7 16 ms 18 ms 27 ms telecomitaliasparkle.lon13.atlas.cogentco.com [130.117.14.86]
8 6 ms 5 ms 4 ms ae30.londra32.lon.seabone.net [195.22.209.220]
9 5 ms 5 ms 5 ms 149.3.183.85
10 18 ms 17 ms 17 ms ae11-11.edge-rt5.thdo.ncuk.net [80.249.97.21]
11 17 ms 17 ms 17 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]
12 18 ms 18 ms 18 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90]
13 17 ms 16 ms 17 ms pingbox1.thinkbroadband.com [80.249.99.164]

AAISP:

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 7 ms 7 ms 7 ms u.gormless.thn.aa.net.uk [90.155.53.129]
3 7 ms 7 ms 7 ms q-aimless.tch.aa.net.uk [90.155.53.109]
4 8 ms 8 ms 8 ms lonap-gw1.thdo.ncuk.net [5.57.80.142]
5 8 ms 8 ms 9 ms ae11-11.edge-rt5.thdo.ncuk.net [80.249.97.21]
6 8 ms 8 ms 8 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]
7 8 ms 8 ms 8 ms pingbox1.thinkbroadband.com [80.249.99.164]

Quite the difference in routes, though AAISP does have excellent peering.

Edit: Re-ran with the correct IP

Edited by NeoLojik (Wed 10-May-23 22:01:45)