HTTP 503 Service Unavailable
Temporarily closed: the server is alive but cannot take requests right now — overloaded or under maintenance.
What HTTP 503 means
HTTP 503 Service Unavailable is the polite downtime signal: the server exists and works, but is temporarily refusing traffic because of overload, maintenance or an upstream dependency being unavailable. A Retry-After header tells clients when to come back.
503 is deliberately different from 500: nothing is broken, capacity is just not there right now. That distinction is exactly what crawlers and API clients use to decide how to react.
Common causes of 503 errors
- Planned maintenance mode (many platforms serve 503 while deploying).
- Traffic spikes exhausting workers, connections or autoscaling limits.
- A dependency (database, cache) being restarted, causing the app to refuse requests.
- DDoS protection or connection limits shedding load.
- Web host suspending or throttling a site that exceeded its plan.
How to fix it as a visitor
- Wait and retry — 503 is temporary by definition.
- Check the site's status page or social accounts for maintenance announcements.
How to fix it as a site owner
- Send Retry-After with a realistic estimate during maintenance windows.
- Fix capacity: scale workers/instances, add caching, queue expensive work.
- Make health checks distinguish “booting” from “dead” so orchestrators do not flap.
- Keep maintenance 503s short — serve cached pages if you can instead of going dark.
Example response
HTTP/1.1 503 Service Unavailable Retry-After: 120 Content-Type: text/html <html><body><h1>Down for maintenance, back in 2 minutes</h1></body></html>
SEO impact
503 is the SEO-safe way to be down: Googlebot understands “temporarily unavailable”, retries later and keeps your pages indexed. Serving maintenance pages with 200 (duplicate content) or 404/410 (deindexing!) during downtime is how sites lose rankings by accident.
FAQ
Should maintenance pages return 503?
Yes, with a Retry-After header. It tells crawlers the outage is temporary and protects your search rankings.
How long can a site serve 503 safely?
Days rather than weeks. Google treats prolonged 503s (roughly beyond a week or two) as a sign the site may be gone and starts dropping URLs.
What is the difference between 500 and 503?
500 means the server failed while processing; 503 means it deliberately refused because it is overloaded or in maintenance.