You received a resource usage alert
WebGee emails you when an account reaches its resource limits. How to find what caused it and what to do about it.
You have received an email saying your account reached its resource limits. Applies to shared and reseller hosting.
The alert is informational — nothing has been suspended. It exists so you find out about a performance problem from us rather than from a customer.
Find the cause
The alert says a limit was reached. cPanel → Resource Usage says which one, when, and what was running at the time.
- In cPanel, open Resource Usage.
- Select the period covering the alert.
- Look at which limit was reached — CPU, I/O, entry processes or memory.
- Open the snapshot for that moment. It lists the processes responsible.
The snapshot is the useful part. Without it you are guessing; with it you usually have the answer directly.
Common causes
In rough order of likelihood:
- A plugin or theme doing too much work per request. Trace it with PHP X-Ray.
- No caching, so every visitor triggers a full page build — LiteSpeed Cache.
- WP-Cron on a busy site, running scheduled tasks on page loads — Replace WP-Cron with a real cron job.
- A heavy cron job on too short an interval.
- Bot traffic — scrapers consume the same resources as customers.
- Malware. A compromised site burns resources doing someone else's work — Scan your site for malware.
Should you upgrade?
Not as the first step. An upgrade raises the ceiling without addressing what is consuming the resources, so a runaway plugin simply consumes more.
Diagnose first. If the snapshot shows legitimate traffic and legitimate work, then an upgrade is the right answer — open a ticket with your Resource Usage figures and we will advise.
If you ignore it
Nothing is suspended for occasional alerts. Sustained overuse degrades your own site — visitors see slow pages, and once entry process or memory limits are involved, 503 errors. Persistent cases affecting server stability are followed up individually.
Related
Fix a 503 "Resource Limit Reached" error
A 503 means your account hit its CPU, memory or entry process limit. How to find what is consuming them and bring usage back down.
Fix the Redis "OOM command not allowed" error
Redis has its own memory limit, separate from your account's. When the cache fills, writes fail with this error until it is cleared or raised.