CheckWebsiteNow

Server errors (5xx)

503 Service Unavailable

The website is temporarily unable to handle requests.

Quick answer

A 503 means the server is not ready right now, usually because of maintenance or too many visitors. It is meant to be temporary. The response may say when to try again.

When to wait: Usually yes: try again in a few minutes. Maintenance windows can last longer.

If you are visiting the website

  1. Wait and reload Wait a few minutes, then reload the page once. A 503 is meant to be temporary.
  2. Avoid repeated reloads Reloading again and again adds load and does not speed up recovery. One try every few minutes is enough.
  3. Check the service's status page Big services often publish an official status page that lists known problems and maintenance times.
  4. Look for a maintenance notice Check the site's social media or newsletter. Planned maintenance is often announced there with an expected end time.
  5. Try again at a quieter time During ticket sales, product launches or big news, a 503 can mean too many visitors at once. Coming back later often works.
  6. Tell the website owner if it lasts If the error stays for hours without any notice, contact the website through another channel and mention the address and time.

If you run the website

  1. Check server load and services Look at CPU, memory, connection limits and the health of services you depend on, such as the database, cache or a payment API.
  2. Set a Retry-After header during maintenance Send Retry-After with seconds (for example Retry-After: 3600) or an HTTP date. Google recommends a best-effort date or duration.
  3. Keep 503 maintenance short Google suggests a 503 page for urgent closures of one to two days. For longer pauses, keep an informative home page that returns a normal status.
  4. Handle traffic peaks Add caching, more server capacity or a waiting room (a queue page) before big launches. Test the busiest pages under load first.
  5. Check server error logs Look at your web server and application logs for the time of the error. They usually say whether the app was overloaded, stopped or waiting on another service.

Is the website down?

Partly. The server answers, but it says it cannot serve pages right now. The reason is usually maintenance or too many visitors at once.

Nothing on your device causes a 503. Waiting is the right move for visitors.

How 503 differs from 500 and 429

A 500 says something broke unexpectedly. A 503 says the server is deliberately or temporarily not ready.

A 429 slows down one visitor who sent too many requests. A 503 affects everyone at the same time.

For developers: what happens technically

The server cannot produce a proper response for now. Load balancers send 503 when no healthy backend is left, and many apps send it in maintenance mode.

A Retry-After header is optional but helpful. Without it, clients must guess when to come back.

Common questions

How long will a 503 last?

Often minutes. Planned maintenance can take an hour or more. If the response contains a Retry-After value, that is the site's own estimate.

Is the website closed for good?

Very unlikely. A 503 means temporary unavailability. A site that is shut down permanently usually disappears from DNS or shows a notice instead.

Why does this happen during sales and ticket releases?

Many people arrive at the same second, and the servers run out of capacity. Some sites then answer 503 or show a queue page to protect themselves.

Does a 503 hurt my site in Google?

Short ones do not. Google slows its crawling and keeps indexed pages for a while, but long-lasting server errors can lead to pages being dropped.

Can I do anything to get in faster?

Not really. Reloading often makes the queue longer for everyone. If the site offers a waiting room or email alert, use that instead.

Likely causes

  • Common Planned maintenance. (Website side)
  • Common Too much traffic or not enough server resources. (Website side)
  • Sometimes A required service behind the website is down. (Website side)

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: