Skip to the content

503 Service Unavailable

The server can't handle the request right now, because it is overloaded or down for maintenance. It is meant to be temporary.

Class
5xx Server error. The request may have been fine, but the server failed to fulfil it.
Defined in
RFC 9110

What it looks like

HTTP/1.1 503 Service Unavailable
Retry-After: 3600

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the site is deliberately or unavoidably not answering: maintenance mode, more visitors than it can handle, a load balancer without a healthy server to send the request to, an application that is still starting up. A Retry-After header can say when to come back.

What to do about it

As a visitor: try again in a few minutes. As a program: wait, do as Retry-After says, and build in retries with growing pauses.

As the owner: for planned maintenance, a 503 with Retry-After is exactly the right answer, far better than a 200 with a "back soon" page or a 404. For the unplanned kind, find out what ran out: worker processes, memory, database connections.

Not to be confused with

502 Bad GatewayA proxy got a broken answer, or none, from the server behind it.
504 Gateway TimeoutA proxy waited too long for the server behind it.
429 Too Many RequestsOnly this client is asked to slow down.

How Google treats it

Google takes a 503 as temporary. It slows its crawling and keeps the pages in its index for the time being. Pages that go on returning it are removed in the end, so don't leave a site in maintenance mode for long.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12