503
503.my.id
THE 503 ERROR DIAGNOSTIC CENTER

The 5xx family

Five codes. Five different faults.

500
Internal Server Error
502
Bad Gateway
503
Service Unavailable
504
Gateway Timeout
429
Too Many Requests

Every one of them is server-side — and every one points at a different first fix. Telling them apart is the whole job.

connection refused

502 — Bad Gateway

The gateway knocked. Nobody was home.

The door opened onto an empty room: the app process behind the proxy was stopped, crashed, or restarting.

HTTP/1.1 502 Bad Gateway connect() failed (111: Connection refused) while connecting to upstream
FULL
Retry-After: 600

503 — Service Unavailable

Alive, but full. It asks you to wait.

The server is up. Maintenance, a saturated worker pool, or a deliberate rule is turning requests away until capacity returns.

HTTP/1.1 503 Service Temporarily Unavailable Retry-After: 600
upstream timed out

504 — Gateway Timeout

The room exists. It never answered.

The gateway waited, and waited — a slow script or a locked database missed the proxy timeout.

HTTP/1.1 504 Gateway Time-out upstream timed out (110: Connection timed out) while reading response header from upstream

The takeaway

Read the response,
not just the code. Each 5xx has its own first fix.

The Explorer on this page compares all five side by side — meaning, fault, cause, and the lab capture for each.

HTTP Status Codes 500, 502, 503, 504, 429 Compared by 503.my.id.