Service Unavailable
The server is up but can't handle the request right now. It's meant to be temporary: overload, maintenance, or an app that isn't ready yet.
A 503 can include a Retry-After header saying when to try again. Load balancers like AWS ALB and HAProxy also return 503 when they have no healthy backend to send the request to, which usually means every instance is failing its health check.
What we see on Larm
Failed HTTP checks on Larm from 9 October to 8 November 2026, across about 130 monitors.
19 monitors got a 503 in this period, with 2,797 failed checks in total. By number of monitors it's the second most common failure, after 502.
COMMON CAUSES
HOW TO FIX IT
What this means for monitoring
A short 503 during a deploy is normal for some setups. A 503 that outlasts the deploy means the new version didn't become healthy. Larm's confirmation window keeps short deploy blips from alerting.
Related status codes
5xx Server Error
Something went wrong on the server and it has nothing more specific to say. It's what most frameworks return when your code throws an exception it doesn't handle.
A server in the middle, like a load balancer, reverse proxy or CDN, tried to pass your request on to the server behind it and got back something it couldn't use. Either the upstream server didn't answer properly, or the connection closed before a full response came back.
A proxy or load balancer forwarded your request and gave up waiting for the server behind it to answer.
Cloudflare-specific. Cloudflare connected to your origin server and got a response it couldn't use, or no response at all.
Cloudflare-specific. Cloudflare tried to connect to your origin server and the connection was refused.
Cloudflare-specific. Cloudflare tried to connect to your origin and the connection timed out.
Cloudflare-specific. Cloudflare can't find a network route to your origin server.
Cloudflare-specific. Cloudflare connected to your origin but couldn't complete the TLS handshake with it.
Cloudflare-specific. Cloudflare couldn't find where to send the request: it couldn't resolve the origin's hostname, or the Cloudflare Tunnel for it isn't connected.
Get alerted when your endpoints return unexpected status codes.
Larm checks your HTTP endpoints from multiple global locations and alerts you when they return status codes outside your expected range.