---
title: "Your website has stopped working: what to check in the first 30 minutes"
description: "If your site won't load, throws a 500 error or has vanished from Google, it's almost always one of these five causes. How to find out which in 30 minutes."
date: "2026-11-10"
category: "Website maintenance"
keywords: "my website is down, website not loading, error 500 website, expired SSL certificate, hacked website redirects, website maintenance"
portada: "/portadas/portada-tu-web-ha-dejado-de-funcionar.webp"
---

It's ten past nine in the morning and a customer sends you a screenshot: "It says the page isn't available". You open the link on your phone and it doesn't load either. That is the moment when most people start poking at things at random and turn a ten-minute outage into a weekend without a website.

First of all: breathe and don't delete anything. Almost everything that breaks on a website can be fixed, and almost everything that gets ruined for good gets ruined because someone in a hurry reinstalled, deleted or changed the DNS without writing down what was there before.

These are the five suspects, in the order in which it makes sense to rule them out.

## 1. It isn't your website: it's your connection or your browser

It sounds like a joke, but it happens every week. Before calling anyone:

- Open the site on your phone using **mobile data**, not the shop's wifi. If it loads there, the problem is your network or your router.
- Try an **incognito window**. If it works there and not in the normal window, it's your cache or an extension.
- Ask someone outside (a customer, a relative in another city) to open the link. If it loads for them, the site is alive.
- Tell https:// apart from http://, and with and without "www". Sometimes only one of the four combinations has broken.

If it doesn't load from outside either, you now know the problem is real and it's on the server.

## 2. Read the exact message, not the headline

"The website doesn't work" tells you nothing. The error message is the most valuable clue you're going to get, and it's free:

- **500 / 502 / 503**: the server is up, but the program inside it has failed. Usually a recent change, an update or the hosting being down.
- **403**: someone has closed off access, normally a permissions change or a hosting block.
- **404 on the homepage**: the site responds, but it can't find the start file. Typical of a half-finished update or a moved folder.
- **"This site can't be reached" plus something about DNS**: the domain no longer points anywhere. Almost always an expired domain or a changed DNS.
- **"Your connection is not private" or invalid certificate**: the security certificate has expired. The site works underneath, but browsers block it with a red screen that scares off one hundred per cent of visitors.
- **ERR_TOO_MANY_REDIRECTS**: someone has added a redirect rule that bites its own tail.

Take a screenshot of the error. With that, whoever looks after your site knows where to start in thirty seconds.

## 3. Cause number one: an expired card

Before hunting for hackers, check your email. Look for invoices from the hosting, the domain or the company that runs the website and see whether there's any notice of non-payment, failed renewal or "your service will be suspended".

It is the most common cause of "my website has disappeared": the automatic payment failed because the card expired, the bank blocked the charge or the account changed. The hosting suspends, the site stops responding and, if days go by, the domain enters a grace period and is then released. At that point it isn't an outage, it's a serious problem.

Fixing it is usually as simple as paying the outstanding invoice and waiting between ten minutes and a couple of hours. If the domain has already expired, rescuing it depends on how many days have passed and whether someone else has bought it. We explain it in detail in [what happens if you stop paying for your website](/blog/en/que-pasa-si-dejas-de-pagar-tu-web).

## 4. A change from the last 48 hours

If the site worked yesterday and doesn't today, ask yourself what changed: an update to the content manager, a new plugin, a template, a DNS change, a hosting migration or someone touching the configuration file.

The rule is simple: **if it broke after a change, it's fixed by undoing that change**. If you have a backup from before, restoring it is the fastest route. And if you don't have one, there's today's lesson.

## 5. When the problem is that someone got in

The signs of a compromised website are fairly recognisable: the site redirects to an online pharmacy, pages appear that you didn't create, Google shows "this site may have been hacked" or the hosting sends you a malware notice.

In that case, three things and in this order: don't delete anything, change the passwords for hosting, email and the website manager from a clean computer, and tell whoever looks after your site so they can clean the code and review the modified files. If customer data is also at stake, there are legal obligations worth looking at calmly.

Restoring a clean backup from before the infection is almost always faster than trying to clean file by file.

## What to do in the meantime

- Put up a simple **maintenance page**, with the logo, one sentence ("we're fixing the website, back in a few hours") and the phone number. Losing the website is annoying; losing the website with no explanation is what makes the customer call your competitor.
- **Tell your customers** who had a booking or an order in progress. A two-line WhatsApp message is worth more than any press release.
- **Don't touch the email** if it's working. The website and the email usually travel along different paths; changing the DNS in a hurry is the most common way of taking the emails down too.

## How to avoid repeating this

A website doesn't maintain itself, just as a blind doesn't oil itself. The reasonable minimum:

- **Automatic backups** and, every so often, one downloaded off the server.
- **Renewals with a valid card** and notices going to the email address you actually read.
- **A security certificate that renews itself** and a check that it really does.
- **A watchman that alerts you** when the site stops responding, instead of finding out from an angry customer.
- **A document with every access** (domain, hosting, email, manager) in the hands of someone you trust. If the person who built your website disappeared tomorrow, could you take back control?

All of this is more or less what website maintenance includes, and its real cost is broken down in [how much it costs to maintain a website per year](/blog/en/cuanto-cuesta-mantener-una-web).

## Conclusion

A website that's down is almost never an irreversible disaster: it's a chain of three or four checks that take half an hour. What does turn an afternoon of scares into a lost week is improvising without knowing what you're touching.

If your website is giving you trouble and you don't know where to start — or if you'd rather have a new website built so it doesn't depend on anyone, with backups and alerts from day one — [request a free design proposal with no obligation](/solicita-web/en). In two days you'll know what you have and what it would cost to fix it.
