Learn how to tell whether a website is genuinely offline or the problem is your own network, DNS, or browser — and what to do in each case.

You open a website, and nothing happens. The tab spins, then times out. Before you email the site owner, restart your router, or assume the whole service has collapsed, there is one question worth answering first: is the site actually down, or is the problem sitting somewhere between you and it?

The distinction matters because the two situations need completely different responses. If the site is genuinely offline, there is nothing you can do but wait. If the problem is on your end, you can usually fix it in under a minute. Most people skip this step and waste time on the wrong one.

Why a Site Can Be "Down" for You Alone

In my experience working on client sites, the most common cause is a DNS cache holding an old address after a hosting migration — particularly on Windows machines, where it survives a browser restart and confuses everyone for hours.

Your request to a website passes through more hops than most people realise. Your browser, your operating system's DNS cache, your router, your ISP's DNS resolver, your ISP's routing, and finally the destination server. A failure at any point produces the same symptom: a page that will not load.

The most common culprits, roughly in order of how often they turn out to be the cause:

• DNS caching. Your device stores the site's IP address for a period. If the site moved servers recently, you may be trying to reach an address that no longer serves it.
• Browser cache. A partially cached page or a stale service worker can produce a broken load even when the server is healthy.
• ISP-level blocking or routing problems. Some sites are unreachable from specific networks or countries while working fine everywhere else.
• Local firewall, antivirus, or VPN. Security software intercepts connections more often than people expect, particularly on corporate networks.
• An IP-level block. If the site's firewall or bot protection has flagged your address, you get blocked while everyone else gets through.

None of these are visible from inside your browser. That is why guessing is unproductive.

The Fastest Way to Get an Answer

The reliable method is to have a server somewhere else request the page and report what it gets back. That removes your network, your device, and your browser from the equation entirely.

Run the URL through a website status checker. You will get one of two useful outcomes:

• The check succeeds. The server responded from an external network, so the site is up. Your problem is local.
• The check fails. An independent network also cannot reach the server, which points to a genuine outage or a misconfiguration on the site's end.

This single test resolves the ambiguity in a few seconds and tells you which direction to investigate.

Reading the Status Code

A status checker does not just report up or down. It returns the HTTP status code the server sent back, and that number narrows the problem considerably.

• 200 — The page loaded normally. If you still cannot see it, the issue is definitively on your side.
• 301 or 302 — The URL redirects somewhere else. This is normal behaviour, but worth checking if you did not configure the redirect yourself.
• 403 — The server is running but refusing the request. Often bot protection, a firewall rule, or a permissions problem.
• 404 — The server is fine; that specific page does not exist. Check the URL for a typo before assuming anything worse.
• 500, 502, 503, 504 — A server-side failure. The site owner needs to investigate their application, database, or hosting. There is nothing you can do from outside.

The difference between a 404 and a 503 is the difference between "you typed the wrong address" and "their infrastructure is broken." Both look identical in a browser.

Each of these codes is explained in more detail in our full guide to HTTP status codes.

If the Site Is Up and You Still Cannot Reach It

Work through these in order. They are arranged so the quickest checks come first.

1. Try a different network

Switch from Wi-Fi to mobile data, or the reverse. If the site loads on one network and not the other, the problem is that network — its DNS, its routing, or a block somewhere along the path. This is the single most informative test you can run, and it takes ten seconds.

2. Open the site in a private window

A private or incognito window bypasses your cache, cookies, and most extensions. If the site loads there, clear your browser cache for that domain and the problem is solved.

3. Flush your DNS cache

On Windows, open Command Prompt and run ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache. Then restart your browser. This fixes the surprisingly common case where a site has moved, and your device is still holding the old address.

4. Disable your VPN or proxy

VPN exit nodes get blocked by websites regularly, particularly by sites using aggressive bot protection. Turn it off and try again. If that fixes it, the site is blocking your VPN provider's range rather than you specifically.

5. Check whether it is slow rather than down

A site that takes twelve seconds to respond will often time out in the browser and look completely offline. A ping test measures the round-trip latency to the server and distinguishes "unreachable" from "responding, but far too slowly." These need different fixes.

6. Check the certificate

An expired or misconfigured SSL certificate produces a full-page browser warning that many people read as an outage. An SSL checker tells you whether the certificate is valid, who issued it, and when it expires. This one is worth checking early if you saw a security warning rather than a blank page.

If the Site Is Genuinely Down

On a client migration last year, the site was up for me and down for the client for two days. It turned out to be their office firewall, not the server — which is why the different-network test comes first in this list.

When an external check also fails, the problem is on the site's end. What you do next depends on whether it is your site.

If it is someone else's site, there is nothing to fix. Check their status page or social accounts — most services post about outages there before anywhere else. Then wait. Repeatedly refreshing does not help and, during a partial outage, adds load to a server that is already struggling.

If it is your own site, the status code points you to the right area:

• 500 — An application error. Check your error logs first; they will usually name the file and line.
• 502 or 504 — A gateway or upstream timeout. Your web server cannot reach the application behind it, or the application is taking too long to respond.
• 503 — The service is unavailable, often deliberately during maintenance, or because the server has run out of resources.
• No response at all — DNS is not resolving, or the server is not reachable at the network level. Verify your DNS records and confirm the server is actually running.

One detail that catches people out: if you have recently changed hosting or DNS, the site may be up for some visitors and down for others while the change propagates. That process can take up to 48 hours, and there is no way to accelerate it.

Frequently Asked Questions

Why does a status checker say a site is up when I cannot open it?

The checker requests the page from a different network than yours. If it succeeds and you fail, the problem lies between you and the server — DNS, cache, VPN, firewall, or an ISP-level block. Try a different network to confirm.

Can a website be down in one country and working in another?

Yes, and it is more common than people expect. Sites block entire regions, CDN nodes fail in specific areas, and ISPs sometimes block sites at the network level. A check from a single external location cannot rule this out.

What does it mean if the site loads but shows an error page?

The server is running, so this is not an outage in the usual sense — it is an application-level failure. The status code tells you more than the error page does, since many sites show a friendly message while returning a 500 behind it.

How long do website outages usually last?

Most are brief. Configuration errors and application crashes are often resolved within minutes once someone notices. Longer outages typically involve hardware failure, expired certificates or domains, or a hosting provider incident affecting many customers at once.

Should I clear my cache every time a site fails to load?

No. Confirm the site is actually up first, then try a private window. Clearing your cache logs you out of everything and is rarely the fix — it is worth doing only once you have narrowed the problem to your browser.

The Short Version

Before troubleshooting, establish which side the problem is on. One external check answers that question, and everything you do afterwards depends on the answer. Skipping it means guessing, and guessing usually means fixing something that was never broken.

Written by Baleeghuddin Shaikh, SEO consultant with 8 years of experience in technical SEO and site diagnostics.