18-01-2025 01:17 PM - edited 18-01-2025 01:55 PM
I've been with EE since it has existed. What's never changed is the shocking amount of errors its web pages throw up when navigating its website. Just out of curiosity, wanted to check current full fibre packages. You click on "see broadband deals" you get "Sorry, looks like a technical error", a message I see regularly. NO, I'm not going to call you! Navigating your package setting throws up these errors all the time and has done for years. Just when are EE going to get on top of things? Another I get most years are reminder emails that my package is coming to an end, not the current one, one from the past. What do you do? Trust its just a mistake and nothing will happen or chase it up as I've done in the past. For gods sake, get it sorted EE. You must be losing potential customers that will just go elsewhere. My once faithful patience is running out to the point I might just leave EE.
18-01-2025 09:15 PM
@chrisd0407 That’s because you can not yet upgrade from legacy EE broadband to New EE broadband and that’s all that shows within your account at present. So if you do what to upgrade you will have to call customer support as you’ll have to continue on legacy broadband.
25-01-2025 09:19 AM
I couldn't even log into my account this morning without getting the same error.
25-01-2025 09:31 AM - edited 25-01-2025 09:31 AM
Log in problems are historic on the EE website, I've had problems for years. Simple log on to look at my account this morning & I get the predictable error: "Sorry, looks like a technical error". Even though it appears to show me as logged in, click on your bills, I get "Sorry, something's gone wrong.
Worst website I have ever visited for errors and "sorry messages". If it wasn't for BT is to become EE (god help them) I would move to them.
25-01-2025 11:35 AM
Hi there @chrisd0407
Thanks for coming back to the community.
Do you get the same error message if you log into the EE app?
Have you tried clearing all cookies/cache for the browser to see if you get the same error?
Leanne 🙂