Website Down? How to Diagnose the Cause in 5 Minutes (Host vs Domain vs Site)

Last updated: August 2026

Minute 1: Is it down for everyone, or just you?

Check the site through a "down for everyone or just me" checker or your phone on cellular data (Wi-Fi off). If it loads for the rest of the world, the problem is local, your network, your DNS cache, or your office firewall. Restart your router, try another network, and stop here.

Minute 2: What exactly do you see?

The error message is the diagnosis:

Minute 3: Check the domain

Look up your domain in a WHOIS checker. Two things: is the expiry date in the past, and are the nameservers what they should be? An expired domain is the worst version of "down", after expiry there's a grace period to renew at normal price, then a redemption period where fees jump to $80-200, and eventually the domain can be auctioned. If it's expired, renew now, before finishing this article.

Minute 4: Check the host

Open your hosting provider's status page (search "[host name] status"). A platform-wide incident means the fix is theirs and your job is just to wait, annoying but safe. No incident? Log into your hosting panel: look for suspension notices, disk-space-full warnings (a full disk takes sites down and blocks email), or resource-limit alerts.

Minute 5: Check the website layer

If DNS resolves and the server responds but you get 500-class errors, the site's own software is failing, typically a plugin update gone wrong, a PHP version change, or a corrupted .htaccess file. The fastest recovery is restoring last night's backup; the proper fix is reading the server error log to see the actual failing component. For WordPress-specific paths, see our white screen guide.

What downtime actually costs (and the case for monitoring)

The expensive part of downtime isn't the outage, it's the discovery gap. Sites without monitoring are typically down for hours before an owner notices, usually because a customer mentions it. Uptime monitoring closes that gap to about a minute. Every plan we run includes 24×7 uptime monitoring with alerts to us, not just to you, which is why our average first response is 12 minutes, including the responses at 3 a.m.

FAQ

My host says everything is fine, but the site is still down. Who's right? The status page covers platform-wide issues, not your account. Open a ticket with the exact error text and the results of your WHOIS check, with those two facts, support can't ping-pong you.

How much uptime should I expect? 99.9% uptime still allows ~43 minutes of downtime per month. Decent hosts beat that; if you're seeing multiple outages monthly, the outages aren't bad luck, they're a reason to migrate.

Can too much traffic take my site down? On shared hosting, yes, a marketing win or a bot swarm can hit resource limits and trigger 503s. If you're planning a launch or a big campaign, prepare the hosting first.

The site is back, do I still need to do anything? Find the cause. Downtime with no identified cause repeats. Check error logs, confirm backups ran through the incident, and note the timeline while it's fresh.