508 Resource Limit Is Reached

What’s actually happening

The entire site returns 508 instead of loading, sometimes for a few seconds, sometimes for minutes, then recovers on its own. It tends to hit during traffic spikes, when a backup or cron runs, or when bots crawl hard. This is a CloudLinux/cPanel signal, not a standard HTTP code: the LVE (Lightweight Virtual Environment) wrapping your account ran out of its allotted CPU, physical memory, I/O, or entry processes (concurrent PHP requests), and the kernel queues or rejects new requests until usage drops.

Common causes

• Entry-process or PHP-worker limit (often just 20-30 on shared plans) saturated by concurrent visitors or a slow page holding workers open.
• A heavy plugin or unindexed query burning CPU on every request (WooCommerce, sliders, related-posts, stats plugins are common).
• A runaway or overlapping cron job, or WP-Cron firing on every pageview under load.
• Bot traffic, aggressive crawlers, or a small DDoS/brute-force run on wp-login.php multiplying request volume.
• A plan whose limits are simply too small for the site's real traffic and resource use.

How to fix it

1. Look at the actual usage graphsIn cPanel open 'Resource Usage' (or 'CPU and Concurrent Connection Usage') to see which limit you're hitting: CPU, Physical Memory, Entry Processes, or I/O, and when. On a VPS with root, lveinfo --period=1d and lvechart show LVE faults per user. You can't fix this blind.
2. Add caching to cut CPU and worker timeInstall a page cache (LiteSpeed Cache, WP Super Cache, W3 Total Cache) so most requests serve static HTML and never start PHP. This is usually the single biggest drop in resource use and frees up entry processes immediately.
3. Kill the specific resource hogUse Query Monitor or the host's process list to find the offending plugin or query, then optimize or replace it. Disable WP-Cron via define('DISABLE_WP_CRON', true); in wp-config.php and run it from a real system cron every 5-15 minutes instead of on pageviews.
4. Block the bots eating your processesIf logs show crawler or login-attempt floods, rate-limit or block them at Cloudflare or in .htaccess, and protect wp-login.php. Cutting junk traffic often pulls you back under the entry-process cap on its own.
5. Raise the limits or move up a planIf usage is legitimate, ask the host to raise your LVE caps (entry processes, CPU%, memory) or move to a plan or VPS with real headroom. On shared hosting you can't override LVE limits yourself, only the provider can.