Resource limit reached
Symptoms
- The site returns errors such as "resource limit reached", "too many processes" or a 503 status.
- The site is slow at busy times, then recovers.
- Email, database or cron tasks stop working for a while.
Common causes
- Traffic is higher than the plan can handle.
- A plugin, script or cron job uses too much CPU, memory or processes.
- Disk space or inodes (the number of files) are full.
- The database is large, or has many slow queries.
Safe initial checks
- Open resource usage in the hosting panel. See Resource usage and logs.
- Check disk and file counts for the account. Large mail or backup folders are common causes.
- Check the cron jobs and recent plugin installs. See Cron jobs.
Step-by-step solutions
- Heavy script or cron job. Reduce how often it runs, or fix the script. See Cron jobs.
- Full disk or inode limit. Remove unneeded files, old backups, and large logs, after making a backup. See Website backups.
- Traffic too high for plan. Compare the usage with your plan, and upgrade if the load is normal and expected.
- Slow application. Turn off unused plugins, and clear caches the application created.
How to confirm the issue is fixed
- Resource usage stays within the plan limits during a normal day.
- The site responds normally at busy times.
When to contact support
Contact support if usage is within your plan limits and the errors continue, or if you need a higher limit.
Information to include in a support ticket
- The time the errors started, and the resource usage graph for that period.
- The exact error text from the log.
Related articles
Last reviewed
2026-10-27
