Server error · 503
503 Service Unavailable
A 503 Service Unavailable means a server that is otherwise able to speak HTTP is not ready to handle this request. It is a deliberate “not now,” used for overload, startup, and maintenance.
HTTP status codes explained · the longer reference on the blog.
What 503 means
Unlike a connection refusal, something accepted the TCP connection and wrote a 503. Unlike a 500, the server is not claiming that a bug broke this particular request. It is claiming it cannot take the work. A Retry-After header, when present, tells clients and crawlers when to come back. Search engines treat a 503 with Retry-After as a temporary state.
The code shows up in three honest situations: the process is still booting, the process is overloaded and shedding load, or someone enabled a maintenance page. It also shows up when a platform’s edge cannot find a healthy upstream and answers 503 on the app’s behalf. A short 503 during a deploy is common. A 503 that stays up is an incident.
Common causes
The app is starting or restarting
A new instance has opened its port and is not ready for traffic yet: migrations running, caches cold, or a readiness check failing. The load balancer still has the instance in rotation, or the only instance is this one.
Overload or a worker pool at its cap
Every PHP-FPM worker, database connection, or request slot is busy. New requests get 503 so the process stays alive. Latency just before the 503s is the clue.
A maintenance switch is on
A deploy hook, a CMS plugin, or an env flag is serving a maintenance document with 503. The app may be healthy underneath the flag.
No healthy upstream
The orchestrator has zero ready pods, or the host’s proxy has no live backend. Visitors get 503 from the edge even though the failure is “nothing is ready.”
How to fix it
Read Retry-After and the page copy
A maintenance page that names a window is a planned hold. An empty 503 from the platform is an incident. The header tells clients when a retry is welcome.
Check readiness, not only liveness
A process can be alive and still refuse traffic. Look at the ready count, the deploy in progress, and whether the maintenance flag is set.
If it is overload, add capacity or shed cheaper
Look at worker saturation, database connections, and a sudden traffic spike. Restarting a saturated pool without more capacity brings the 503 back.
Turn maintenance off when the release is done
Confirm the flag, the plugin, and any CDN bypass cookie. Then request the URL with a cache bypass so you are not seeing a stored 503.
Is it your site, or just you?
A 503 is the same for anonymous visitors. Check from a phone on cellular data. If they see it too, it is not your browser profile.
The homepage checker reports the status from our servers. HTTP 503 there means the refusal is visible off your network. If the checker gets 200, your request may be stuck on a cached 503 or an old DNS target.
How to monitor for 503
Expect 200 on the public URL. A 503 fails the monitor. During a planned maintenance window the status is still a real 503 — pause the monitor if you do not want an alert, or leave it running if you want to know when the window started. There is no separate maintenance calendar in the product. The second consecutive failure is what triggers the first alert, so a deploy that returns 200 on the next check stays quiet.
The checker on the ismysiteup homepage requests the URL from our servers and shows the HTTP status, response time, and SSL details. No account is required, and that checker allows 5 checks per hour from the same network. A free account watches 5 URLs, each checked every 10 minutes, and sends alerts on WhatsApp, Telegram, Slack, or email. A monitor expects HTTP 200 unless you set a different expected status (100–599). One failed check is confirmed with a second check before the first alert, and a later success sends a recovery alert. Pro (every 5 minutes) and Business (every minute) are listed on the pricing page; paid checkout is not open yet.
Related status codes
- 500Internal Server ErrorThe application failed while handling a request it understood.
- 502Bad GatewayA proxy received an invalid response from the server behind it.
- 504Gateway TimeoutA proxy connected to the origin and never got a response in time.
- 429Too Many RequestsA rate limit rejected this client. The application may be healthy.
FAQ
What does 503 Service Unavailable mean?
The server can answer HTTP and is not taking this request right now. Overload, startup, and maintenance are the usual reasons.
Should a maintenance page use 503?
Yes. A 503 tells clients and crawlers the hold is temporary. Pair it with Retry-After when you know the window. A 200 maintenance page looks like the site is up.
How fast will I know about a 503?
On the free plan, checks run every 10 minutes, and the first alert waits for a second failed check. Pro (every 5 minutes) and Business (every minute) are on the pricing page and are not open for checkout yet.