A website won't load, and you assume it's down. But then a friend says it works fine for them — so what's going on? There's a possibility people often overlook: the site might be perfectly up and running, and simply blocking you specifically. Being genuinely down and being deliberately blocked look almost identical from your screen, yet they call for completely different responses. Here's how to tell whether a website is actually down or just refusing you — and what to do about it.

It's not two possibilities — it's three

When a site won't load, there are actually three explanations:

  1. It's down for everyone — a real server outage.
  2. There's a problem on your end — a local issue like DNS or your network (our guide on whether a site is down for everyone or just you covers this).
  3. The site is up but blocking you specifically — it works for others, but something makes it refuse your connection.

Most troubleshooting advice covers the first two. This article is about spotting the third — because the fix is entirely different.

First: is the site actually down?

Start by removing yourself from the equation. Run the site through our live website down checker, which connects from our servers on a separate network:

  • If our server can't reach it either, the site is genuinely down for everyone — wait it out.
  • If our server loads it fine but you can't, the site is up — so your problem is either a local issue or a deliberate block. The signs below tell you which.

Signs a site is blocking you (rather than being down)

If the checker says the site is up but you still can't get in, these clues point to a block aimed at you:

  • It loads for others but not you. The clearest sign — the site works from the checker, other networks, or friends, just not your connection.
  • You get a 403 Forbidden or "Access Denied." A deliberate block usually returns a 403, not a timeout or a 5xx error. Our guide on fixing a 403 Forbidden error covers this code.
  • A geo-restriction message. "This content isn't available in your region/country" means you're blocked by location, not that the site is down.
  • A rate-limit or 429 message. "Too many requests" means you've been temporarily throttled — see our guide on Cloudflare checks and 403/429 errors.
  • A security "you have been blocked" page or a challenge you can't pass, often from a firewall or bot-protection layer.
  • It works over a VPN or different network but not your normal one — a strong sign your specific IP is being blocked.

How to tell "down" from "blocked" quickly

Three quick tests settle it:

  1. Check from a neutral server. Our checker reaching the site = it's up, so you're either blocked or having a local issue. Our checker failing = it's genuinely down.
  2. Read the error code. Timeouts and 5xx (500, 502, 503) errors usually mean the site is down or struggling. A 403, 429, or a geo/security message usually means you're blocked. Our guide on what HTTP status codes mean helps you interpret them.
  3. Switch networks. Try mobile data instead of Wi-Fi, or a VPN. If the site suddenly works, your original IP or network is being blocked — the site itself is fine.

Why sites block specific visitors

Blocks are usually deliberate, and for reasons that have nothing to do with you personally:

  • IP reputation. Your IP (or a shared/VPN IP) was flagged for suspicious activity — sometimes from a previous user of that address.
  • Geo-restrictions. Licensing or legal rules limit content to certain countries.
  • Firewall or WAF rules. The site's security is blocking a range, a country, or a request pattern your connection matched.
  • Rate limiting. You (or your network) made too many requests too quickly.
  • VPN or proxy detection. Some sites block known VPN IP ranges outright.

What to do if you're being blocked

Your options depend on the type of block:

  • If it's your IP: try turning your VPN off (or on), restart your router to get a fresh IP from your ISP, or wait — temporary blocks often lift on their own.
  • If it's geo-restriction: the block is intentional by region, so options are limited; it's the site's deliberate choice.
  • If it's rate limiting (429): simply slow down and wait a few minutes before trying again.
  • If it's a firewall/security block and you're a legitimate visitor: you may have been flagged by mistake — contact the site owner and explain, as they can allow-list you.

What to do if it's actually down

If the checker confirms the site is down for everyone, there's nothing to fix on your end — wait for the site's team to restore it, and check back periodically.

The bottom line

When a site won't load, don't assume it's down — it might be up and blocking you specifically. Check it from a neutral server first: if the site is reachable for everyone but you, read the signs. A 403, 429, geo-message, or "you've been blocked" page — especially when it works over a different network or VPN — means you're being blocked, not that the site is down. Once you know which it is, the right move is obvious: wait out a real outage, or address the block that's keeping you out.