← Back to status codes
HTTP Status Code
503 Service Unavailable
Server ErrorThe server is temporarily unable to handle the request.
HTTP status code reference, response example, common causes, fixes, and related status codes.
What does HTTP 503 Service Unavailable mean?
HTTP 503 Service Unavailable is a status code sent by a server to indicate the result of an HTTP request.
Status codes help browsers, APIs, apps, and backend systems understand whether a request succeeded, failed, was redirected, or needs additional action.
In practice, HTTP 503 Service Unavailable usually appears when a server responds under specific request, validation, permission, or infrastructure conditions.
Response example
HTTP/1.1 503 Service Unavailable Retry-After: 120
HTTP example
HTTP/1.1 503 Service Unavailable
Relevant headers
Retry-After
Retry-After: 120
Common causes
- Server overload
- Maintenance window
- Temporary backend outage
How to fix it
- Retry later
- Scale infrastructure if overloaded
- Check maintenance or deployment status
Common mistakes
- Assuming the status code alone explains the full backend issue
- Ignoring related response headers that add important context
- Treating temporary errors as permanent failures
- Retrying too aggressively without checking the cause
- Debugging the frontend only when the problem is server-side
How browsers and APIs use it
Browsers, APIs, and backend services use HTTP status codes to understand the outcome of a request. Depending on the status code, an application may render content, retry a request, redirect the user, show an error, or trigger a different flow in the client or server.
Developer note
HTTP 503 often means a temporary failure. If you're building a client app, treat it differently from a permanent 4xx error.
Client-side example
if (response.status === 503) {
console.log("Service temporarily unavailable");
}