- Order by phone: 0800 033 8006
- Blog
- Coverage checker
- Store locator
on 22-10-2023 03:21 PM
Is anyone else occasionally getting a 'connection down' error from Chrome (or 'Secure Connection Failed' from Firefox) when changing page - if I hit refresh it works fine. At first I wondered if it was the site I was using but have noticed it on multiple different major websites over the past couple of months and not noticed it from other locations where I don't use Three Broadband so does seem to be related to the router/connection (this is via wired Ethernet too, so not a WiFi problem). I've tried changing DNS server in case that helps but no difference.
It mainly seems to happen when trying to first load a site or (annoyingly) at checkout when a different site is being loaded as part of the checkout process. It certainly doesn't happen everytime but does happen with reasonable frequency. I've also noticed I often get it when trying to pull/push from/to Github too and have to do so a number of times for it to work (browsing the Github website works fine).
on 18-06-2025 09:51 AM
I imagine it'll be #3 in areas where other providers currently have offer no 5G service, yet Three do.. Where I am, there's only Three as a 5G option (the only reason I'm still here!), but I can't imagine that during whatever due diligence that Vodaphone must carried out, that engineers failed to notice that the Three 5G service is fundamentally broken.. So I can only hope there's a fix, otherwise it'll be Starlink or something..
Anyway, nothing changed here, still as broken as ever..
on 13-06-2025 12:52 PM
That's actually an interesting take, I had not thought about roaming to the Vodaphone network, which according to their tool is quite strong in my area,
on 13-06-2025 02:59 AM
Maybe using the Vodafone equipment and/or signals will bypass this issue entirely?
I doubt that we can all switch without some form of hassle...
on 12-06-2025 02:00 PM
The merger with Vodaphone is now complete, do we think that this issue will now get resolved? Honestly, I'm doubtful.
on 27-05-2025 05:09 PM
Guess what? This issue still exists! Hello? Anyone still here?
I cannot say how frustrating, and unnecessary, it is to have to install a VPN onto all the household computers just to use the internet service I paid for.
In better news, it looks like fibre has *finally* rolled out in my area. It'll cost me more, but I'd rather pay more for a service which does work than less for a service that doesn't work and apparently will never be fixed.
on 30-05-2025 09:22 AM
Perhaps looping in @PeteG will add some fresh eyes to the issue, probably not.
on 30-05-2025 11:15 AM
Hello.
I don't have much in the way of new information to share on this issue, sadly. I can confirm it is still being looked into though. When there's an update, I'll be sure to pass it along.
Pete.
Mod tip! The author of a post can hit 'Accept as Solution', to highlight a reply that helped solved their query.
30-05-2025 04:44 PM - edited 30-05-2025 04:49 PM
"I can confirm it is still being looked into though". I have to be honest, I find that pretty hard to believe, beyond a cursory "yeah, that's still an issue. Oh well". 18 months to be no closer to any kind of resolution is, frankly, ridiculous... when you consider what *can* be achieved in 18 months.
"When there's an update, I'll be sure to pass it along". There hasn't been an update in 1.5 years. I'm not quite sure why we should expect there to be one in the next 1.5 years.
You are aware that your service is effectively broken for all of the users in this thread (and most likely, countless more), yes?
on 30-05-2025 02:01 PM
Has the issue been experienced by an engineer? Using the copious data supplied by members of this thread, I would have expected someone with a device and access to logging data to have been able to replicate the issue and use that to work backwards towards the root cause.
on 11-06-2025 12:17 AM
Esp as I found GitHub was one of the main sites where I would experience it! (updating Home Assistant running on my Raspberry Pi was always a bit of a heartsink time!)