solobuild
Your website going down is one of the most stressful things that can happen to a one-person business, mostly because there is nobody else to call. There is no IT department and no ops engineer on standby, just you, a blank browser tab, and a growing sense that customers are seeing it too. The good news is that most outages come from a short list of causes, and you can work through that list calmly in about fifteen minutes. This guide walks through the order to check things, what each result tells you, how to talk to customers while it is broken, and the few changes that make the next outage shorter or keep it from happening at all.
First, confirm the site is actually down
Before you log into anything, make sure the problem is not on your end. A surprising number of apparent outages turn out to be a local issue, like a cached DNS answer on your laptop, a VPN routing traffic strangely, a browser extension blocking a script, or a hiccup with your own internet provider. The quickest test is to turn off Wi-Fi on your phone and load the site over mobile data. If it loads there but not on your computer, the site is fine and the fault is somewhere between you and it.
The second test is to check from outside your network entirely. Free checkers like isitdown.page or HostTracker send a request from their own servers and tell you whether the site responded. If those tools can reach it, your visitors probably can too, and you can stop worrying and restart your router. If they cannot reach it, the outage is real and it is time to figure out which layer broke.
It also helps to note exactly what you see, because the error message is your best clue. A browser warning about the connection not being private points to your SSL certificate. A message saying the server's address could not be found points to DNS or your domain. A plain "500 Internal Server Error" or "503 Service Unavailable" means the server was reached but something on it failed. A page full of ads or a registrar's parking page means your domain has almost certainly expired. Write the message down or screenshot it, since your host's support team will ask for it anyway.
Work through the common causes in order
The order matters here, because some checks take thirty seconds and rule out a whole category of problems. Start with the domain, since an expired domain takes everything offline at once and gives you no helpful error. Look up your domain on ICANN's lookup tool (lookup.icann.org) and read the expiry date. If it has lapsed, log into your registrar and renew it right away. Most registrars hold expired domains in a grace period for a few weeks, so you can usually get it back at the normal price if you act quickly, though DNS may take a few hours to come back after renewal.
If the domain is fine, check your host's status page next. Every major host publishes one, and outages at the hosting level are far more common than problems in your own site. If your host is reporting an incident, there is very little you can do except wait and communicate, which is covered in the next section. It is worth bookmarking this page now, before you need it, because finding it in a panic is harder than it sounds.
When the host looks healthy, look at your SSL certificate. An expired certificate does not technically take your site down, but modern browsers show a full-page warning that most visitors will not click past, so it has the same effect. Most hosts now issue free certificates through Let's Encrypt and renew them automatically, but that renewal can fail silently if DNS changed or a setting was toggled. Your hosting dashboard usually has a button to reissue the certificate, and that fixes it in a few minutes.
If none of those explain it, the problem is likely inside your site itself. On a WordPress site, the most common trigger is a plugin or theme update that broke something, especially if the outage started right after an update ran. You can test this by renaming the plugins folder over FTP or your host's file manager, which disables every plugin at once. If the site comes back, rename it back and turn plugins on one at a time until you find the culprit. Running out of storage space or hitting your plan's resource limits can also cause 500 and 503 errors, and your hosting dashboard will show both.
The last cause to consider is a hack. Signs include your site redirecting to spam pages, strange new admin users, files you did not create, or a warning from Google that the site may be harmful. This is the situation where you should stop trying to fix things yourself and restore from a clean backup or bring in help, because partial cleanups often leave a back door behind and the site gets reinfected within days.
Communicate while it is broken
Customers are much more forgiving of an outage they know about than one they discover on their own. If the site is going to be down for more than a few minutes, post a short note wherever your audience already follows you, whether that is your email list, X, LinkedIn, or a pinned message in your community. It does not need to be detailed. A line saying the site is having issues, that you are working on it, and when you will post the next update is enough.
If you sell something with ongoing access, like a SaaS product or a membership, consider a simple status page on a separate service. Tools like Better Stack include a hosted status page on their free plan, and because it lives on their infrastructure, it stays up when your site does not. That gives you one link to point people toward instead of answering the same question in five places.
Once it is fixed, send a brief follow-up explaining what happened in plain language. You do not need to write a technical postmortem, and nobody expects one from a solo founder. Something like "our domain renewal failed and the site was offline for two hours, and I have turned on auto-renew so it does not happen again" builds more trust than silence, because it shows you are paying attention.
Set things up so the next outage is shorter
Most of the damage in an outage comes from not knowing about it. Plenty of solo founders have found out their site was down from a customer email, sometimes a full day after it broke. An uptime monitor fixes this by checking your site every few minutes and sending you an alert the moment it stops responding. UptimeRobot's free plan covers 50 monitors at five-minute intervals, and after a period where the free tier was restricted to non-commercial use, its current terms allow business use again. Better Stack's free plan gives you 10 monitors with three-minute checks plus a status page, which is plenty for most one-person businesses.
The next thing to fix is your backups, since a recent backup turns a disaster into a twenty-minute restore. The detail people miss is where the backups live and how often they run. Some entry-level hosting plans take daily backups automatically but only let you restore them by contacting support, while higher tiers add on-demand backups you can trigger before an update. SiteGround keeps 30 days of daily backups, and its GrowBig plan adds on-demand backups, which is the feature you actually want when you are about to update a plugin. Its StartUp plan was listed at $2.99 per month for the first term at the time of writing, renewing at $17.99, so check the renewal price before you commit rather than just the introductory one.
Turn on auto-renew for your domain and make sure the card on file is current. An expired card is the quiet reason behind a lot of lapsed domains, since the registrar tries to renew, fails, sends a warning to an inbox you never check, and then lets it go. While you are in your registrar account, update the contact email so those warnings reach an address you actually read.
If your site has been hacked before, or if it takes payments or stores customer data, a web application firewall is worth considering. A WAF, short for web application firewall, sits in front of your site and filters out malicious traffic before it reaches your server, which blocks most automated attacks and many denial-of-service attempts. Sucuri bundles a firewall with malware scanning, uptime monitoring, and unlimited malware cleanup, with platform plans starting at $199.99 per year. That is a real cost for a small site, so it makes the most sense when the site earns money directly or has already been targeted. For a simple portfolio or landing page, good backups and a monitor are usually enough.
Tool comparison
Here is how the tools mentioned in this guide compare. Prices were current at the time of writing, but hosting and security prices change often, so confirm on each vendor's site before buying.
| Tool | Best For | Free Tier | Starting Price |
|---|---|---|---|
| UptimeRobot | Simple uptime alerts across many sites | Yes, 50 monitors at 5-minute checks | Paid plans add faster checks and SMS alerts |
| Better Stack | Monitoring plus a hosted status page | Yes, 10 monitors at 3-minute checks and a status page | Paid plans add 30-second checks |
| SiteGround | Managed hosting with daily backups | No | $2.99/mo intro, renews at $17.99/mo |
| Sucuri | Firewall, malware cleanup, and hack recovery | No | $199.99/yr for the Basic Platform |
For most one-person businesses, the sensible order is to add a free uptime monitor today, confirm your backups next, and only add a paid firewall once the site earns enough that a day of downtime or a hack would cost more than the subscription.
Frequently asked questions
How do I know if my website is down for everyone or just me?
Load the site over mobile data with Wi-Fi turned off, then check it with an external tool such as isitdown.page or HostTracker. If those tools can reach it, the problem is local to your device or network. If they cannot, the site is down for everyone and you should start checking your domain, host, and certificate.
What is the most common reason a small business website goes down?
Hosting-level outages are the most frequent cause, followed by expired domains, expired SSL certificates, and broken plugin or theme updates. An expired domain is especially common for solo founders because renewal warnings go to old email addresses or fail on expired cards. Checking the expiry date takes less than a minute and rules it out quickly.
How long does it take for a website to come back after renewing an expired domain?
It usually comes back within a few hours, though it can take up to 24 to 48 hours in some cases while DNS changes spread across the internet. Some visitors will see the site return sooner than others during that window. If it has been more than two days, contact your registrar and confirm the domain is pointing at the correct nameservers.
Should I contact my hosting provider when my site goes down?
Yes, once you have ruled out the domain and checked their status page. Give them the exact error message, the time it started, and anything you changed recently, such as a plugin update. Good hosts can see server logs you cannot, and they can often identify the cause in minutes.
The short version
When your site goes down, resist the urge to start changing things at random. Confirm it is really down from outside your network, read the error message, and work through the domain, the host, the certificate, and your own site in that order, because each check rules out a whole layer. Tell your customers early, even if all you can say is that you are on it. Then spend an hour this week setting up an uptime monitor, checking that your backups exist and can be restored, and turning on domain auto-renew with a working card. Those three changes will not prevent every outage, but they will make sure you hear about the next one first and can recover from it quickly.