Knowledge Base
What does a hosting resource limit mean?
A resource limit controls how much processing power, memory or other server capacity your hosting account can use at once. Reaching a limit can slow the website or cause errors even when storage is not full. Open cPanel → Resource Usage → Details or Current usage, choose the Timeframe that covers the problem and compare Usage, Limit and Fault.
Find the relevant time
- Sign in to your account, open Services, find the hosting service and choose Log in to cPanel.
- Use Search Tools to open Resource Usage under Metrics. The dashboard summarises recent issues; choose Details or Current usage to see the measurements.
- Set Timeframe to the period when the website was slow or showed an error. Adjust Time Unit for a closer or broader view. A quiet reading now does not rule out a problem earlier in the day.
- Look at which measurements reached their limits and whether Fault increased. A fault count records a limit being reached; it is not proof of a broken server or a security incident.
What the names mean
- SPEED / CPU: processing power used to run website requests. Heavy plugins, busy pages or background jobs can use it up.
- Physical Memory Usage / PMEM: working memory needed while code runs. This is different from the space used to store files.
- Entry Processes / EP: requests entering the account at the same time. This is not a simple count of visitors; requests can overlap and take different amounts of time.
- NPROC: running processes, including work in the background. I/O is how quickly the account reads or writes data; IOPS counts those operations.
- Disk Usage is stored data such as files, mail and backups. Check it separately on cPanel Tools or in Disk Usage. An unlimited number of domains or an unlimited traffic allowance does not mean unlimited CPU or memory.
What to do next
- Record the time, affected address, error and measurement that reached its limit. Check whether this coincided with a backup, import, scheduled task, traffic increase or website update.
- For WordPress, follow the slow-website checks. Reduce unnecessary work and test one change at a time. Do not disable every plugin or security control on a live site as a first step.
- If limits are reached regularly, ask us to review the workload and plan. More resources may help a busy site, but an upgrade alone does not fix faulty code or an unwanted traffic source.
- Open Support → New Ticket, select Tech/Server and include the domain, timeframe and a screenshot of the relevant readings. We can help distinguish a brief spike from a recurring capacity problem.