In reply to a post by Dreovid:

How is everyone's experience with upload speed and Hey! Broadbands peering?

As far as I can tell, F&W, who provides the infrastructure for Hey! broadband only peer with a couple of other networks.

I'm on the 1gbps package, and for me, the upload rate to everything except the ookla speedtest servers is fairly abysmal. I've hosted an openspeedtest server on my network, and generally, people who I've asked to use it see their download (my upload) capped around 50mbps.
I've also routed it through a Cloudflare tunnel, and that's improved it to around 70mbps.

If anyone wants to give it a go here are the links (report back because I don't log the results).
This test is directly through HB.

and this test is through cloudflare

Here is some feedback for you, 40 down 17 up. From Virgin Media in a good VM area where I typically get max speed to anything reputable.

Also traceroute. This is to the first link.

Tracing route to 185.86.10.16 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms PFSENSE.home [192.168.1.252]
2 * * * Request timed out.
3 9 ms 7 ms 8 ms leic-core-2a-ae58-650.network.virginmedia.net [82.3.34.5]
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 29 ms 19 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
7 * * * Request timed out.
8 * * * Request timed out.
9 23 ms 20 ms 24 ms nl-ams04a-ri3-ae-9-0.aorta.net [84.116.130.242]
10 22 ms 20 ms 20 ms b901f059.ptr.era-ix.net [185.1.240.89]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 28 ms 30 ms 33 ms 194.35.42.13
16 * * * Request timed out.
17 37 ms 36 ms 33 ms 185.86.10.16

Found another unusual problem with my HeyBroadband connection this evening... The cloud services used by Bambu Labs 3D printers sometimes don't work over the HB connection.

I was trying to get something downloaded to my printer for over 2 hours today, then it dawned on me that perhaps it was another HB routing problem. I forced my printer to use my TalkTalk connection & it worked immediately.

It's a bit of a niche problem, but just thought I'd leave this here in case anyone else has a similar issue & can't find a solution.

Yes, upload is awful, but I do not think they really care about it. But I will when my contract is up for change….

But they could not care, because support from South Africa is totally meaningless

At least routing works fine on static (payable) IP 31.214.156.xx
and can access almost all (same random domains had either that subnet or exact IP banned but somehow managed to get the other side companies to whitelist it)

Edited by sebus (Fri 15-Nov-24 16:34:18)