Why websites go down, and how to prevent it
The common reasons small business websites go offline, from expired domains to bad updates, and the simple precautions that prevent most outages.
Websites rarely go down for exotic reasons. When a small business site disappears, the cause is usually something ordinary: a bill that did not get paid, an update that did not agree with another update, or a server having a bad morning.
That is encouraging, because ordinary problems have ordinary fixes. Here are the usual suspects, roughly in the order we see them, and what to do about each.
The paperwork failures
These are the most avoidable outages and, awkwardly, among the most common.
The domain expired
Your domain registration has a renewal date. Miss it and the address stops working. The website is still sitting safely on its server, but nobody can reach it, and your email on that domain stops as well.
It nearly always comes down to an expired credit card or reminder emails going to an address nobody reads any more.
The hosting was not paid
Same story, different account. Hosting companies suspend sites when a payment fails, sometimes with little warning.
The security certificate lapsed
The certificate that gives you the padlock has an expiry date. Normally it renews itself. When that renewal fails, visitors are met with a full page warning telling them the site may be unsafe. The site is technically up, but practically nobody will click past that screen.
Prevention: switch on auto renew for the domain and hosting, keep the payment card current, send reminders to an inbox that is read, and keep a short list of renewal dates in your calendar.
Hosting faults
Servers are physical machines in buildings, and they fail. Hardware wears out, a network connection drops, a data centre has a power problem. On shared hosting, another site on the same server can hog resources or attract an attack, and everyone on that server slows to a crawl.
You cannot prevent these yourself. What you can do is choose a host with a good track record and clear communication, and know how to reach their support and check their status page when something seems wrong.
Brief blips are part of life on the internet. Frequent or long outages are a reason to move.
Updates that break things
If your site runs on a content management system, it depends on a stack of software that is updated regularly. Most updates go through without a murmur. Occasionally one does not, and you get a blank white page, an error message, or a site that loads but with the checkout or contact form quietly broken.
The risk goes up when updates have been neglected for a long time and a dozen are applied at once, or when updates are set to apply automatically with nobody checking the result.
Prevention: take a backup before updating, update regularly in small batches, and look over the site afterwards. For anything substantial, try it on a test copy of the site first.
Other causes worth knowing
- A DNS mistake. DNS is the set of records that tells the internet where your site lives. One wrong entry, often made while changing email or moving hosts, and the site vanishes.
- A sudden crowd. A mention on the local news or a popular social post can send more visitors than a small hosting plan can handle. A nice problem, but still a problem.
- A full disk or hit limit. Budget plans have ceilings. Years of uploaded photos or log files can fill the space and bring things to a halt.
- A hack. A compromised site may be taken offline by the host, or blocked by browsers, until it is cleaned.
Monitoring: find out before your customers do
The worst way to learn your site is down is from a customer, three days after it happened.
Uptime monitoring fixes that. A monitoring service checks your site every few minutes from outside and sends an alert by email or text the moment it stops responding. Good monitoring also watches the things that fail slowly: certificate expiry, domain expiry, and whether the page loading is actually your page and not an error message.
Two cautions. An alert only helps if it goes to someone who will act on it, so decide who that is. And monitoring does not catch everything. A contact form can stop delivering while the site looks perfectly healthy, which is why a monthly test enquiry is still worth doing by hand.
What to do when your site is down
Keep this list somewhere other than on your website.
- Confirm it. Try another device, and turn off wifi on your phone to use mobile data. Sometimes the problem is your own connection.
- Read the error. A security warning points to the certificate. "This site can't be reached" suggests the domain or DNS. A hosting company's holding page suggests billing or suspension. An error page from your own site suggests a software fault.
- Check the obvious accounts. Log in to your registrar and your host. Is anything expired or unpaid?
- Think about what changed. Was anything updated or edited in the last day?
- Contact support. Call whoever looks after the site, or the host, with what you have found.
- Tell customers if it drags on. A quick note on your social pages and your Google Business Profile, with a phone number, keeps enquiries coming.
Afterwards, ask what would have caught it sooner. It usually comes down to one of four things: auto renew, monitoring, a backup, or a named person responsible. With all four in place, outages become rare and short.