How to use it
- Enter the address of the page that shows 503.
- Read the status code. 503 from our servers too means the site is unavailable for everyone.
- Wait and check again, or follow the fixes below if only you get the error.
What 503 Service Unavailable means
The MDN reference defines 503 as a server error that indicates the server is not ready to handle the request. The important word is temporary. A 503 says "not now", not "never". That is the difference to a 404 (nothing at this address) or a 403 (you are not allowed).
A server that sends 503 should also send a Retry-After header with an estimate of when the service will be back, either as a number of seconds or as a date. Many sites skip it, so a missing value does not mean the outage will be long.
Why servers send 503
MDN names two common causes. The first is maintenance: administrators route all traffic to a 503 page while they update software or move servers, and some platforms do this automatically during updates. The second is overload: when memory, CPU or the pool of connections runs out, the application rejects new requests with 503 instead of crashing.
| Situation | Typical signs | What to expect |
|---|---|---|
| Planned maintenance | A branded page that says "back soon", often with a Retry-After header | Back at the announced time |
| Traffic spike | Error comes and goes, ticket sales, game launches, breaking news | Better when the rush ends |
| Overloaded API | The app fails, the website still opens | Watch the official status page |
| Hosting limits | Small sites on shared hosting, error at busy times | Until the owner upgrades or caches |
Is it down for everyone?
The check above sends the request from our servers. If it also gets 503, the site is unavailable for everyone and there is nothing to fix on your side. If our check gets 200 while you still see 503, the cause is closer to you: a cached error page, a VPN or proxy that is overloaded, or a different server that your region or network is routed to.
MDN also notes that 503 responses usually should not be cached, because people would keep seeing the error after the fix. Some setups cache them anyway, which is why a private window is worth a try.
What you can do as a visitor
- Wait a minute, then reload once. Overload errors are often gone quickly. Repeated fast reloads add load and can trigger a 429 limit on your address.
- Look for a maintenance notice. The official status page or the service's account on social media usually announces planned work and the end time.
- Try a private window. If the page loads there, clear the cache for the site.
- Turn off the VPN or proxy. A busy VPN exit or company proxy can produce its own 503.
- Use the app or the website instead. They often run on separate servers, so one may work while the other is overloaded.
What you can do as the site owner
For maintenance, return 503 with a Retry-After header instead of a 200 page that says "under maintenance", so browsers and crawlers know it is temporary. Google slows down crawling when it sees 5xx answers and keeps indexed pages for a while, but its documentation says URLs that persistently return a server error are removed from the index. For overload, look at the limits that are hit first: worker processes, database connections, memory. A cache or CDN in front of static pages removes most of the load. When you are back, confirm it from outside with the website down checker.
Related errors
A 502 Bad Gateway comes from a proxy that got a broken answer from the server behind it. If your browser shows This site can't be reached, no server answered at all. The full list is in HTTP status codes explained.
Frequently asked questions
Does 503 mean the website is down?
For you, yes, for now. The server is running and answers, but it refuses to handle the request at the moment. That is usually planned maintenance or overload, and both are temporary by design.
How long does a 503 error last?
Maintenance pages often last minutes to a few hours. The server can say how long in the Retry-After header, which some maintenance pages also print as text. Overload errors come and go with traffic, so they often disappear once a rush is over.
What is the difference between 503 and 429?
A 503 is about the server: it cannot take any more work right now. A 429 Too Many Requests is about you or your network: you sent more requests than the site allows. MDN notes that rate limits of specific clients should use 429, not 503.
Why do I get 503 on one app but not in the browser?
Apps and websites often use different servers. The app may call an API that is overloaded while the website is served from a cache. Check the official status page of the service, which usually lists the API separately.
Will refreshing make it worse?
Refreshing every second adds load to a server that is already struggling and can get your address rate limited. Wait at least a minute between tries.
I run the site. Will a 503 during maintenance hurt my Google ranking?
Google slows down crawling when it sees 5xx errors and keeps already indexed pages for a while. Pages that return server errors persistently are removed from the index, so keep maintenance short and send a Retry-After header.