What HTTP status codes mean for “is it down?”

Last updated: 1 September 2026

HTTP status codes describe how a server responded to a request. On isitdown.me we use them for reachability, not for judging whether the content is what you wanted. This guide maps common codes to our UP, DOWN, and DEGRADED labels.

Codes we treat as UP (reachable)

Any response from 100 through 499 means the server participated in HTTP. Examples visitors ask about:

If you need the homepage content specifically, a 404 on / may feel “down” even when our label is UP. That is a product/content issue, not transport failure.

Codes we treat as DEGRADED

500-599 indicate server or gateway errors: 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout, and so on. We received a response, but the operator signalled trouble. Treat these as “partially there” rather than completely silent.

When there is no code (DOWN)

Timeouts, connection resets, TLS failures, or DNS lookup failure produce DOWN with no reliable HTTP status. That is the closest match to “down for everyone” in the transport sense.

How to read a domain page

Visit /example.com on isitdown.me. You will see the latest status word, numeric HTTP code when available, response time, and whether DNS succeeded. History lists recent visitor checks, not a continuous graph.

FAQ

Why not mark 503 as DOWN? Because the load balancer or server explicitly replied. Operators often use 503 during maintenance while keeping DNS alive. DEGRADED communicates “something answered, but it is unhappy”.

Do you check HTTP (non-TLS)? We attempt HTTPS first on the canonical hostname. Plain HTTP behaviour may differ; our check reflects the HTTPS path described in how we check.

Unsure about a domain? Run a check and compare the code with the explanations above.

Check a domain

Run a live reachability check on the isitdown.me homepage, or open a saved status page at /your-domain.com.

All guides · Back to home