IsSiteUpOrDown

HTTP status codes explained: what 403, 404, 429, 500, 502, 503 and 504 mean

Every time a browser asks a website for a page, the server replies with a three-digit status code before anything else. You normally never see it, but when something goes wrong it's the single most useful clue about where the problem is. IsSiteUpOrDown shows this code on every status page under "HTTP response".

The five families

RangeMeaningIs the site up?
1xxInformational, rarely seenYes
2xxSuccessYes
3xxRedirect: "look over there instead"Yes
4xxProblem with the requestYes, the server answered
5xxProblem on the serverNot properly

That last column is why IsSiteUpOrDown counts any response under 500 as UP: the server is alive and talking, even if it refused this particular request.

200 OK

Everything worked. If you see 200 here but the site won't load for you, the problem is on your side. Start with this checklist.

301 and 302: redirects

The site is sending visitors somewhere else, for example from example.com to www.example.com, or from HTTP to HTTPS. We follow up to five redirects automatically. Endless redirect loops usually come from bad cookies. Clearing them for that site often fixes it.

403 Forbidden

The server understood the request but won't allow it. Common reasons: the content is region-locked, your IP address was blocked, or a security service decided the request looked automated. For you, try turning off a VPN or switching networks. A 403 doesn't mean the site is down.

404 Not Found

The server is fine, but that specific page doesn't exist. Check the address for typos, or go to the site's homepage and navigate from there.

429 Too Many Requests

You (or everyone sharing your IP address, such as an office or university network) sent too many requests too quickly. Wait a few minutes. It clears by itself.

500 Internal Server Error

A generic "something crashed" from the website's own software. It's the site's problem. Reloading occasionally works if the fault was temporary, but usually you just have to wait for them to fix it.

502 Bad Gateway

Most large sites sit behind a front door (a load balancer or CDN such as Cloudflare). A 502 means the front door is working but the server behind it sent back nonsense or nothing. It's a classic sign of an outage in progress, often during deployments or traffic spikes.

503 Service Unavailable

The server is deliberately turning people away, because it's overloaded or down for planned maintenance. Sites often show a friendly maintenance page with this code. Check back later.

504 Gateway Timeout

Like a 502, but the server behind the front door didn't answer in time. Common when a site's database is struggling under load.

No code at all

Sometimes there's no status code because no server answered. IsSiteUpOrDown shows these as:

Quick rule: 4xx means "it's about your request", 5xx means "it's about their server", and no code means "nobody answered".
Is a site not loading right now?

More guides

TroubleshootingBasics Is it down for everyone or just me? How to tell in 60 seconds A quick, reliable routine to work out whether a website is really down or the problem is your browser, device, network or internet provider. 5 min read DNSHow-to How to flush DNS on Windows, Mac, Linux, iPhone and Android Step-by-step commands to clear the DNS cache on every major system and browser, plus when flushing DNS actually helps and when it doesn't. 6 min read OutagesExplainer Why websites go down: the 7 most common causes of outages From traffic spikes to expired domains and cloud provider failures, here is what actually takes websites offline and how long each kind of outage usually lasts. 6 min read

How useful is IsSiteUpOrDown?

No ratings yet. Be the first!
Your rating
What should we improve? (pick any)