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.
- 400Bad RequestThe server could not parse the request and refused to handle it.
- 401UnauthorizedThe server wants authentication, and this request did not pass it.
- 403ForbiddenThe server understood the request and refused to serve it.
- 404Not FoundThis URL is not on the server. The host itself may still be up.
- 408Request TimeoutThe server waited for the client to finish sending, then gave up.
- 429Too Many RequestsA rate limit rejected this client. The application may be healthy.
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.
- 500Internal Server ErrorThe application failed while handling a request it understood.
- 502Bad GatewayA proxy received an invalid response from the server behind it.
- 503Service UnavailableThe server is reachable and is refusing new work for the moment.
- 504Gateway TimeoutA proxy connected to the origin and never got a response in time.
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.
- 520Web Server Returned an Unknown ErrorCloudflare connected, and the origin’s reply was empty or not valid HTTP.
- 521Web Server Is DownCloudflare reached the origin IP, and the origin refused the connection.
- 522Connection Timed OutCloudflare tried to open TCP to the origin and the handshake never finished.
- 523Origin Is UnreachableCloudflare could not find a route to the origin server.
- 524A Timeout OccurredCloudflare connected and the origin did not finish a response in time.
- 525SSL Handshake FailedCloudflare could not complete a TLS handshake with the origin.
- 526Invalid SSL CertificateCloudflare rejected the certificate your origin presented.
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.