The 503 Service Unavailable error indicates the server is temporarily unable to process the request. Unlike 500, 503 suggests a transient state that should resolve.
It's the appropriate code for planned maintenance or temporary overload.
Symptoms
- HTTP 503 code: Service Unavailable in the response.
- Retry-After header: often accompanied by an indication of when to retry.
- Maintenance page: some services display an explanatory page.
Common Causes
- Maintenance: planned unavailability for update or deployment.
- Overload: too many simultaneous requests, saturated server.
- Circuit breaker: automatic protection activated due to repeated errors.
- Dependency down: critical service unavailable (DB, cache, third-party API).
Automate with MoniTao
- 503 alerts: configure a specific alert for 503 errors.
- Maintenance windows: temporarily disable alerts during planned maintenance.
Frequently Asked Questions
Is 503 less serious than 500?
503 indicates an expected temporary state. 500 indicates an unexpected error. 503 is "normal" during maintenance.
How to implement a 503 for maintenance?
Configure your load balancer or a maintenance.html file with the 503 code.
Should I alert on all 503s?
Alert if the 503 isn't related to planned maintenance or lasts too long.
How to handle 503s client-side?
Respect the Retry-After header and implement automatic retry with backoff.
Ready to Sleep Soundly?
Start free, no credit card required.