- Order by phone: 0800 033 8006
- Blog
- Coverage checker
- Store locator
on 10-22-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 02-25-2024 04:02 PM
Added a few to tracker now.
on 02-23-2024 02:45 PM
Definitely happens on Windows & Linux for me.
on 02-20-2024 08:34 PM
At this point I was going to suggest that our best course of action would be to start leaving public reviews on trustpilot with the aim of naming and shaming Three into action... When I checked, it turns out that Three Broadband only has a score of 1.5 and Three UK as a company has just 1.3.
Since it's not possible to rate a company / product 0 on trustpilot, the scores are more like 0.5 and 0.3 out of 4 respectively so I don't think we'll make much of a dent in the shame factor.
on 02-20-2024 08:28 PM
What did you learn from the service desk @JonathanB . It's been 2 weeks since you told us you'd give us an update. Since this appears to be our only route for support, I don't think that's an acceptable time to leave us waiting.
I also note that you've dodged all questions about whether we'll be able to get out of our contracts early. Please let us know our options.
on 02-20-2024 05:00 PM
Also been suffering from this since becoming a 3 customer last month.
The fact that this isn't fixed and is seemingly being swept under the rug is disgraceful.
02-18-2024 10:57 PM - edited 02-18-2024 10:58 PM
I hope this isn't true, that domestic customers are treated as second class. Although the lack of response on this thread does seem to indicate just that approach.
on 02-18-2024 09:52 PM
I do emphasise with the people still affected by this, I was affected by this for many many months and I now consider it to be fixed but I am a business customer. They must have done something and I hope it can be applied to non-business customers too.
on 02-22-2024 11:40 PM
I'm a business customer too. I switched back to the NR503E to test again, but it was worse than ever. Now switched back to the MU5001 and it's working fine again. I guess I'll just have to consider the Zyxel useless for the time being and keep an eye on this thread in the hopes that it gets fixed one day.
on 02-12-2024 10:32 PM
@JonathanB more information courtesy of another poster on the ISPReview forums -
Hi EDIflyer, I signed up just to reply to you. I was running the NR5103Ev2 on Three and ran into the same issues. I am running 100s of API calls a min for work and Three was causing SSL issues with 50% or more of them based on my monitoring logs (even after enabling adult content, limiting the APN to IPV4 and 4G). I was annoyed and bought the Scancom EE long term sim that was on sale at Amazon and popped it into the NR5103Ev2 and changed the APN settings to EEs settings and IPV4. Its been running for 4+ hours now without any issues where before I could see constant issues on Three. The SSL errors are the result of something Three is doing. I would expect whatever DPI they have in place is breaking SSL. I will be dropping Three and keeping EE (I mean I paid for the long term SIM so thats a no brainer at this point for me)
P.S. I tested with my Smarty SIM in my mobile as well and got the same errors which is no surprise since they are essentially Three but figured I would add that so others don't think testing Smarty proves anything.
Example log:
File "XXXXXXXXXXXXXXXl/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='XXXXXXXXXXXXXXX.com', port=443): Max retries exceeded with url:XXXXXXXXXXXXXXX
(Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1106)')))
I note they tried many of the things that lots of us have tried too and the symptoms are also very similar. Have the team properly examined the potential for deep packet inspection to be causing an issue? Activating a VPN seems to resolve the issue which would also seem to be a potential route.
It would be good to know where in the technical team this has reached - given the number of customers involved can you please confirmed this has been highlighted and escalated to the highest levels? I really hope it's not still stuck in a helpdesk somewhere!
02-10-2024 04:27 AM - edited 02-10-2024 04:28 AM
I am currently flying back to the UK on a Singapore Airlines A380 and their WiFi service just gave me the exact same issue when hitting GitHub
what’s the betting that their in-flight service uses Zyxel kit, or it’s related to some form of content filter.
BTW I see this problem with my second router, but that’s also a Zyxel FWA017 so probably has mostly the same firmware code