By Sarah Dia, HostDroplet Support
“Is my website down, or is it just me?” It’s the question that hits the moment your site won’t load — a blank page, an error, or an endless spinner — and your stomach drops. Your stomach drops and your first thought is usually “my host is down.” Maybe — but often not. Before you fire off a panicked support ticket, about 60 seconds of checking will tell you whether your website is really down for everyone, or whether it’s just you, or something you can fix in a minute yourself.
The trick is to narrow it down in the right order instead of guessing. Here’s how to tell exactly where the problem is.
First question: is it down for everyone, or just you?
This is the fastest and most useful check, because “just me” and “everyone” lead to completely different places.
- Run your site through our Website Status Checker — it tells you whether your site responds from outside your own connection.
- Try loading it on your phone using mobile data (not your Wi-Fi), and in a private/incognito window.
If it loads fine anywhere other than your usual setup, the site isn’t down — the problem is local to you. If it’s unreachable everywhere, it’s a genuine outage and you’ll want the second half of this guide.
If it’s just you: quick local fixes
A “just me” outage is almost always stale local data or your own network. Work through these:
- Restart your router and reload.
- Clear your browser cache or use incognito.
- Flush your computer’s DNS cache so it re-checks where your site lives.
- Disable a VPN, proxy, or ad-blocking extension temporarily.
If you’re seeing a specific connection error rather than a blank page, these guides pinpoint it: ERR_CONNECTION_REFUSED, ERR_CONNECTION_TIMED_OUT, and This Site Can’t Be Reached.
If it’s down for everyone: find which of three things broke
A real outage almost always traces to one of three culprits, and the error you see is the biggest clue. (The HTTP status code shown is worth noting.)
1. Your server or host
If the site simply won’t connect, times out, or the whole server is unreachable, the issue may be at the hosting level — an outage or a resource limit. If your site sits behind Cloudflare, a 521 or 522 error points here too. This is the one to bring to your host.
2. Your site itself
If you get a 500 Internal Server Error or a “critical error” message, the server is up but something in your site broke — very often a bad plugin, theme, or update. If the outage started right after you changed something, that’s almost certainly the cause.
3. Your domain or DNS
If you see a DNS error (like a domain that “can’t be found”), the server may be fine but your domain isn’t routing to it — an expired domain, a DNS misconfiguration, or changes still propagating. Check where your domain resolves with our DNS Lookup tool; Cloudflare’s DNS explainer is helpful background on why this happens.
The honest truth about uptime
Here’s something worth internalizing so you don’t panic at every blip: no website has 100% uptime. Brief, occasional interruptions — a few seconds during maintenance, a momentary hiccup — are normal and unavoidable. What matters is how rare and how short they are. Our guide on web hosting uptime explains what to expect, and what a 99.9% uptime guarantee really means puts the numbers in perspective. A real outage is one that lasts and affects everyone — not a two-second flicker.
Don’t be the last to know
The worst way to learn your site is down is a customer telling you. Set up website monitoring so you get an alert the moment your site stops responding — often before anyone else notices. And understanding the common causes of website downtime helps you prevent the avoidable ones in the first place.
Quick answers
How do I know if it’s my host’s fault?
If your site is unreachable for everyone, you’re not seeing a 500 or DNS error, and nothing changed on your end, it’s likely a server issue worth raising with your host. If you get a 500 error or it broke right after an update, it’s probably your site, not the host.
My site is down but my host says everything’s fine. Now what?
Check whether it’s actually a DNS or domain issue (the server can be perfectly healthy while your domain misroutes), and confirm it’s down for everyone and not just your network. Share the exact error you see with support so they can trace it.
How much downtime is normal?
Very little — a strong host targets well above 99.9% uptime, which works out to only minutes per month. Brief blips happen; sustained or frequent outages don’t, and are worth investigating.
How do I get alerted when my site goes down?
Use a website monitoring service, which checks your site continuously and messages you the moment it stops responding. It turns “a customer told me” into “I already knew and I’m on it.”
So before you assume the worst, run the one check that matters: is it down for everyone, or just you? From there, the error you see points straight at whether it’s your network, your site, your server, or your domain — and if it turns out to be something on our end, reach out with the details and we’ll get you back online fast.
