The hosting account — not the server — hit its limit. Shared hosts running CloudLinux cap how many requests one account can handle at the same time (entry processes); when more arrive, visitors get this page. Traffic spikes, bots and slow pages that hold connections open are the usual reasons.
Resource Limit Is Reached The website is temporarily unable to service your request as it exceeded resource limit. Please try again later.
How 2 other clients word the same error
Browser tab
508 Resource Limit Is Reached
curl -I
HTTP/1.1 508
| Error | 508 Resource Limit Is Reached |
| Usually fixed by | The site owner or host |
| Status | 508 — the hosting platform’s use, not HTTP’s (RFC 5842 defines 508 as Loop Detected, for WebDAV) |
| Sent by | CloudLinux, on shared hosting |
| Limit | Entry processes: requests the account handles at once |
Check the site from outside
Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.
What it means
CloudLinux gives each hosting account its own limits — CPU, memory, processes, and entry processes, the number of requests being handled at the same moment. When the entry process limit is full, the next request is refused with this page. The server is fine; this one account is at its ceiling.
Why it happens
- A traffic spike, or bots crawling many pages at once.
- Slow pages: each request holds its slot longer, so fewer are needed to fill the limit.
- Background calls stacking up — WordPress admin-ajax and Heartbeat requests, cron jobs started by visits.
- A plan whose limits are too small for the site.
How to fix it
- Open cPanel → Resource Usage: it shows when the limit was hit and which one.
- Cache pages for anonymous visitors, so most requests never reach PHP.
- Block or slow abusive bots, and reduce Heartbeat and admin-ajax traffic.
- Speed up the slowest pages; if real traffic outgrows the plan, ask the host for higher limits.
If you are visiting the site
- Try again in a few minutes; the site is busy, not broken.
Questions
Is 508 a real HTTP status code?
The number is: RFC 5842 defines 508 as “Loop Detected”, for WebDAV. “Resource Limit Is Reached” is CloudLinux reusing it for its own limits — the page you see comes from the hosting platform, not from your site.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Limits — docs.cloudlinux.com
- GitHub — cloudlinux/mod_hostinglimits: Apache module. Needed for Apache and LVE cooperation — github.com
- CloudLinux Issues — docs.litespeedtech.com
- RFC 5842 — rfc-editor.org