508 Resource Limit Reached

A 508 error means your account briefly used more server resources than your plan allows. Every account on our shared servers runs inside its own CloudLinux LVE container, which guarantees your neighbours cannot slow you down — and keeps your usage from affecting theirs. When you hit a ceiling, the server pauses new requests and shows a 508 until usage drops.

What the Limits Are

CloudLinux LVE caps a handful of resources per account. In plain terms:

CPU — how much processor time your scripts can use. Heavy pages that run too long hit this first.
Entry Processes (EP) — how many requests can be actively running PHP at the same moment. A traffic spike or a slow page can fill these up.
Physical Memory (PMEM) — the RAM your processes may use at once.
I/O and IOPS — how fast and how often your account can read from and write to disk.

For the exact figures on your plan and a fuller explanation, see LVE Limits and Resource Limits.

Why It Happens

A 508 is a symptom of demand outrunning your allowance. The usual triggers are:

Traffic spikes — a post goes viral or you launch a campaign and many visitors arrive at once.
Heavy plugins — page builders, related-post widgets, or poorly written plugins that run expensive queries on every page load.
Bad bots — aggressive crawlers and scrapers hammering your site with rapid requests.
No caching — every visit rebuilds the page from scratch instead of serving a saved copy.

Diagnose It in cPanel

Log into cPanel.
Open Metrics > Resource Usage.
Review the graphs for CPU, Entry Processes, Physical Memory, and I/O over the last few days.
Note which limit is being hit and at what times — a daily spike points to a cron job or scheduled task; a constant ceiling points to a heavy plugin or crawler traffic.

Note The Resource Usage page tells you which limit you are hitting. That is the single most useful clue for fixing a 508 — a memory problem and a CPU problem have very different solutions.

Fix It: Reduce Your Usage

Enable Caching

Caching is the highest-impact change for most sites. It serves saved copies of your pages instead of rebuilding them per request, which slashes CPU and memory use. Ultra accounts include AccelerateWP for this.

See AccelerateWP to turn on page caching, object caching, and asset optimization.
For WordPress, enable full-page caching first — it usually gives the biggest drop in resource use.

Block Abusive Bots

If your Resource Usage spikes line up with crawler traffic, block or slow the offenders. Review your access logs, then deny the worst user agents or IP ranges in .htaccess or via a security plugin.

Optimize the Database and Queries

Bloated tables and slow queries burn CPU and I/O. Remove unused plugins, clean out post revisions and spam comments, and repair or optimize your database tables from phpMyAdmin in cPanel.

Upgrade the Plan

If your site has legitimately grown beyond its current allowance, a larger plan gives you higher LVE limits. This is the right answer when your traffic and usage are genuinely high and already optimized.

Can Support Just Raise My Limits?

No. Plan limits are enforced and are not adjusted on request. A 508 is resolved by reducing your usage (caching, blocking bots, optimizing your site) or by upgrading to a plan with higher limits. Support cannot simply lift the ceiling on your existing plan, because those limits are what keep every account on the server fast and fair.

Tip Start with caching before anything else. On a typical WordPress site, enabling full-page caching often removes 508 errors entirely without any other change.

Need Help Interpreting the Graphs?

If you are not sure which limit you are hitting or what is driving it, open a support ticket. Include your domain and a note of when the 508 errors appear, and we will help you read the Resource Usage data and point you at the biggest wins.