Website care · 17 Nov 2026 · 7 min read
What to do when your website goes offline
When a website is down, work from the simple causes outwards, contact the right provider and tell customers. This guide gives the order of checks and a plan for next time.
The short answer
When your website is down, first check whether it is down for everyone by testing on mobile data. Then check the domain, hosting account, certificate, host status page and recent updates. Contact the provider that controls the failed part, tell customers another way to reach you, and set up uptime alerts.
First, confirm that the site is really down
When your website is down, the first job is to find out whether it is down for everyone or only for you. Open the site on a phone using mobile data, not your office wifi. Ask someone in another place to try. Use a free "is it down" checker from any reputable provider. If the site loads elsewhere, the fault may be your own network, a cached copy in your browser or a local DNS problem.
Then note exactly what you see, because the message points to the cause. Take a screenshot and write down the time. The common messages mean different things.
| What you see | What it usually points to |
|---|---|
| Site can't be reached, or the server cannot be found | A domain or DNS problem, or a server that is offline |
| Connection timed out | The server is not answering, or is overloaded |
| A security or certificate warning | An expired or misconfigured certificate |
| A server error page, often described as a 500 type error | An error in the site's code, plugin or database |
| A maintenance message or a blank white page | An update that stopped part way, or a code error |
| A suspended or parked page | An unpaid or expired hosting or domain account |
How do I find out why my site is down?
Work from the outside in. Check the simple, common causes first, because they are the quickest to rule out.
- Log in to the domain account. Has the domain expired, or been suspended? An expired domain takes the site and the email offline together.
- Log in to the hosting control panel. Look for a suspension notice, a billing issue, a status banner or an exceeded resource limit.
- Many hosts publish a status page. Check it for an outage on their side.
- If visitors see a security warning, the certificate may have expired. Our guide to HTTPS and SSL certificates explains how certificates work and how to renew one.
- Think back. Was a plugin, theme or the platform updated today? Did anyone edit code or settings? Most outages follow a change.
- The hosting panel usually has an error log that names the failing file or process. Send it to whoever maintains the site.
Keep notes as you go. A short list of what you checked and the time helps the next person you call and prevents the same checks being repeated.
Who should I contact first?
Contact whoever controls the part that failed, in this order.
- If the message points at the domain or the account, contact the domain registrar or hosting company's support. Have your account details ready.
- If the host says the server is fine, contact the person or company that maintains the site. Give them the time, the message, the screenshot and what changed.
- If the site was just updated, ask them to roll back to the last working version before looking for a perfect fix.
- If you suspect that someone has tampered with the site, tell your developer and your host at once, and do not make changes that destroy evidence.
It saves a great deal of time to know in advance who these people are. Keep a one page list somewhere that does not depend on the website: who holds the domain, who holds the hosting, who maintains the site, and their contact routes. Our guide to when fixing is enough and when to redesign explains how ongoing care fits with bigger changes.
When you contact support, be concrete. Say what the site address is, what the error says, when it started and what you have already tried. Avoid saying only "the site is broken".
Common causes and the usual fix
Expired domain or hosting
Renew it, then allow time for the change to spread. Turn on automatic renewal and make sure the billing contact is an address that someone reads.
Expired certificate
Renew or reissue the certificate. Many hosts do this automatically, but a changed setting can stop it. Check your host's current documentation.
Failed update or plugin conflict
Restore from a backup taken before the update, or disable the plugin that caused the problem. This is why every update should be preceded by a backup, and tested on a copy first.
Overload
A burst of visitors, a bad bot or a heavy page can use up the resources your hosting plan allows. The site may come back by itself, but the cause needs fixing. Slow, heavy pages make this worse; see Core Web Vitals explained for how page weight and speed connect.
Code or database error
Often shown as a server error. A developer needs to read the log. If the database is full, corrupt or disconnected, the site may need a database repair or restore.
Attack or malware
If the host has blocked the site, or you see unfamiliar content, this needs a professional clean-up, new passwords and a review of how the intruder got in.
While the site is down
Tell your customers, even if you have no fix yet. Post a short note on your social media accounts, change your email signature or voicemail if people usually reach you through the site, and give an alternative way to order or book. A calm line such as "our site is having a problem; you can reach us by email or phone" prevents lost trade and confusion.
Do not make big changes in a panic. Fix one thing at a time and note what you changed. Avoid reinstalling the whole site unless you have a verified backup. If you have paid advertising running to the site, pause it so you do not pay for visitors who land on an error.
For search visibility, a short outage generally does not do lasting harm. A long one can. If the page must be unavailable for a planned period, a developer can return the right status code so search engines know it is temporary. Check Google's current documentation on handling site downtime.
How do I get an alert before customers notice?
Set up uptime monitoring. A monitoring service requests your site from outside your server at regular intervals and sends an email or message if it fails to respond. Many services have a free level that is enough for a small site, but check the current terms of whichever one you choose.
Make the checks useful:
- Monitor the home page and one or two important pages, such as the contact page or checkout.
- Check for specific text on the page and not just a response, so that a blank page is caught.
- Send alerts to more than one person, by different routes.
- Watch the certificate expiry date and the domain expiry date as well.
- Test the alert itself once, to be sure it arrives.
Monitoring tells you that something is wrong. It does not fix it, so pair it with the contact list described above. A short written plan is enough.
Reduce the chance of next time
Most outages are predictable. Keep software updated on a schedule, with a backup before every update. Take backups that are stored away from the server and test restoring one. Keep the number of plugins and add-ons reasonable. Use hosting that matches your traffic. Put renewal dates in a shared calendar.
Fonts, scripts and other files loaded from outside providers can also fail or slow the page; the guide on web fonts covers one such dependency. A site that must be accessible to all visitors also needs a stated route for people who cannot use a broken page; our guide to the accessibility statement explains how to give visitors an alternative contact path.
After any outage, write down what happened, the cause, the time to fix and what you will change. If you need help with monitoring, backups or ongoing care, see our website development service.
Related guides
- Website development
- Https and ssl certificates explained
- Core web vitals explained
- Website maintenance vs redesign when fixing is enough
- Web Fonts: How to Choose and Load Them Without Slowing Your Site
- Website Accessibility Statement: What to Include
Questions and answers
How do I find out why my site is down?
Check whether it is down for everyone using a phone on mobile data. Then look at domain and hosting account status, the host's status page, certificate expiry, recent updates and the error log in the hosting panel. Note what you see and the time.
Who should I contact first when my website is down?
If the problem is the domain or hosting account, contact that provider. If the host says the server is fine, contact whoever maintains the site and give them the message, the time and any recent changes. Keep this contact list outside the website.
How do I get an alert before customers notice?
Use an uptime monitoring service that checks your site from outside at regular intervals and emails or messages you on failure. Monitor key pages, check for text on the page, alert more than one person and watch domain and certificate expiry dates.
Will being offline hurt my search rankings?
A short outage usually does not cause lasting harm, but a long one can. Fix it quickly. Check Google's current documentation on site downtime, and ask a developer how to signal that an outage is temporary.
Should I restore a backup straight away?
If a recent update caused the fault and you have a tested backup from before it, restoring is often the quickest fix. If you are unsure of the cause, or a break-in is possible, ask your developer first so that evidence is not lost.
What should I tell customers while the site is down?
Say briefly that the site has a problem and give another way to reach you or order, such as email or phone. Post it on your social profiles, and pause paid adverts that send visitors to the broken site.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.