What Actually Gets a Shared Hosting Account Suspended
Shared hosting accounts are almost never suspended for using too much bandwidth. They are suspended for three things the plan page does not advertise: exceeding the inode limit, exceeding the concurrent entry-process or CPU limit, and hosting content that violates the acceptable use policy. The first two are hard caps written into the terms of service, and a site can hit them while using a fraction of the "unlimited" storage and transfer the plan is sold on.
The practical consequence is that the number people shop on -- bandwidth -- is the least likely limit to end an account, while the limits that actually bind are usually one click deeper in the terms.
The Three Limits That Actually Bind
Inodes. An inode is one file or directory. A shared plan advertising unlimited storage commonly caps inodes somewhere in the hundreds of thousands, and a WordPress install with a few plugins, a cache directory, and an email account holding years of messages reaches six figures without anyone noticing. Hitting the cap typically stops backups and new file writes first; sustained overage is what triggers the suspension. Email is the usual culprit, because messages are individual files and IMAP accounts are rarely pruned.
Entry processes and CPU. Entry processes are the number of simultaneous PHP executions the account may run. On shared plans this is a small number, often in the range of 10-40 depending on host and tier. When the limit is reached, additional visitors receive a 508 error rather than a slow page. This is why a site can be "down" for real users while an uptime monitor requesting a single cached page reports 100 percent availability.
Acceptable use. The AUP covers what the account is used for rather than how much it consumes: bulk email sending, storing files not served by the website, running long background jobs, resource-heavy scripts, and content categories the host declines to carry. Violations here can produce immediate suspension without the warning that resource overages usually get.
Comparing shared plans on storage and bandwidth compares the two numbers least likely to end the account. Compare inode caps and entry-process limits instead, and expect to find them in the terms of service rather than the plan table.
How the Limits Compare to What Is Advertised
| Limit | Where it is published | What happens at the cap | Who hits it first |
|---|---|---|---|
| Bandwidth | Plan page, prominently | Usually throttling or an upgrade prompt | Media-heavy sites, rarely |
| Storage | Plan page, prominently | New uploads fail | Video and backup storage |
| Inodes (file count) | Terms of service or knowledge base | Backups stop, then writes fail, then suspension | Old email accounts, cache directories |
| Entry processes / CPU | Terms of service or knowledge base | 508 errors for real visitors | Uncached WooCommerce and membership sites |
| Acceptable use policy | Separate AUP document | Suspension, sometimes immediate | Bulk mailers, file storage use |
What Changes by Site Type
Brochure and small business sites rarely approach either cap. For these, shared hosting behaves as advertised, and the sizing question is covered in the small business sizing guide.
WooCommerce and membership sites hit entry-process limits first, because cart, checkout, and account pages cannot be served from cache. Every logged-in visitor consumes a PHP process for the duration of the request. This is the most common reason a store outgrows shared hosting while its traffic numbers still look modest.
Sites with long-running email accounts hit inodes first. Ten years of IMAP mail across several mailboxes can account for the majority of an inode count on its own, which is one reason separating mail from web hosting is worth considering.
Sites with aggressive backup plugins generate inodes continuously. A plugin keeping thirty full backups inside the account directory duplicates the entire file count thirty times over, and it counts against the same cap the live site uses.
How to Check Before It Becomes a Problem
- Find the inode count in cPanel: the statistics sidebar reports it, often labelled File Usage. Compare it against the cap in the host's terms, not against the storage figure on the plan page.
- Find the entry-process limit and current usage: most cPanel hosts expose a resource usage page showing how often the account has hit the entry-process or CPU ceiling. Repeated "faults" there are the early warning that precedes 508 errors.
- Audit mailboxes separately: check message counts per mailbox and archive or delete anything older than a retention period you actually need.
- Cap backup retention inside the account: keep two or three local copies at most and send the rest offsite. Backup storage is also where restore charges tend to surprise people, so confirm what a restore costs before you need one.
- Read the AUP for the specific words that matter: bulk email, file storage, background processes, and cryptocurrency-related workloads are the four categories most often prohibited outright.
What Suspension Actually Looks Like
Resource overages typically escalate: an automated warning email, then throttling, then suspension if usage continues. AUP violations skip the ladder and can suspend immediately, which is why the AUP is the document worth reading before signing up rather than after.
Reinstatement usually requires reducing usage below the cap or removing the offending content, and hosts commonly ask for a written explanation of what changed. Data is generally retained during a suspension, but that is a policy question rather than a guarantee -- the retention window during suspension is stated in the terms and is worth checking, because it differs substantially between hosts.
If a suspension does land, the sequence that resolves it fastest is the same regardless of cause. Get the specific reason in writing from support rather than accepting the generic notice, because "resource abuse" can mean either of two completely different limits and the remedies do not overlap. Ask which metric was exceeded, over what window, and what threshold has to be reached for reinstatement. Then fix that metric before replying, since a reinstatement request that arrives with the numbers already reduced is resolved considerably faster than one promising to reduce them. Keep the ticket, because a second suspension on the same account is treated differently from a first.
The upgrade path is the other outcome. A suspension notice is frequently the first time an owner learns the account was on a plan that no longer fits, and the move is usually to VPS or managed hosting rather than to a larger shared plan, since the binding limits are structural to shared environments. That transition is covered in the shared to VPS migration guide.
Which Limits Should You Actually Compare?
Compare inode caps and entry-process limits, in that order, and treat storage and bandwidth as tiebreakers rather than as the decision. Before buying, find both numbers in the terms of service -- if a host does not publish them, that absence is itself a data point, because the hosts that compete on these limits tend to state them. Then check the current numbers in cPanel quarterly rather than waiting for the warning email. A store or membership site running uncached logged-in traffic should plan the move off shared hosting on its own schedule instead of discovering the ceiling during a sale.
Read the full hosting comparisons on HostingDive -- or compare shared and VPS options with current intro and renewal pricing.
Frequently Asked Questions
- What is an inode in web hosting?
- One inode is one file or directory on the account. Because every email message, cached file, plugin asset, and backup file counts as one, the total climbs far faster than disk usage suggests -- which is how an account can hit an inode cap while using a small fraction of its advertised storage.
- Why does the site show a 508 error when the host reports full uptime?
- A 508 means the account hit its concurrent entry-process limit, so new requests were refused. Uptime monitors usually request a single cached page, which can be served without a PHP process, so the monitor sees a healthy site while real visitors hitting dynamic pages are refused. The distinction between this and an actual outage is covered in what an uptime guarantee actually measures.
- Can a host suspend an account without warning?
- For acceptable use violations, generally yes -- those can be immediate. Resource overages more commonly follow an escalation path of warning, throttling, then suspension, though the specific sequence is set by each host's terms rather than by any standard.
- Does deleting email free up inodes?
- Yes, and it is usually the fastest reduction available, since each message is a separate file. Emptying trash and spam folders and archiving old mail offline often reclaims a large share of the count without touching the website at all.
- Is upgrading to a bigger shared plan the fix?
- Sometimes for inodes, rarely for entry processes. Entry-process ceilings are structural to shared environments and do not scale much between shared tiers, so a site refusing visitors at peak usually needs VPS or managed hosting rather than the next shared plan up.