503 Service Unavailable: what it means and what to do
A 503 means the server is alive and answering, but has deliberately decided it cannot handle requests right now. The official definition in RFC 9110 is that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance. Temporary is the key word: a 503 is the server asking the world to come back shortly, and it often includes a Retry-After header saying roughly when. Planned maintenance pages, traffic spikes, and deploy restarts are the everyday causes.
If you are just visiting a site
- Wait, then retry. Minutes is the normal scale. Maintenance windows and traffic surges pass, and the same address starts working again without you changing anything.
- Respect the pause. Refreshing every few seconds during an overload adds to the load causing the problem. Give it a few minutes between tries.
- Check the service's status page or social account. Larger services announce maintenance and incidents there, often with an estimated end time.
- Be suspicious if only you ever see it. If everyone else reaches the site fine, a local caching or DNS oddity may be steering you to a retired server. Restarting your router or switching network is a fair test.
If it is your site
- Send Retry-After during maintenance. It tells browsers and crawlers when to return, which protects your search presence far better than letting them guess.
- Return 503, not 200, on maintenance pages. A maintenance page served with a success code can get indexed in place of your real content. The 503 exists precisely to prevent that.
- Find the capacity trigger if it is not maintenance. Recurring 503s under load mean something saturates: connection pools, worker processes, a database limit. The server error log names which.
- Scale or shed load deliberately. Queueing, a static fallback page, or a CDN waiting room all beat the server falling over unevenly on its own.
Visitors: a 503 is a rain check, wait it out. Owners: an unplanned 503 pattern is a capacity alarm, and a planned one without Retry-After is a self-inflicted SEO problem.
Common questions
How long does a 503 last? As long as the overload or maintenance lasts. Short spikes clear in minutes. Announced maintenance usually publishes a window. A 503 that lasts for days on a site you rely on usually means the owner has a bigger problem or has not noticed.
What is the difference between 502, 503, and 504? A 502 means a gateway got an invalid response from the backend. A 503 means the server itself is temporarily unavailable, by overload or by choice. A 504 means a gateway waited for the backend and the backend never answered in time.
Related errors