Upkept

Why Is My Website Down? A Plain-English Troubleshooting Guide

Your site won’t load. Here’s how to check whether it’s really down, the eight most likely causes, and exactly what to do and who to call for each one.

10 min read

If your website won’t load, start here: almost every outage comes down to one of a handful of boring problems — an unpaid bill, an expired domain name, a lapsed security certificate, an update that broke something, or your host having a bad day. None of them require you to understand how websites work. They require you to know who to call and what to say.

Before you ring anyone, though, spend sixty seconds confirming the site is actually down for everyone and not just for you. That one step saves a lot of panicked phone calls.

First: is it really down, or is it just you?

Browsers and phones hold on to old copies of pages, home internet has bad days, and one misbehaving browser extension can make a perfectly healthy site look dead. Work through this in order — it takes about a minute.

  1. Open your site on your phone with Wi-Fi turned off, so it’s using mobile data. Different network, different route to your site.
  2. Try a different browser, or a private window. That rules out a saved copy of an old page and anything you’ve installed in your usual browser.
  3. Type the address in by hand instead of clicking a bookmark or an old link. Bookmarks quietly rot.
  4. Ask someone across town to load it, or search for “is it down right now” and put your address into one of the free checkers.
  5. Write down the exact error message, word for word, and screenshot it. This is the most useful thing you can hand to whoever helps you.

If it loads on mobile data but not on your office Wi-Fi, your site is fine and your internet is the problem — restart the router before anything else. If it’s down everywhere, keep reading.

What the error message is telling you

You don’t need to know what the words mean. You only need to match them to a rough area of blame, so you ring the right company first.

What you seeWhat it usually means
“This site can’t be reached”, or a page offering to sell you your own domainThe domain name has expired, or the settings pointing it at your site have changed.
“Your connection is not private”, or a full-page red warningThe security certificate expired. The site is still there — browsers are blocking the door.
“Account suspended”A bill hasn’t gone through, or the host has switched the site off for another reason.
A blank white page, or “500 Internal Server Error”Something inside the site broke — usually right after an update or an edit.
“503 Service Unavailable” or “Error establishing a database connection”The server is overloaded or unwell. Often the host’s problem, not yours.
The site loads but sends visitors somewhere strangeThe site has been hacked.
One page shows “404 not found”, the rest of the site is fineNot an outage. A page was renamed or deleted and something still links to the old address.

The eight usual suspects, roughly in order

1. The domain name expired

The most common cause and the most avoidable. A domain name is rented, not owned — usually a year at a time — so an expired card, or a reminder sent to an inbox you stopped checking, takes the whole site down at once. Your email often stops at the same moment, which is the giveaway. Log in to the company you bought the name from, renew it, and switch auto-renew on. It normally comes back within a few hours. Leave it for weeks and there’s a recovery fee on top — and eventually somebody else can buy your name.

2. The hosting bill didn’t go through

Hosting is the rent on the space your site sits in — a separate bill from the domain name, sometimes from a different company entirely. When a card expires, most hosts suspend the account rather than delete anything, so you get a suspension page where your homepage used to be. Pay the invoice and it’s usually back within the hour with nothing lost. If you can’t remember who you host with, look for a small recurring charge on your bank statement.

3. Somebody changed a setting

The settings that point your domain name at your actual website are delicate, and they’re nearly always changed with good intentions — someone setting up a new email system, or starting to move the site to a new host. When they change, the site can be up for some people and down for others for a day or two while the change spreads around the internet. That split is the classic symptom. Think about the last two days and who touched what; the fastest fix is almost always to put it back exactly as it was.

4. The security certificate expired

That’s the padlock in the address bar. Certificates renew themselves these days, but renewals do fail quietly, and then one morning every visitor meets a full-page warning telling them your site isn’t safe. Technically you’re up. Practically it’s worse than down, because a security warning frightens people in a way a blank page doesn’t. This one belongs to your host — ring them and ask them to reissue it. Usually a five-minute job at their end.

5. Your host is having an outage

Sometimes it genuinely isn’t you. Data centres lose power and networks fall over, and a few thousand small business sites go dark together. To check, search for your host’s name plus the word “status” — most of them publish a page showing current problems — or see whether other sites you know on the same host are down too. There’s nothing for you to fix. Watch the status page, and spend the time telling customers where else to reach you.

6. An update broke something

Websites are built out of parts, and those parts get updated. Most updates are uneventful; occasionally two of them disagree and you get a white screen or a 500 error within seconds. The tell is timing — it worked this morning, something got updated, now it doesn’t. The fix is to undo the last change. If your site keeps a saved copy of every version, you roll back and you’re live again while somebody works out what went wrong. If it doesn’t, you need a backup restored, which is a good moment to find out whether you have one.

7. Too much traffic at once

Rarer, but it happens to small businesses more than you’d think: a mention in the local paper, a post that takes off, an email blast that lands all at once. The site slows, then starts turning visitors away — on your best day, naturally. Call your host, tell them you’ve had a sudden spike, and ask for more room. Most can sort it while you’re on the phone.

8. The site was hacked

The signs: visitors get sent somewhere else, pages appear that you didn’t write, your listing in search results fills with nonsense in another language, or your own login stops working. Sometimes browsers put a “deceptive site ahead” warning in front of it, which is the version your customers see. Don’t just delete the pages you can see and hope — whatever let them in is usually still there. Get the site taken offline or restored from a known-clean backup, then change every password involved: hosting, domain, and the site’s own logins.

Who to call, and what to have ready

Three parties matter, and most owners aren’t sure which is which:

  • Your registrar — where you bought the domain name. They handle the name, its renewal, and the settings that point it somewhere.
  • Your host — where the site’s files live. They handle the server, the certificate and any suspension.
  • Whoever built or looks after the site — for the pages themselves, the updates, or a recent edit.

They’re sometimes all the same company and sometimes three different ones. Find out which today, while nothing is broken, and write it down somewhere that isn’t your website.

Having this ready turns a forty-minute call into a five-minute one:

  • The exact web address, spelled out, and the exact error message with your screenshot.
  • Roughly when it stopped working, and the last time you know for certain it worked.
  • Anything that changed recently — an update, a new email setup, a designer doing work, a card that expired.
  • Whether it’s down for everybody or only you, and what you already tried.
  • The account number, or the email address the account is registered to, so they can find you.

And ask direct questions rather than “is my site down?”. Is my account current? Is my domain expired? Is there an outage affecting my server? Is my certificate valid? Those four cover most of this article, and the person on the phone can answer all four in about a minute.

What to do while it’s down

You’re not only waiting. The phone still works, and so does everything else customers use to find you.

  • Post a short note with your phone number on your Google Business Profile and your Facebook page. Most people looking for you today will land on one of those.
  • If you’re paying for ads that point at the site, pause them. Don’t buy clicks to an error page.
  • Tell whoever answers your phone what’s going on, so a customer mentioning it doesn’t catch them out.
  • Don’t promise a time you can’t control — especially in a host outage, where the honest answer is that you’re waiting too.

The boring fix that prevents most of this

Look back at that list. Expired domain, unpaid hosting, a lapsed certificate, an update nobody checked, no backup to restore. Every one is a small administrative job that nobody owned. Websites rarely fall over for dramatic reasons — they fall over because the website is the one part of the business nobody looks at until a customer says something.

So: put the domain and the hosting on auto-renew with a card that isn’t about to expire, send the renewal emails to an address you actually read, and keep a backup you’ve genuinely tested restoring. Then have something checking the site around the clock — because the difference between a twenty-minute outage and a four-day one is hardly ever the fault itself. It’s how long it took someone to notice.

Common questions

How long will my website take to come back?
It depends entirely on the cause. A suspended account is usually back within an hour of the bill being paid, and a bad update can be undone in minutes if your site keeps old versions. An expired domain typically takes a few hours to spread back across the internet, and a host outage takes exactly as long as it takes — there’s nothing you can do to hurry that one.
My site loads for me but customers say it doesn’t. What’s happening?
That’s the classic sign of a settings change still spreading, or an old copy of the page saved on your own device. Check it on your phone with Wi-Fi off, which is the quickest way to see what a stranger sees. If it fails there, it’s down for real and your computer is just showing you yesterday’s version.
Will a few hours of downtime hurt my Google ranking?
A short outage is unlikely to do lasting damage — search engines come back and try again, and a normally reliable site gets the benefit of the doubt. Outages running for days are a different matter, because pages can start dropping out of results. The practical risk is less about ranking and more about the customers who tried you today and rang someone else.
Whose job is it to notice my site is down — mine or my web designer’s?
Unless you’re paying someone specifically to look after the site, the honest answer is nobody’s. Most designers build a site, hand it over and move on to the next project, which is a perfectly normal arrangement — it just means no one is watching afterwards. Ongoing care is a separate thing from building the site, and it’s worth being clear about which one you’re paying for.
Should I just rebuild the site somewhere else?
Almost never, and definitely not while you’re panicking. Every cause in this guide is fixable in hours or less, while a rebuild takes weeks and throws away the history search engines have built up about your pages. Get the site back first, then decide calmly whether the setup underneath it is one you want to keep.