508 Resource Limit Is Reached Error
Visitors see "508 Resource Limit Is Reached" instead of your pages — your hosting account hit its cap on processing power or memory, and the server refused to build the page.
Common signs of this issue
- Pages show "508 Resource Limit Is Reached" or simply "Resource Limit Is Reached" on a plain white page.
- The error comes and goes — the site works for a while, fails when it gets busy, then works again.
- It tends to appear at the same times of day, or whenever more than a handful of people use the site at once.
- The site may feel sluggish in the minutes before the error starts appearing.
- Your hosting dashboard (often cPanel) shows warnings about CPU, memory, or entry processes, or usage graphs pinned at 100 percent.
- You may have received an email from your host saying the account is exceeding its resource limits.
- Only your site — and any other sites on the same hosting account — is affected.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Log in to your hosting control panel and find the resource usage graphs — on cPanel, look for "Resource Usage" or the small CPU, memory, and entry-process meters. This is the single most useful check — it shows which limit is being hit and when.
- Note the timing. Spikes at the same hour every day point to a scheduled job — a backup, an export, a plugin's automatic task. Spikes that match your busy hours point to real visitor traffic.
- Check whether the limit being hit is entry processes — the number of page requests the server will work on for you at the same moment, often only 10 to 20 on shared plans. A slow site burns through those slots fast, because each visitor occupies one for longer.
- Ask what changed recently — a new plugin, a redesign, an email campaign, or an ad or mention that could be sending a wave of visitors. A traffic spike hitting your limits can be good news wearing an error message.
- Look at your traffic statistics for unfamiliar surges. Floods of visits from countries you do not sell to, or from "bots" and "crawlers," mean automated traffic is burning your allowance rather than real customers.
- Find your plan's published limits on your host's comparison page. Seeing how small your CPU, memory, and entry-process numbers are can be clarifying.
- If the graphs show heavy load even overnight with no visitors, treat that as a red flag — a runaway plugin, a stuck scheduled task, or malware can all produce load that never sleeps.
What this usually means
A 508 is a shared-hosting error. On most inexpensive hosting, many accounts share one physical server, and the host puts a fence around each account: so much processing power, so much memory, so many simultaneous page requests ("entry processes"). When your account hits a fence, the server does not slow everyone else down — it simply refuses to build your page and shows the 508 instead, which is why the error comes and goes with load.
What pushes an account into the fence varies. Sometimes it is genuinely more visitors than the plan was sized for — an ad landing or a mention taking off. Just as often it is waste: a heavy or misbehaving plugin doing expensive work on every page view, a scheduled task that never finishes, aggressive bot traffic that is not customers at all, or a hacked site quietly running someone else's code on your account.
This matters because there is an honest fork in the road. If the usage is legitimate — real customers on a reasonably lean site — the fix is a bigger hosting plan, and that is money well spent. But if a plugin, bot traffic, or malware is burning the resources, upgrading just buys a bigger bucket for the same leak. The usage graphs, and what the load lines up with, tell you which side of the fork you are on.
What not to do
- Don't keep refreshing the page. Every reload asks the server to do the same work again and holds the account at its limit longer.
- Don't upgrade your hosting plan on the spot without looking at the usage graphs first — if the cause is a leak rather than real traffic, you will pay more every month and hit the same wall soon.
- Don't install a cache or optimization plugin as a panic fix while the site is over its limits; that is itself heavy work for a struggling account.
- Don't delete plugins at random. Deactivate one suspect at a time and watch the graphs, so you know what actually helped.
- Don't ignore a 508 that started with no change in your real traffic. Load that appears from nowhere is how bot floods and hacked sites announce themselves.
- Don't migrate to a new host mid-crisis. If the underlying cause travels with the site, so does the problem.
When to get help
The moment to bring in a professional is when the usage graphs show heavy load and you cannot say what is causing it. Someone who can read server logs and plugin behavior can usually pinpoint the culprit — a specific plugin, a scheduled task, a bot flood, or malware — in an hour or two, and that answer determines whether you need a cleanup, a configuration change, or genuinely a bigger plan. That is cheaper than guessing: an unnecessary hosting upgrade costs you every month forever, and an undetected hacked site costs far more than that.
Could your hosting be the problem?
If your host is slow, unreliable, or hard to deal with, moving to a better one can clear up issues like this for good. One we genuinely recommend is Instant Access Internet Services — a smaller, compassionate company with 30 years in the business, known for being one of the fastest, with great management and low pricing. (Just a recommendation — no affiliate link, no kickback.)
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
What does 508 Resource Limit Is Reached mean?
Your hosting account hit the cap your host places on processing power, memory, or simultaneous page requests, so the server refused to build the page. It is a capacity limit being enforced, not a broken site — which is why it comes and goes with load.
What are entry processes in cPanel?
The number of page requests the server will handle for your account at the same moment — often only 10 to 20 on shared hosting. When all slots are busy, additional visitors get the 508 error. Slow sites hit the limit sooner because each request holds a slot longer.
Will upgrading my hosting plan fix a 508 error?
Only if the resource use is legitimate — real visitors on a reasonably efficient site. If a plugin, bot traffic, or malware is consuming the resources, a bigger plan just delays the same error.
Why does the 508 error come and go?
The limits are enforced moment to moment. When usage drops below the cap the site works again; when load returns, so does the error. That on-and-off pattern is the signature of a resource limit rather than an outage.
Can bot traffic cause a resource limit error?
Yes, and it is common. Aggressive crawlers and bots can generate far more requests than your real visitors do, burning your allowance on traffic that will never buy anything.
Does a 508 error mean my site was hacked?
Not usually, but it is worth ruling out. A hacked site often runs extra code on every page view or sends spam in the background, producing load that does not match your visitor numbers — especially load that continues overnight when nobody is browsing.