Guide Errors & Troubleshooting

What to do if you see "Account Suspended"

Your files and data are still there — a suspension is a switch, not a deletion. Here is what causes it and how to get it lifted.

Updated 6 min read Beginner

Instead of your site, visitors see a plain page saying Account Suspended, or something close to it. This is not a crash and it is not data loss. A suspension is a deliberate switch a hosting provider flips to take an account offline temporarily, and everything behind it — files, databases, email — stays exactly where it was. The page comes down the moment the reason for the suspension is resolved.

The usual reasons, and they are usually one of a short list

An overdue or failed payment

By far the most common reason. If a renewal payment failed — an expired card, a bank declining the charge — the account is typically suspended after a grace period rather than being cancelled outright. Check your billing area or the email address on the account for a payment failure notice; it usually arrived before the suspension did and explains it in one line.

Resource usage well beyond the plan

Shared hosting works because usage stays within reasonable, shared limits. An account that is consuming a disproportionate share of CPU, memory or bandwidth — sometimes because of a genuine traffic surge, sometimes because of a runaway script or a compromised plugin quietly running something it shouldn't — can be suspended to protect the other accounts on the same server while the cause is identified.

A terms of service issue

Content or activity that breaches the hosting terms — this covers things like sending unsolicited bulk email, hosting content that infringes someone else's rights, or running services the plan isn't intended for. This category usually comes with a specific explanation from the provider rather than a generic page, since it needs to name what was found.

A compromised account sending spam or hosting malicious content

If the account has been compromised — through a stolen password, an outdated plugin with a known vulnerability, or a weak FTP credential — it can start sending spam or serving malicious files without the account holder doing anything at all. Providers often suspend an account proactively in this situation, both to stop the activity and to protect the account holder, before the account holder has even noticed anything wrong.

An abuse complaint from a third party

Sometimes the trigger is an external report — a spam complaint, a copyright notice, a blocklisting by a security service — rather than anything detected internally. These are usually resolved quickly once the specific content or activity named in the complaint is addressed.

What to check first

  1. Read any notification you were sent

    Suspensions are very rarely silent. Check the email address on file — including spam and junk folders — for a message explaining the reason before assuming you have to ask.

  2. Check your billing status

    Log in to your billing area and confirm whether an invoice is overdue or a card on file has expired. This resolves the largest single category of suspensions without needing to contact anyone.

  3. Think about what changed recently

    A new plugin, a public form that started attracting spam submissions, a sudden spike in traffic, a password you haven't changed in a long time. Any of these narrows down which category above is the likely one.

What to preserve, in case it matters

If the cause isn't immediately obvious from a billing check, it's worth keeping a short record before things change further:

  • A screenshot of the suspended page itself, including its exact wording if it names a reason.
  • Any suspension email in full, rather than deleted or summarised from memory.
  • The approximate time the site was last known to be working normally.

None of this is difficult to gather, and having it ready means a support conversation starts from facts rather than from "I don't know why this happened".

Change your password as a precaution

If there's any possibility the suspension is related to unauthorised activity — spam you didn't send, files you don't recognise, a suspicious login you can't account for — change your hosting account password and your site's admin passwords before doing anything else. This is worth doing even if you aren't yet certain that's the cause, because it costs nothing and closes off the most common route back in while the rest is being investigated. Our guide on choosing a strong password covers what makes one hard to guess or reuse against.

Getting it lifted

Contact support with your account details and, if you have them, the specifics gathered above. If the cause is billing, settling the outstanding amount typically restores access very quickly. If the cause is resource usage or a terms of service issue, support can tell you exactly what needs to change before the account is reinstated — and in the case of a compromised account, will usually want to confirm the specific issue has been cleaned up first, which our guide on fixing a site redirecting to spam can help with if that turns out to be the underlying cause.

Whatever the reason, the pattern is the same: identify what triggered it, address that specific thing, and access is restored. Nothing about a suspension is a one-way door.

Frequently asked questions

Will I lose my files while the account is suspended?

No. Suspension disables public access to the account; it does not delete anything. Files, databases and email are kept in place while the account is suspended, so restoring access restores the site exactly as it was.

Why would I need to change my password if this wasn't a hack?

Most suspensions are billing or resource related and have nothing to do with a compromise. But if the cause turns out to be malicious activity you didn't authorise — spam being sent from your account, for example — a password change is the first thing worth doing while the rest is investigated, since it closes off the most common way that happens.

Related reading