A page will not load, and the first question decides everything you do next: is the website down for everyone, or is the problem somewhere between you and it — your browser, your Wi-Fi, your provider? Guessing wrong wastes an hour either waiting for a fix that is yours to make, or fiddling with settings while a global outage fixes itself.
The checks below take about five minutes in total and are ordered from the outside in: first establish whether the site is up for the rest of the world, then work through the local causes one by one until the page loads or the culprit is obvious.
Step 1: Check whether the site is down for everyone
- Open an outage tracker such as Downdetector (downdetector.com) and search for the service. A sharp spike in user reports in the last hour means a real, widespread problem — your job is done; wait it out.
- For large services, check the company's own status page (search the service name + "status"). Big platforms publish live incident information there, including which features are affected.
- A "down for everyone or just me" checker site gives a second opinion by loading the page from its own servers: if it can load the site and you cannot, the problem is on your side of the fence.
Note the limit of these tools: they track big services well, but a small website may have no listing at all — absence of reports proves nothing for a small site. Continue to step 2 either way.
Step 2: Try a different device and a different network
This is the single most informative test. Load the site on your phone with Wi-Fi switched off, so it uses mobile data. Three outcomes:
- Loads on mobile data, not on Wi-Fi: the problem is your home network or your internet provider's route to the site. Restart the router; if it persists, it is likely the DNS issue in step 4.
- Fails on both, but trackers show no outage: suspect the site itself (small sites fail silently) or a regional/provider issue. Try again in a while, and check the site's social media accounts for announcements.
- Loads on another device on the same Wi-Fi: the problem is the first device — go to step 3.
Step 3: Rule out your browser (cache, cookies, extensions)
Browsers keep copies of sites, and a corrupted copy can break one site while everything else works:
- Hard refresh: press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to reload the page ignoring the cache.
- Private window: open the site in an incognito/private window. This disables most extensions and uses no stored cookies — if the site works there, an extension or a stored cookie is the culprit.
- Clear the site's data: in your browser settings, clear cached files and cookies (you can usually limit this to the one site via the padlock icon in the address bar > site settings). You will be signed out of sites, so expect to log in again.
- Try another browser if you have one. A site that loads in Firefox but not Chrome has told you exactly where the fault lives.
Step 4: Check DNS — the internet's phone book
DNS translates a site's name into its address. If your provider's DNS is broken or stale, names stop resolving while the sites themselves are fine — the classic symptom is "some sites load, one specific site never does, and it works on mobile data".
- Test the theory: on your computer, try loading the site after switching your connection's DNS to a public resolver — 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) — in your network settings. On a phone, toggling to mobile data (step 2) already tests a different DNS.
- On Windows, also flush the local DNS cache: open Command Prompt and run
ipconfig /flushdns. It clears out stale name records your PC has memorised. - If the site loads with the new DNS, you can leave the setting in place — public resolvers are a legitimate long-term choice — or switch back in a day or two when your provider has fixed theirs.
Step 5: The remaining usual suspects
- Your security software or firewall may be blocking the site — check its blocked/allowed list, especially after an update.
- The site's address changed: an old bookmark may point to a retired subdomain. Search for the site by name and follow the current link.
- Regional blocking or provider filtering: if the site loads for friends on other providers but never for anyone on yours, your provider may be filtering it (sometimes by court order, sometimes by mistake). The provider's support line is the place to ask.
- Certificate and clock errors: if the error mentions certificates or secure connections and affects many sites, check your device's date and time — a wrong clock makes valid certificates look expired.
If the site is a small one and every check says it is genuinely down, there is nothing to fix at your end: note the time, try again later, and if you have a relationship with the site (a shop you ordered from, your club's page), contact them through another channel — small site owners often learn about outages from their visitors first.
Key takeaways
- Start outside-in: outage trackers and the service's own status page tell you if it is down for everyone.
- The mobile-data test splits the problem in half: loads there but not on Wi-Fi = your network or provider's DNS.
- A private window and a hard refresh rule out cache, cookies and extensions in under a minute.
- If one site fails only on your connection, try a public DNS (1.1.1.1 or 8.8.8.8) and ipconfig /flushdns on Windows.
Quick questions
The site loads for my friend but not for me. Why?
You are on different paths to it: different provider, different DNS, possibly different cached copies. Work through steps 2–4 — in practice it is usually your provider's DNS or your browser's stored data for that site.
What does the error code tell me?
A 404 means the site is up but that page is gone. 500/502/503 errors are the site's own server failing — genuinely their problem. “Server not found” or DNS errors point to name resolution (step 4). A timeout with no code at all suggests a connection or filtering problem between you and the site.
Is it safe to use public DNS like 1.1.1.1?
Yes — Cloudflare's 1.1.1.1 and Google's 8.8.8.8 are long-running public services used by millions. Changing DNS only changes which directory your device consults for addresses; it does not reroute or expose your traffic, though the resolver does see which site names you look up.
How long should I wait before trying again?
For a confirmed big-service outage, check the status page every so often rather than refreshing constantly — major incidents are usually updated there as they are fixed. For a small site with no status page, an hour or two is a reasonable interval.
Further reading: Downdetector — check real-time service problems and outages — Downdetector (Ookla).