← All status codes
503

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

More traffic than the app can handle
Maintenance mode is switched on
The app is still starting after a deploy or restart
Every backend is failing the load balancer's health checks
Autoscaling hasn't caught up with traffic

HOW TO FIX IT

Check whether a deploy or maintenance is in progress
Check the health of the targets behind your load balancer
Check load and scale up if the app is overloaded
Check that the health endpoint the load balancer uses responds

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

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.