Emergency Rescue Plan active — senior engineer replies within 12 hours See the plan →
Infrastructure · people search: “My host suspended my website for 'abuse' or resource use.”

My host suspended my website for 'abuse' or resource use.

A suspension notice is your host protecting the shared server. Whether it's malware, a traffic flood, or an honest spike, the recovery order is the same.

Plain English · no jargon · 4-minute read

Part of Servers & Infrastructure — read first, then fix it in 48h.

One morning the site is gone and the host's email says 'suspended for abuse', 'excessive resource usage', or 'malicious content'. A suspension isn't the same as a hack or an outage: the host has deliberately cut the account, usually because something on it threatened the server or its neighbours. The notice is your map — read exactly which reason was given, because it decides the fix.

Check these first, yourself

  1. Read the exact reason in the suspension email and the host's control panel — 'abuse', 'resources', and 'malicious content' each mean a different problem.

  2. If it's resource usage, check traffic and logs for a spike: a bot flood or a viral moment can look identical from the server's side.

  3. Don't reinstall or wipe anything before you know whether the trigger was an infection — you'll destroy the evidence the host is asking about.

  4. Reply to the host factually and ask exactly what they need to lift the suspension; most have a documented process and speed it up when you engage properly.

Should you fix it yourself or call a rescue?

Have you tried the free fixes (images, caching, plugins)?If yes and it's still slow → the problem is deeper.
Is your hosting or server the bottleneck?Shared hosting, old PHP, no object cache → server-level problem.

Still have questions?

Can I switch hosts to escape the suspension?

Moving hosts before understanding the cause usually carries the trigger with you — a hacked file or a resource-hungry script travels with the data. Diagnose first, then migrate if the host relationship is beyond repair.

What if the spike was legitimate traffic I want?

Then the fix is capacity and caching, not apologising. A shared plan has hard limits; the rescue can tell you whether you need a bigger plan, better caching, or a small server of your own.

Don't want to become an expert in this?

Send the symptom — get a flat-rate ticket and a plain-English plan within 12 hours.

Start the Rescue