How to check Resource Usage in cPanel when error 508 appears

Category: cPanel

The message 508 Resource Limit Is Reached appears when your hosting account reaches a temporary resource limit, such as CPU, memory, entry processes, or disk read/write activity. In cPanel, Resource Usage helps you confirm whether it was a one-time spike, unusual traffic, a scheduled task, or a site that needs optimization.

Before you start

You need access to cPanel for the affected domain.
Write down the approximate time when you saw the 508 error, slowness, or intermittent downtime.
If you use a CMS, identify whether the issue started after updating a plugin, theme, or PHP version.
Do not delete files or disable the whole site before checking the spike time first.

Steps

Log in to cPanel and search for Resource Usage. In some panels it may appear as Uso de recursos or inside a metrics section.
Open the report and check whether you see a notice such as Your site had issues in the past 24 hours or an equivalent message.
Open the report details to see hourly or daily graphs.
Compare the error time with CPU, memory, entry process, I/O, or process count spikes.
If the spike matches CMS activity, check recent plugins, wp-cron.php tasks, forms, bots, or unusual traffic before changing settings at random.
If the spike already ended, monitor for a few more hours before opening a ticket; if it repeats, save the exact time and the resource that reached the limit.

What to check in the report

Indicator	What it can mean	First safe change
High CPU	Many visits, heavy plugins, internal searches, or long PHP processes.	Enable cache, pause nonessential plugins, and review recent tasks.
High memory	PHP scripts consuming more memory than usual.	Check plugins, PHP version, and `memory_limit` if the site requires it.
Entry Processes	Many simultaneous PHP requests.	Check bots, forms, uncached pages, or repeated AJAX calls.
High I/O	Heavy disk read/write activity.	Check backups, imports, misconfigured cache, or large downloads.

Final verification

The error time matches a visible spike in Resource Usage.
You identified which resource reached the limit: CPU, memory, entry processes, I/O, or processes.
You applied a focused change, such as enabling cache, pausing a recent plugin, or stopping a scheduled task.
The site loads again without showing 508 Resource Limit Is Reached during the next review.

Common mistakes

The report shows a spike, but you do not know what caused it → You only checked the general summary → open the hourly details and compare them with recent site changes.
The error returns every few minutes → A scheduled task, bot, or plugin is running at intervals → check cron jobs, forms, and CMS activity.
You raised memory_limit and the site is still slow → The limit reached was not PHP memory → go back to the report and confirm whether the spike was CPU, I/O, or entry processes.

When to ask for help

Open a ticket if the resource reaches the limit several times a day, if the site stays unreachable even though you made no recent changes, or if you cannot identify the process causing the spike. Include the domain, approximate time, Resource Usage screenshot, and what changes you tried so support can review the case faster.

Still need help?

If this guide didn’t solve your issue, our team can help you via ticket.

Open ticket Go to my account