We are currently investigating an possible issue related to MySQL Overload suspensions. Many more accounts than usual are getting suspended for this reason since the 16th of May.
As soon as we learn more about this issue, I’ll update this topic.
We are aware of the issue and are doing our best to get this resolved as soon as possible.
I completely understand that this may cause confusion and you will have additional questions. I am happy to provide any information I have to help you.
However, to keep the contents of this topic clean, clear and concise, I ask that you carefully read the Outage Communication Rules before posting.
In a nutshell:
Please keep the posts about the outage in this topic, and all posts not about this outage outside of this topic.
Please post relevant questions only that have not been answered yet. It may be compelling to ask obvious questions like “when will this be fixed”, but basic information like that will be put in this message as soon as we know it.
Please carefully check the known symptoms and affected components.
If you are on the affected components, you are almost certainly affected by the outage. If so, please refrain from simply stating you are affected, it does not help get your service back up faster.
If you are not on the affected components but do experience all of the symptoms, please say so below so we can check if our list is incomplete.
If you do not experience all listed issues and are not on the components that are known to be affected, the issue you are experiencing is most likely not related to this outage. If so, please create a new topic in the Hosting Support category and describe the issue there.
If you say you are affected by the outage, please always include your website URL. I can’t check if you are affected by the outage if you don’t say which of your websites is affected.
Posts that do not follow these rules may be deleted without warning. This is to help ensure that all the relevant information is easily available to everyone reading this topic.
Hello to everyone, since May 17, 2022, I’ve been experiencing daily suspensions for MySQL Usage Limit. In fact, I came to this forum today to ask for advice on upgrading to premium because I thought it was a personal issue caused by visitors and because the free account couldn’t support my website! But after reading this message at the top, I decided to leave you a message and consider keeping a free account if possible!
The outage isn’t so much the issue, but I’m also locked out of phpmyadmin (which I suppose makes sense) and I’d really like to get a copy of the DB so I can merge it with a local one
Is there any way to access the database whilst the account is suspended?
On the 24th of May the limits have been tweaked which should result in fewer suspensions. We hope that this has resolved the issue.
I have also flagged and deleted some posts that violate the Outage Communication Rules. Please read and understand them before posting here to prevent unnecessary flags against your profile.
Thanks for the information, My account was suspended too because MySQL Usage Limits. First time on May-22 and second time yesterday May-27. I hope will be fixed. I have a modest WordPress site with light traffic (almost cero traffic)
I just checked how things are going with the MySQL usage suspensions, and it doesn’t appear that the issue has been resolved just yet. We still see many more accounts than usual get suspended by this.
my account got suspended too, i need up and running it is my schools project which i have to present it in less than 24h plase fix it is very important for me
I removed some irrelevant posts. As clearly stated in the outage communication rules: posts in this topic MUST be ONLY about this outage. Posts in violation will be deleted without warning.
If you see posts like that, please do not reply to the posts here, because you’re just be creating more unrelated junk posts. Please flag them so a moderator can delete them instead.
Looking at the current situation, it seems that the last fix has worked! Far fewer MySQL suspensions have occurred since then. So it seems the issue has been resolved now.
