The page will not load. Is the website broken, is your internet broken, or is something in between quietly failing? Knowing how to check if a website is down for everyone or just you takes about ninety seconds and saves a remarkable amount of frustration — no more rebooting routers for a problem in another continent, no more waiting for a fix that is actually yours to make. This tutorial runs the checks in order, from fastest to most thorough.

Step One: Ask the Internet (30 Seconds)
Status-check services exist for exactly this question — sites such as downforeveryoneorjustme.com and downdetector — which attempt to load the page from their own servers and report whether the failure is yours alone or shared by the world. If the service says “down for everyone”, your work is done: the fault is the website’s, the fix is theirs, and the only remaining task is patience (plus, for services you depend on, checking their official status page or social feeds for incident reports). If it says “just you”, the problem lives somewhere between your device and the site — proceed down the ladder. One caution for brand-new failures: these services aggregate reports, so a major outage’s first minutes may show ambiguous results; combining this check with the next one resolves the ambiguity in under a minute.
Step Two: the Isolation Tests (Is It the Device, the Network, or the Site?)
Three quick swaps localise the fault. Try another site you use rarely: if NOTHING loads, the problem is your connection — check the router’s lights, restart it (a full power-cycle, thirty seconds unplugged), and consult your provider’s outage map. Try the failing site on a second device on the same network, then on your phone with Wi-Fi off (mobile data): if mobile data works while home Wi-Fi fails, your network or provider is implicated; if both fail while other sites load, suspicion moves to the site’s relationship with your provider or location. Finally, try a different browser or a private/incognito window: if the site loads there, the culprit is your main browser — a corrupted cache, a misbehaving extension, or cookies the site has taken against. These swaps are the network version of a doctor checking which limb hurts, and they pair with this site’s home Wi-Fi setup tips whenever the answer turns out to be your own network after all.
A quick variation worth memorising: if the site fails on every device and network you try but the checkers insist it is up, suspect your region or the site’s own geo-blocking — content licences and sanctions make some sites deliberately unreachable from some countries, which is a policy wearing the costume of a fault. A reputable VPN endpoint in another country settles that question in one test, though it is a diagnostic, not an entitlement to bypass rules that apply to you.
Step Three: Read the Error — It Is Telling You Something
Browsers and servers announce the fault’s nature if you read past “it doesn’t work”. A 404 means the server is alive and the page is gone — the site is up; the link is dead. A 500 or 503 means the server itself is failing or overloaded — genuinely their problem. “DNS_PROBE_FINISHED” or “server not found” means your device could not translate the site’s name into an address — a DNS problem, fixable by switching your DNS resolver to a public one (1.1.1.1 or 8.8.8.8) or by waiting out your provider’s stale records. A certificate warning (“your connection is not private”) means the site’s security certificate is broken, expired or mismatched — the site is reachable but its identity papers are not in order; do NOT bypass the warning to log into anything important. A timeout with other sites working fine suggests routing or blocking between you and them — occasionally regional, occasionally the site blocking your provider’s traffic outright. Each error converts a mystery into a category, and the category tells you whose desk the fix sits on.
Step Four: the Fixes That Are Yours to Make
When the fault is local, the cure list is short and usually decisive. Clear the cache and cookies for the single site (not your whole browser history — surgical beats scorched-earth). Disable browser extensions temporarily — ad blockers and privacy tools break legitimate sites regularly, and one reload with them off gives a verdict. Restart the browser itself, flush the DNS cache (one terminal command on any system), and power-cycle the router if several devices share the symptom. Check your device’s clock: an incorrect system date makes every security certificate look expired and every secure site “broken” — a two-minute fix for a maddening failure. If nothing resolves it and the isolation tests point inward, your provider’s support is next — arrive with your findings (“loads on mobile data, fails on your network, DNS resolves on 1.1.1.1 but not yours”) and you will skip twenty minutes of scripted questions.
The Reporting Habit That Helps Everyone
One last step closes the loop: if the site really is down, say so where it helps. Outage-reporting sites become accurate only because users report — the ninety seconds you spent checking is most valuable in its first minutes, when others are still rebooting their routers. And note what you found in whatever log your future self will thank you for, because repeat patterns (this provider, this site, every evening) are data, not déjà vu. The world’s systems report their own health in their own ways — even the listening devices our companion explainer describes, in how voice assistants understand you, fail in diagnosable layers rather than all at once. Knowing how to check if a website is down is the small, general skill underneath all of it: isolate, read the error, fix what’s yours, and wait calmly for what is not.
