503
Service Unavailable
The server is temporarily unable to handle the request. This is usually due to the server being overloaded with traffic, undergoing maintenance, or having its resources exhausted. A Retry-After header may indicate when to try again.
What does HTTP 503 mean?
The server is temporarily unable to handle the request. This is usually due to the server being overloaded with traffic, undergoing maintenance, or having its resources exhausted. A Retry-After header may indicate when to try again.
Common causes
- 1
The server is overloaded — too many concurrent requests are exhausting CPU, memory, or connection pool capacity.
- 2
Planned maintenance or deployment in progress. The server returns 503 intentionally while updating.
- 3
A dependency (database, cache, external API) is down, and the server cannot serve requests without it.
How to fix it
- 1
If under heavy load, scale up (more resources) or scale out (more instances). Enable auto-scaling if your infrastructure supports it.
- 2
If in maintenance mode, wait for it to complete. If you control the server, check that the maintenance window has not exceeded its expected duration.
- 3
Check downstream dependencies: database connections, Redis, external APIs. A 503 often means a backing service is unreachable rather than the web server itself.
Monitor for HTTP 503 errors
Uptrack distinguishes between brief 503 blips and sustained outages by confirming consecutive failures before alerting. This means you get notified about real downtime, not transient load spikes during a deploy.
Catch HTTP errors before your users do
20 monitors free — 10 at 30s, 10 at 1min. No credit card required.
Start Monitoring Free