Why Is My Website Down? A Step-by-Step Diagnosis

Your website is usually down for one of a few reasons: an expired domain or hosting plan, a DNS fault, a crashed or overloaded server, an expired SSL certificate, or a broken update. Work through them in that order, quickest to rule out first. Most outages we see trace back to billing or a bad update, not a mysterious server fault.

Here is the quick map most outages fall into, and where to look first.

What you see	Most likely cause	First thing to check
Nothing loads, address fails	Expired domain or a DNS fault	Registrar renewal, then DNS records
A billing or suspension notice	Unpaid or lapsed hosting plan	Your host invoice
Page times out or a server error	Crashed, overloaded, or under-maintenance server	The host's status page
A full-page security warning	Expired SSL certificate	Certificate renewal
Errors or content you did not add	Broken update or a hacked site	Recent changes, then backups

Source: our own triage order for Malaysian SME sites (illustrative checklist, not a vendor table).

Is the site down for everyone, or just you?

Check whether the site is truly down before you panic, because half the time it is only down for you. Your own device, network, or browser cache can block a site that everyone else still reaches.

Try loading it on mobile data with Wi-Fi off, and on a different device. Open it in a private window to skip your cache. A free "is it down" checker tests the site from outside your network and settles the question in seconds.

If it loads elsewhere, the fault is local, and clearing your cache or switching networks fixes it. If it is down everywhere, move to the causes below.

Has your domain or hosting expired?

An expired domain or an unpaid hosting invoice is the single most common reason a whole site vanishes at once. Both run on renewal dates that are easy to miss, especially when the reminder emails go to an address nobody checks.

An expired domain stops resolving, so the address simply fails to load. An unpaid or lapsed hosting plan gets suspended, often showing a billing notice instead of your site. Neither is a technical fault, and both come back the moment you pay.

We have dealt with more than one lapsed-domain scramble. The fix is always dull: log in to the registrar or host, settle the invoice, and wait for the service to restore.

Set auto-renew, and point the renewal reminders at an inbox you actually read.

Is it a DNS or connection problem?

A DNS fault breaks the link between your domain name and the server it lives on, so the browser cannot find where to go. This often shows as a "site can't be reached" or "server not found" error rather than a blank page.

DNS is the phonebook of the internet that translates your domain into the server's IP address (Cloudflare, accessed 2026). If someone changed a DNS record, moved hosts, or a change is still spreading, the site can drop for some visitors and not others. A DNS change can take up to about 48 hours to propagate fully.

Check that your domain still points at the right server, and that any recent record change was correct. If you just switched hosts, give propagation time before assuming something broke.

Did the server crash, overload, or go into maintenance?

A crashed, overloaded, or under-maintenance server takes the site down at the host's end, not yours. This is the classic outage: the domain resolves, but the page times out or throws a server error.

Shared hosting is the usual suspect for a small site. When one site on the server spikes or the box runs out of memory, everything on it slows or stops. A sudden traffic surge does the same. Planned work is different again, and our guide to a host down for maintenance separates a normal maintenance window from a red flag.

Check your host's status page and your email for outage or maintenance notices. If the server keeps buckling under normal traffic, the plan is undersized, and the answer is a better plan, not a bigger promise. A genuine 99.9% uptime still allows a few hours of downtime a year, so a rare short outage is not proof of a bad host.

Did a recent change or a hack break the site?

A broken update or a hacked site is the likely cause when everything worked an hour ago and now shows errors or content you did not put there. The two look different, and the fix depends on which one you are facing.

A failed plugin, theme, or code update can throw a blank white screen or a fatal error. In our experience most site emergencies come from outdated or clashing plugins, not clever attacks. Rolling back the change, or restoring a recent backup, usually brings it straight back, which is exactly why a backup earns its keep.

A defaced homepage, spam pages, or a browser security warning point to a compromise instead. That needs a clean-up, not a rollback, and our guides to why sites get hacked and a malware blacklist cover the recovery path.

Frequently asked questions

How do I check if my website is really down or just down for me?

Load the site on a second device and on mobile data with Wi-Fi off, then open it in a private browser window to bypass your cache. If it works anywhere, the outage is local to your device or network, and clearing the cache or switching networks fixes it. A free third-party "is it down" checker confirms it from outside, independent of your own connection.

My domain works but the page won't load. What does that mean?

That usually points to the server or the site itself, not the domain. If the address resolves but the page times out or shows a server error, the host may be down, overloaded, or doing maintenance. If it loads but shows errors or a security warning, a recent update or a hack is the likelier cause. Check the host's status page first, then any recent change you made.

How long does it take for a website to come back after I fix it?

It depends on the cause. Paying an overdue hosting invoice or renewing a domain often restores the site within minutes to a few hours. A DNS change can take up to about 48 hours to spread fully. Restoring a backup or rolling back a bad update is usually quick once you have access. A hacked site takes longest, because it needs a full clean-up.

Can an expired SSL certificate take my site down?

Not exactly, but it can look that way. An expired SSL certificate does not stop the server, yet browsers show a full-page security warning that scares visitors off, so the site is effectively unreachable for most people. Renewing or reissuing the certificate clears the warning. Many hosts renew it automatically, so check that setting if it lapsed.

Why does my site keep going down again and again?

Repeated outages usually mean an undersized hosting plan, a recurring plugin conflict, or an unresolved security problem, not bad luck. A shared server that buckles under normal traffic needs a bigger plan. A site that breaks after every update has a conflict worth fixing at the root. Track when the outages happen, because the pattern points at the cause faster than any single incident.

Get the pattern diagnosed, not just the symptom

Storming Solutions builds and maintains websites for Malaysian businesses from Kuala Lumpur. A site that keeps blinking out is one of the first things we are asked to trace.

Our honest view: most outages are billing or a bad update, so we look there before blaming the server.

Is your site down right now, or dropping too often to ignore? Send us the URL on WhatsApp and we will help you find the cause. Then talk to us about web development and hosting you can actually rely on.