"508 Resource Limit Is Reached": What It Means on Shared Hosting
The 508 page means your shared hosting account hit one of its CPU, memory or process limits. Here is how to tell which one, how to bring usage down, and when to move.
Short answer: shared hosts give each account fixed limits on CPU, memory, simultaneous processes and disk activity, usually with CloudLinux. When your site goes over one, visitors see "508 Resource Limit Is Reached" until usage drops. The cPanel Resource Usage page shows which limit you hit. Caching and blocking bad bots usually fix it; if real traffic keeps hitting the limits, the site has outgrown the plan.
The limits behind the 508
| Limit | What it counts | Typically hit by |
|---|---|---|
| Entry processes (EP) | Requests being handled at the same moment | Traffic spikes, bots, slow pages |
| CPU | Share of a processor core | Heavy plugins, uncached pages, search |
| Physical memory (PMEM) | RAM used by your processes | Page builders, large imports |
| Processes (NPROC) | Total processes, including cron and SSH | Overlapping cron jobs |
| IO / IOPS | Disk read/write speed and operations | Backups, big database queries |
Bring usage down
- 1Turn on page caching so most visits never run PHP.
- 2Check the access log for one IP or bot making thousands of requests, and block it.
- 3Replace WordPress's visit-triggered cron with a real cron job every 5–15 minutes.
- 4Slow down the Heartbeat API on admin pages if several people edit at once.
- 5Disable plugins you no longer use, especially related-posts, statistics and broken-link checkers that run on every page.
- 6Move backups to run at night, outside your busiest hours.
When to move instead
If the 508 comes from real customers at your busiest hours, optimising only buys time. The next step is a server where the site's limits are set for its needs rather than for a share of a crowded box.
On GHP Cloud
Sites still have limits, but they are yours: each site gets its own Linux user, PHP pool and CPU, memory and disk-I/O ceilings on a server that only runs your sites. A busy site slows itself, not your other sites, and you can see and change its limits in the panel. Servers are in India, principally Mumbai.
Frequently asked questions
How long does a 508 error last?
Until usage drops back under the limit, usually seconds to minutes. Repeated 508s mean the cause is still there.
Does a 508 error hurt SEO?
Occasional ones do not. If Googlebot keeps meeting them, it crawls less and pages can drop until the errors stop.
Will upgrading my shared plan fix it?
It raises the limits, so it can. Check which limit you hit first; more CPU does not help a site that runs out of entry processes because of a bot.
GHP Team
GHP Cloud
Manage WordPress sites the smart way
GHP Cloud gives you a managed server in India with a firewall, malware scanning and daily backups, billed in INR with a GST invoice — from ₹1,450/month.