Connecting Home Broadband to My EE Account is Bugged

[Sebastian_J]

Hey all, I have just got my first EE product after always being a Vodafone loyalist...I bought the EE super fast home broadband but when I try to link it to the My EE account, either online or on the app it always gives me the same error. It gives me 4 lines of actual code that looks exactly like this:

{
"code": "500",
"message": "QuotaViolation"
}

When I called them on their support, they were nice but they had no idea how to fix it and said it could be 10+ days before they email me with a solution...I am also up for contract renewal for my phone and don't really have time to wait for 10 days, does anyone know anything of this/has seen this issue before?
Thanks

Seb

[nuttyxander]

I also have this issue, it's ridiculous that the only options to report this are this forum, a phone call or a letter.

This is precisely the kind of issue best reported by email or a form.

[nuttyxander]

Adding insult to injury, your complaint form is also broken.

[nuttyxander]

As in screenshot, the counter stays well under 500 words, but it insists it's more - presumably you have a poorly coded regex?

[jksejkse]

I'm also getting this 'quotaviolation' json error when trying to register my broadband.
Any updates, please, EE, on the nature of the problem and how to work around it?

[Sebastian_J]

Hey All, Just for another update. After all this time there is still no solution to the problem, I have been on calls with the Broadband care team, the billing team, the IT team, the App solutions team to no avail. I was told by Phil in the "IT" team that there was "no end in sight" for the issue even after all this time. I suggest that all who have this issue instead raise the issues with EE to Ofcom as ringing numbers or contacting support helplines for EE is getting me/us nowhere. If everyone who reads this raises the issue to Ofcom we have the highest chance of getting a solution. I will be ending all contracts with EE and I suggest you all do the same. Can't say I didn't try.

[joeapplleby]

I had the same issue I tried it again on a different network (not EE) and it worked fine.

[Sarahmcccracken]