Learn how to check if a site is really down or the problem's on your end. Simple tools, real fixes, no jargon — from someone who's been there.

How to Check If a Website Is Down or Not Working (A Real Troubleshooting Guide)

I still remember the exact moment my stomach dropped. I was three days into launching a small online store for a friend, checkout page freshly wired up, and I opened the site on my phone during lunch to show a coworker. Nothing loaded. Just a spinning wheel and then a blank white screen.

My first thought wasn't "let me troubleshoot calmly." It was pure panic. Did the server crash? Did I break something in the last update? Is the domain about to expire and I forgot to renew it?

Turns out, none of that was true. My own Wi-Fi router had decided to have a mid-afternoon crisis and was dropping DNS requests. The site was fine. My internet was not.

That fifteen minutes of unnecessary panic taught me something I now tell literally everyone who messages me saying "hey, is this website down for you too?" — there's a right order to check things, and almost nobody does it in that order. They usually jump straight to refreshing the page forty times, which, spoiler, does not help.

So here's everything I've picked up from years of dealing with "is it down or is it just me" moments, both as someone who runs websites and as someone who just uses the internet like everybody else.

Why This Actually Matters More Than People Think

If you run a website, even a small blog or a local business page, downtime costs you. Not just money in obvious cases like an online store, but trust. Someone tries to visit your site, it doesn't load, and a good chunk of them just leave and don't come back to try again later. They assume you're unreliable.

If you're just a regular visitor trying to check your bank balance or finish an order on some shopping site, not knowing whether it's your connection or their server wastes your time and your patience.

Either way, being able to quickly figure out "is this actually down, or is something on my end broken" saves you a lot of unnecessary stress.

The First Thing I Always Do (And You Probably Skip This)

Before touching any tool or website checker, I open the site in an incognito or private browsing window.

I cannot tell you how many times a site "wasn't working" for me and it turned out to be a cached version of the page, an old cookie messing with a login session, or a browser extension (ad blockers are sneaky culprits here) quietly blocking something important.

Here's the quick version:

• Chrome: Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac)
• Firefox: Ctrl+Shift+P
• Safari: Cmd+Shift+N
• Edge: Ctrl+Shift+N

If the site loads fine in incognito mode, the problem was never the website. It was something local to your regular browser session — cache, cookies, or an extension.

I once spent almost twenty minutes convinced a client's WordPress site had been hacked because the homepage looked completely broken, styles missing, layout collapsed. Opened it in incognito. Loaded perfectly. Turned out an old cached CSS file in my regular browser was the actual issue. Nothing was wrong with the site at all.

Step 2: Check If It's Down for Everyone, Not Just You

This is where most people's troubleshooting begins and ends, and honestly it's a reasonable second step. There are a few tools I actually use regularly:

Downdetector

Downdetector is genuinely useful because it's not just pinging a server — it's aggregating real user reports. If a huge site like Instagram or your bank's app is having issues, you'll usually see a spike on Downdetector within minutes, sometimes before the company even acknowledges it publicly.

The catch: Downdetector works best for big, popular platforms. If you're checking your cousin's small business website, you're not going to find it listed there because not enough people are reporting on it.

IsItDownRightNow.com and DownForEveryoneOrJustMe.com

These two do something simpler and more universal — they send a request to the website from their own servers and tell you if it responded. This works for basically any website, big or small.

I use DownForEveryoneOrJustMe more often just because the name makes me laugh every time, but functionally they do the same job. Type in the URL, hit check, and it tells you if the site responded from its location or not.

The important nuance here: these tools check from one server location. If a website is geo-blocked in certain regions, or if there's a routing issue specific to your ISP or country, these tools might say "it's up!" while it's still genuinely broken for you.

Step 3: Try a Different Network

This one sounds obvious once you hear it, but almost nobody does it in the moment of frustration.

Switch from Wi-Fi to your phone's mobile data (or vice versa) and try loading the site again.

I make this mistake myself more than I'd like to admit. A site "wouldn't load" for me one evening, and I assumed the site's servers were struggling. Switched off Wi-Fi, tried on 4G, loaded instantly. My home router had a DNS hiccup that was somehow only affecting that one domain.

If a site loads on mobile data but not on your home Wi-Fi, the problem is almost certainly on your end — your router, your ISP's DNS servers, or occasionally your ISP blocking or throttling something.

Step 4: Ping the Website (Yes, This Old-School Trick Still Works)

This sounds technical but it's genuinely simple, and I still use it constantly.

On Windows:

1. Press the Windows key, type cmd, hit Enter to open Command Prompt.
2. Type ping example.com (replace with the actual site) and press Enter.

On Mac:

1. Open Spotlight (Cmd+Space), type Terminal, hit Enter.
2. Type ping example.com and press Enter. Press Ctrl+C to stop it.

What you're looking for: if you get replies back with response times (usually in milliseconds), the server is reachable and responding. If you get "Request timed out" or "could not find host," that's a strong sign there's a connectivity or DNS problem, either with the site or with your own network.

A word of caution though — some websites deliberately block ping requests as a security measure, so a failed ping doesn't automatically mean the site is down. It just means that specific test didn't give you useful info. I've been fooled by this before with a client's site that was very much online but had ping requests disabled at the firewall level.

Step 5: Flush Your DNS Cache

This fixed more "broken websites" for me than almost anything else on this list, and it's criminally underused.

Your computer stores a local memory of website addresses (DNS cache) so it doesn't have to look them up every single time. Sometimes this cache gets stale or corrupted, and your computer keeps trying to reach an old or wrong server address for a site that has since moved or changed.

On Windows: Open Command Prompt and type:

ipconfig /flushdns

On Mac (recent versions): Open Terminal and type:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

After flushing, try the website again. I've had sites that were "completely broken" for two days suddenly load perfectly after this one command. It's especially common right after a website changes hosting providers or updates its server configuration.

Step 6: Check DNS Propagation (For Site Owners Especially)

If you're the one managing the website and you just made DNS changes — new hosting, new domain, added a subdomain — this step is for you specifically.

DNS changes don't happen instantly everywhere in the world. They spread out gradually, sometimes taking anywhere from a few minutes to 48 hours depending on your DNS provider and the TTL (time to live) settings.

I use whatsmydns.net for this. You type in your domain, and it checks DNS resolution from dozens of locations around the world simultaneously. You'll often see a map where some locations show the new IP address and others still show the old one — that's completely normal during propagation.

The mistake I made the first time I moved a site to new hosting: I panicked because the site "wasn't working" for me, when really it was working fine for most of the world already, my own ISP's DNS servers just hadn't picked up the change yet. I could've saved myself an anxious hour by checking whatsmydns.net first.

Step 7: Look at the Actual Error Message

People skim right past error messages, but they're genuinely telling you something specific.

• "This site can't be reached" / DNS_PROBE_FINISHED_NXDOMAIN — Usually means the domain doesn't resolve. Could be an expired domain, a DNS misconfiguration, or the site genuinely doesn't exist anymore.
• "Connection timed out" — The server isn't responding at all. Could be down, or a firewall is blocking the request.
• 502 Bad Gateway / 503 Service Unavailable — The server is up, but something behind it (like a database, or the app itself) is struggling or overloaded.
• "Your connection is not private" (SSL error) — The site is technically reachable, but there's a problem with its security certificate, often because it expired.
• 404 Not Found — The server is fine, that specific page just doesn't exist (maybe it moved or was deleted).

I once got a very concerned message from a friend saying my site was "completely down." Turned out it was an SSL certificate that had quietly expired the night before because an auto-renewal setting on the hosting panel had silently failed. The server itself was running the whole time. Knowing the difference between "the whole site is down" and "there's a certificate issue" saved me from unnecessarily restarting servers and panicking over nothing.

Step 8: Check Your Firewall, VPN, or Antivirus

If you're on a work laptop or a computer with strict security software, sometimes the software itself is quietly blocking a site without telling you clearly why.

I've had corporate VPNs block entire categories of sites (sometimes accidentally lumping in perfectly legitimate business tools with actual malicious sites). If you're on a VPN, try disconnecting it temporarily and reloading the page. If it suddenly works, that's your answer.

Also worth checking: browser extensions, especially ad blockers and privacy tools like uBlock Origin or Privacy Badger. Sometimes they block scripts a website needs to actually render properly, and instead of a clean error, you just get a broken or blank-looking page.

Real Example: A Weird One I Didn't Expect

A few months back, a WordPress site I manage started throwing a white screen for visitors in one specific country, while working fine everywhere else, including for me.

Downdetector showed nothing (too small a site to register there). IsItDownRightNow said it was up. Ping worked. DNS was resolving correctly everywhere on whatsmydns.net.

Turned out the hosting provider's CDN (Content Delivery Network — in this case Cloudflare) had a routing hiccup at one of its regional edge servers, and visitors being routed through that specific edge node were hitting errors while everyone else sailed through fine.

The fix was on Cloudflare's end, and honestly there wasn't much I could do except wait it out and keep an eye on Cloudflare's own status page at cloudflarestatus.com. That's a good habit if your site uses Cloudflare, AWS, or any major infrastructure provider — check their status pages directly, because sometimes the problem isn't your hosting account at all, it's the underlying infrastructure everyone shares.

Other useful status pages worth bookmarking if you rely on specific services:

• AWS Health Dashboard
• Google Cloud Status
• GitHub Status (if your site deploys from GitHub)

For Website Owners: Setting Up Monitoring So You're Not Always Guessing

If you own a website, the smartest thing you can do is stop manually checking whether it's up and instead get notified automatically the second it goes down.

I use UptimeRobot for most of my smaller projects because the free plan checks your site every five minutes and emails or texts you if it goes down. For anything more business-critical, Pingdom or StatusCake offer more detailed monitoring, including checking specific pages, not just the homepage.

Setting this up takes about ten minutes and has saved me from finding out about downtime through an angry customer email instead of finding out immediately and fixing it before most people even noticed.

Common Mistakes People Make (I've Made Most of These Myself)

Refreshing the page over and over. This does nothing except waste your time and occasionally make things worse by hammering an already struggling server with more requests.

Assuming it's always the website's fault. In my experience, more often than people expect, the actual problem is local — your Wi-Fi, your DNS, a VPN, or a browser extension.

Ignoring the exact error message. The difference between a DNS error and a 503 error tells you completely different things about where the problem actually is.

Not checking on a different device or network. This is the fastest way to isolate whether the issue is you or them, and it takes thirty seconds.

Panicking before checking basics. I get it, downtime feels urgent, especially if it's your own site and it's costing you sales or reputation. But five minutes of proper troubleshooting beats an hour of frantic, directionless clicking.

Forgetting about caching. Both your browser's cache and, if you run a website, any caching plugin or CDN cache can serve an old, broken version of a page long after the actual issue is fixed. Sometimes a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) or clearing the CDN cache is the actual missing step.

A Quick Checklist You Can Actually Use

Next time a site won't load, run through this in order — it usually takes less than five minutes total:

1. Open it in an incognito/private window.
2. Check Downdetector or IsItDownRightNow.com.
3. Switch networks (Wi-Fi to mobile data or vice versa).
4. Ping the domain from Command Prompt or Terminal.
5. Flush your DNS cache.
6. Read the actual error message carefully.
7. Temporarily disable VPN or ad blockers.
8. If you're the site owner, check DNS propagation and your hosting/CDN status page.

Nine times out of ten, one of these steps gives you a clear answer, and half the time the fix is embarrassingly simple, like my router meltdown from the beginning of this whole thing.

Final Thoughts

The honest truth is that "is it down or is it just me" isn't really a mystery once you know where to look. Most people just don't know the order to check things in, so they either panic unnecessarily or blame the wrong thing entirely.

I've been on both sides of this — the frustrated visitor convinced a site betrayed me, and the site owner convinced their server had exploded, when really it was something small and fixable the whole time. Give yourself the five minutes to actually check properly before you assume the worst. Your future self, and probably your blood pressure, will thank you.