Intermittent connection issues loading/changing site- secure connection failed/site can't be reached

[EDIflyer]

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).

I'm using a NR5103E with Firmware Version V1.00(ACBJ.0)b14 - I tried rebooting it but to no effect.

[torz77]

Lucky you! My internet is still very much broken 😞

[torz77]

Hey Three! Guess what? Your service is still broken!

Maybe you can think about kicking this upstairs to your new corporate overlords to actually do something, **anything** about it.

I won't hold my breath.

[Nameless]

The service is definitely still broken - The error still exists

I will need to test if I can actually use Vodafone's network bands at some point however MVNOs may not be able to do so yet...

[AlSeek]

I'm optimistic about the VodafoneThree merger. The way I see it there are three outcomes that may happen.

1. Best case: Three issue is resolved by Vodafone systems replacing a system currently broken in Three.

2. Middle case: Three issue remains for Three users but Vodafone users do not inherit the issue. With roaming of either SIM possible on the combined network it may become possible to get a Vodafone based SIM and use it on Three masts without experiencing the issue.

3. Worst case: The issue remains for Three and spreads to Vodafone.

I think there is a reasonable chance case #2 may come to pass but I won't get my hopes up. VodafoneThree did announce this week that they intend to allow roaming for customers of each network on the other's "within a few months" so I guess we'll find out fairly soon. Although if case #2 does happen it may be temporary as over time they combine into a single network it could still evolve into case #1 or #3.

[andym00]

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.. 

[bytespider]

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,

[Nameless]

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...

[bytespider]

The merger with Vodaphone is now complete, do we think that this issue will now get resolved? Honestly, I'm doubtful.

[torz77]

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.

[bytespider]

Perhaps looping in @PeteG will add some fresh eyes to the issue, probably not.