A 503 Service Unavailable error means the server is reachable but temporarily unable to handle your request. Unlike a 500 error, a 503 signals "try again later": the service is overloaded, in maintenance, or the application behind it is not running. Finding which one tells you whether to wait or act.
Before you start
- Note whether the 503 affects all pages or just some, and whether it comes and goes.
- Access to cPanel to view resource usage and logs.
Common causes of a 503 error
- Account resource limits – too many concurrent processes (entry processes) or memory, often from traffic spikes or bots.
- Maintenance mode left on by a plugin or framework (for example Laravel's
php artisan down). - A stopped application such as a Node.js or Python app in cPanel.
- Aggressive crawlers or attacks flooding the site.
- Server-wide maintenance or overload (rare and short).
How to fix a 503 error
- Check resource usage. In cPanel → Metrics → Resource Usage, look for entry process (EP), CPU or memory faults at the times of the 503. If you see them, see resource limit reached.
- Find heavy traffic. Check Metrics → Visitors or the raw access log for bots hammering pages like
xmlrpc.php, search URLs orwp-login.php, and block them. See protect WordPress login and XML-RPC. - Enable caching. LiteSpeed Cache serves pages without starting PHP, which removes most load spikes.
- Turn off maintenance mode. Delete WordPress
.maintenancefiles, disable maintenance plugins, or runphp artisan upfor Laravel. - Restart applications. In Setup Node.js App or Setup Python App, restart the app and read its log.
- Contact support if resources look normal and the 503 persists; mention the time and URL.
Note: On LiteSpeed servers a 503 can also come from the PHP handler itself. Our LiteSpeed 503 guide covers that case specifically.
FAQ
How long does a 503 error last?
Traffic spikes pass in minutes; limits reached constantly need optimisation or a bigger plan.
Does a 503 hurt SEO?
Google treats short 503s as temporary. Long-running ones can lead to deindexing.
Is 503 the same as 508?
Both can come from resource limits; 508 specifically means the CloudLinux limit was hit.