Reference

HTTP status codes

A short reference for the error codes people search when a site looks down. Each page covers what the code means, common causes, what to fix, how to tell a local glitch from a real outage, and how to monitor for it.

Success and redirect codes live in the blog post HTTP status codes explained.

Client errors (4xx)

The server understood the request and refused it. The host is often still up. The URL, the caller, or a rule in front of the app is what failed.

Server errors (5xx)

The site, or a proxy in front of it, failed while handling the request. These are the codes that usually mean an outage for that URL.

Cloudflare errors (520–526)

Cloudflare's own codes, not registered HTTP statuses. The edge returns them when it cannot finish a request to your origin server.

FAQ

Which HTTP codes mean a URL is down?

500, 502, 503, and 504 mean the server or a proxy failed while handling the request. 521 through 526 mean Cloudflare could not finish a request to the origin. A 404 or 403 means the server answered and refused that URL. The host can still be up.

How do I check a status code without an account?

Use the checker on the ismysiteup homepage. It requests the URL from our servers and shows the HTTP status, response time, and SSL details. The same network can run 5 of those checks per hour.

Can I get an alert when a URL starts returning 502 or 503?

Yes. A free monitor checks every 10 minutes, expects HTTP 200 unless you change that, and alerts on WhatsApp, Telegram, Slack, or email after a second failed check. Pro and Business check faster and are listed on the pricing page. Paid checkout is not open yet.