Skip to content

HTTP Status Codes Explained: 200, 404, 503 and More

Updated November 16, 2026 · 6 min read

Every time your browser asks a website for a page, the server answers with a three-digit number first. That HTTP status code sums up how the request went, and when something breaks it's often the most useful clue you have.

Quick answer

HTTP status codes tell you how a server handled a request. Codes in the 200s mean success, 300s mean redirect, 400s mean the request was refused or something was wrong on the visitor's side, and 500s mean the server (or something in front of it) failed. Cloudflare's 52x codes mean Cloudflare was working but couldn't get a proper answer from the website behind it.

When you run a check with Is It Down Everywhere?, we show the status code we received, so this guide is your decoder ring.

The five families at a glance

  • 1xx, informational: "Got it, keep going." You'll almost never see these.
  • 2xx, success: the server understood the request and answered it.
  • 3xx, redirection: the content lives somewhere else, so go there.
  • 4xx, client errors: the server refused the request or couldn't find what was asked for.
  • 5xx, server errors: the request looked fine but the server couldn't deliver.

The first digit tells you who's probably at fault. A 4xx usually points at the request, and a 5xx points at the website.

The codes you'll actually meet

Code Name What it means in plain English Is the site down?
200 OK Everything worked. No
301 Moved Permanently The page has a new permanent address and you're being sent there. No
302 Found (temporary redirect) The page is temporarily somewhere else, often a login or regional page. No
403 Forbidden The server is up but refuses to serve this request. Usually not
404 Not Found The server is up but that page doesn't exist. No, just that page
429 Too Many Requests You (or the checker) asked too often, so the server is slowing you down. No
500 Internal Server Error Something crashed inside the website's own code. Yes, at least partly
502 Bad Gateway A server in the middle got a bad answer from the server behind it. Yes, usually
503 Service Unavailable The server is overloaded or in maintenance. Yes, temporarily
504 Gateway Timeout A server in the middle waited too long for the server behind it. Yes, usually
520 Web Server Returned an Unknown Error Cloudflare got an empty or unexpected reply from the site. Yes
521 Web Server Is Down The site's own server refused Cloudflare's connection. Yes
522 Connection Timed Out Cloudflare couldn't complete a connection to the site's server. Yes
523 Origin Is Unreachable Cloudflare couldn't find a route to the site's server. Yes
524 A Timeout Occurred Cloudflare connected, but the site took too long to answer. Yes, or very slow
525 SSL Handshake Failed Cloudflare and the site couldn't agree on a secure connection. Yes
526 Invalid SSL Certificate The site's own security certificate couldn't be validated. Yes

A closer look at the tricky ones

301 and 302: redirects aren't errors

When we check example.com and get a 301 pointing to www.example.com, that's normal. Most sites redirect between versions of their address or from HTTP to HTTPS. A redirect only becomes a problem if it loops forever. Your browser will then complain about "too many redirects", and clearing cookies for that site often fixes it.

403: up, but not for you

A 403 means the server is alive and decided not to serve the request. For visitors, common reasons are a regional restriction, a security service that thinks your traffic looks suspicious, or a page you need to log in for. For automated checkers like ours, some large sites return 403 to anything that isn't a full browser. That's why a 403 on our check doesn't automatically mean "down".

404: the page is missing, not the site

A 404 means you reached the server and it answered, but there's nothing at that address. Check for typos, or go to the homepage and navigate from there. If a site's homepage returns 404, something has gone wrong with a recent change on their side.

429: slow down

Sites use 429 to protect themselves from too many requests in a short time. If you see it in your browser, wait a few minutes before retrying, and don't keep hammering refresh, because it resets the clock on some sites. A 429 on our check means the site is up but rate-limiting automated requests.

500: something broke inside

A 500 is the server's way of saying "I tripped over my own feet". It's often caused by a bug, a bad deploy or a database problem. There's nothing you can do except wait, though a reload a minute later sometimes works if only some of their servers are affected.

502 and 504: trouble between servers

Big websites are built in layers: a load balancer or CDN at the front and application servers behind. A 502 means the front layer got a broken answer from the back. A 504 means it got no answer in time. Both usually show up during outages, deploys or traffic spikes.

503: overloaded or in maintenance

A 503 is often deliberate. Sites return it during planned maintenance or when they're shedding load to stay alive. It typically clears up on its own, sometimes within minutes.

Cloudflare 52x: the middleman is fine, the site isn't

Many websites sit behind Cloudflare, which handles traffic before passing it on to the site's own server (the "origin"). The 52x codes are Cloudflare telling you exactly that: we're fine, the website behind us isn't. A 521 or 522 usually means the origin server is down or overloaded. A 525 or 526 points to a certificate or HTTPS setup problem on the site's side. None of these can be fixed by visitors.

Errors that don't have a status code

Sometimes there's no number at all, because the connection failed before the server could answer. Your browser then shows messages like DNS_PROBE_FINISHED_NXDOMAIN or ERR_CONNECTION_TIMED_OUT, and our checker reports a timeout or connection error. If the site is up for us but you see one of these, follow our guide to fixing "This site can't be reached".

What to do with this information

  1. 2xx or 3xx on our check, but the site won't load for you? The site is up. The problem is between you and it, so see is it down for everyone or just me?
  2. 403 or 429 on our check? The server is alive. If it also fails for you, you may be blocked or rate-limited.
  3. 5xx or 52x? It's a real problem on the site's side. Wait, and keep an eye on its status page.

Want to understand why servers end up returning 5xx errors in the first place? Our explainer on how website outages happen covers the usual causes. For anything else, the FAQ is a good next stop.