503 Service Unavailable

An HTTP 503 Service Unavailable error indicates that the server is temporarily unable to handle the request, usually due to being overloaded or undergoing maintenance. Unlike a 500 error, a 503 implies the condition is temporary and the server is expected to recover. End users should try again later, while developers should investigate capacity and deployment status.

Common causes

• Server is overloaded with too many concurrent requests and has exhausted its worker pool or thread capacity
• The application is undergoing scheduled or unscheduled maintenance and has been intentionally taken offline
• Auto-scaling has not provisioned enough instances to handle a sudden traffic spike
• A required downstream service or dependency (e.g., database, cache, API) is unavailable
• Deployment or rolling update in progress where old instances are terminated before new ones become healthy

How to fix it

• Monitor server resource usage (CPU, memory, connections) and scale up or out if thresholds are exceeded
• Implement a Retry-After header in 503 responses to inform clients when to retry the request
• Configure auto-scaling policies to respond more aggressively to sudden traffic increases
• Set up health checks and circuit breakers for downstream dependencies to degrade gracefully instead of failing entirely
• Use a maintenance page or feature flag system to communicate planned downtime without returning raw error responses

Related HTTP errors