How to Fix Error 508 (Resource Limit Is Reached)
Error 508 means your hosting account briefly hit one of its allocated resource limits, so the server stopped serving requests for a moment. It affects visitors as a short outage, and it points to your site using more than its share, not to a broken server. It is fixable, usually by cutting load or caching. If it keeps happening, a bigger plan on our web hosting may be the answer.
What the error means
On shared hosting, every account gets a fixed slice of the server’s resources so one busy site cannot slow down the rest. On JetHost, that is handled by CloudLinux, which gives each account its own limits for CPU, physical memory (RAM), Entry Processes (the number of requests running at once, known as EP), I/O, and the total number of processes (NPROC). When your site reaches any one of those limits, the server pauses new requests for a short time and returns Error 508. It usually clears on its own within moments, but it tells you the site is pushing against its ceiling.
Common causes
- A sudden spike in traffic.
- Heavy or poorly coded plugins and themes.
- Expensive database queries.
- Bots or crawlers hammering the site.
- No page caching, so every visit rebuilds the page.
- Too many requests running at once.
- Runaway or overlapping cron jobs.
- The WordPress Heartbeat API firing too often.
How to fix it
Start by finding out which limit you hit and when, then cut the load that caused it. The Resource Usage tool in cPanel is your first stop.
- Open cPanel and go to Resource Usage to see which limit was reached and at what time.
- Turn on page caching, such as LiteSpeed Cache, so pages are served without rebuilding each time.
- Optimize your database to speed up slow queries.
- Find and replace heavy plugins that use the most resources.
- Block bad bots that crawl the site too aggressively.
- Reduce how often the WordPress Heartbeat API runs.
- Limit or stagger cron jobs so they do not overlap.
- If you consistently hit the limits, upgrade your plan or move to a VPS.
On JetHost hosting
On JetHost, the Resource Usage tool in cPanel shows exactly which limit you reached and when, so you are not guessing. Our stack uses LiteSpeed, and turning on LiteSpeed Cache cuts server load sharply, which clears most 508 errors on its own. You can also ease the load by lowering the WordPress Heartbeat frequency, covered in our guide to controlling the WordPress Heartbeat API. If your site has simply outgrown shared hosting, our support team can advise on the right plan, or you can step up to a VPS for dedicated resources.
JetHost Experts Tip
Turn on LiteSpeed Cache first. For most sites it cuts CPU and memory use enough to stop 508 errors without touching anything else.
Frequently asked questions
It means your hosting account hit one of its allocated limits, such as CPU, memory, or concurrent processes, so the server paused requests for a short time.
Open cPanel and go to Resource Usage. It shows which limit was reached and at what time, so you can target the cause instead of guessing.
Often, yes. Page caching such as LiteSpeed Cache serves pages without rebuilding them each visit, which cuts CPU and memory use and clears most 508 errors.
If you hit the limits often even after caching and optimizing, your site has outgrown its plan. Upgrade to a larger plan or move to a VPS for dedicated resources.
New Hosting Plan with 80% OFF
Upgrade your website’s home without the heavy bill. Get new hosting plan with a huge 80% discount. Get free SSL, email accounts, and a control panel to manage your site. Enjoy fast performance, secure environment, and 24/7 support – all in one affordable package.
Need more help?
If 508 errors keep coming back, open a ticket through Client Area, then Support Tickets, and we will help you right-size your plan.
