Blog / How the internet works /
Status pages for small businesses
When your website or app has a problem, customers do what anyone does: they go looking for an answer. If they can’t find one, they email you, message you on WhatsApp, tweet at you and refresh the page every thirty seconds. Your inbox fills up with the same question twenty times: “Is it down?”
A status page answers that question once, in public, so you can spend your time fixing things instead of replying to each person.
What a status page is
It’s a simple page, usually on its own address like status.yourbrand.com, that shows whether your service is working and what’s going on if it isn’t. Large companies have them: the big cloud providers and payment services all publish status pages, and people check them first when something breaks.
But you don’t need to be large. Any small business whose customers depend on a website, a booking system, an app or an online shop can benefit.
Do you actually need one?
Be honest here. A status page is useful if:
- Customers log in or rely on you (a booking tool, a members area, a SaaS, a web shop with frequent orders).
- You get the same “is it down?” message more than occasionally.
- You depend on third-party services (payments, shipping, email) that could fail without it being your fault.
- You manage sites for clients and want a clear, shared source of truth.
You can skip it if you run a small brochure site that gets a handful of visits a day. A status page for a site nobody checks in a panic is a distraction. A simple “contact us” with a phone number does the job.
What goes on it
Keep it plain.
- Current status. A clear headline such as “All systems operational”, or “Checkout is slow”.
- Components. Break things into the parts customers care about: Website, Checkout, Customer login, Email notifications. If only one part fails, you say so.
- Active incidents. What is wrong, since when, what you know, and when you’ll update again.
- History. A list of past incidents, which builds trust over time. Hiding history looks worse than having had problems.
- A way to reach you that doesn’t depend on the broken thing. If your website is down, a contact form on it is no use. Offer a phone number, WhatsApp or social account.
- Optional: subscribe. Let people get updates by email or SMS if your tool supports it.
How to write an incident update
This is the hard bit. In the middle of a problem, wording matters more than design.
- Say what customers experience, not what the server did. “Some customers can’t complete payment” beats “database latency increased”.
- Say what you’re doing, even if that is “investigating”.
- Give the time of the next update, and keep to it.
- Don’t speculate about causes you haven’t confirmed, and don’t promise a fix time you can’t guarantee.
- Close the loop. When it’s fixed, say so, and give a short, honest summary afterwards.
A good update sounds like a person: calm, specific and brief.
Where to host it, and one important rule
Host it somewhere separate from your main site. A status page on the same server as the thing that has failed will fail with it. If your site runs on WordPress on one host, don’t put the status page on the same hosting account.
Options, from cheapest to most polished:
- Your uptime monitor’s built-in page. Many monitoring services include a public status page on their free or low-cost plans, and update it automatically. This is where I’d start; see the uptime monitoring setup I use for client sites for the monitoring side.
- A dedicated status page service. There are several, with free tiers aimed at small teams, offering subscriptions, scheduled maintenance notices and custom domains.
- A simple static page on a different host or free static hosting, edited by hand. It’s basic but it works, and it’s hard to break.
- A social account or WhatsApp broadcast as a stopgap, if the audience already lives there.
Automatic vs manual
Automatic pages update from monitoring checks, so they flip to “down” without you doing anything. They’re honest and fast, but they can’t explain. Manual pages let you write the context, but only if you remember to update them in the middle of a crisis.
A mix works best: automatic status for the main components, plus the ability to add a human note.
Planned maintenance
A status page isn’t only for disasters. Use it to announce planned work in advance: “Saturday 10pm to 11pm: shop will be unavailable while we move to a new server”. Customers appreciate warning far more than surprise, and it lowers support messages. If you’re planning a bigger move, hosting migrations without losing rankings is worth reading too.
Common mistakes
- Putting the status page on the same server as the service.
- Never updating it, so it says “all fine” while customers are complaining.
- Technical language nobody outside your team understands.
- Blaming a third party instead of explaining the effect.
- Having it but not linking to it. Add the link to your site footer, your support email signature and your auto-replies.
Key takeaways
- A status page answers “is it down?” once instead of twenty times.
- Worth it when customers depend on you or you handle repeat support questions.
- Show current status, components, incidents with times, and history.
- Write updates in plain language and promise only the next update time.
- Host it away from your main site, and link to it from places people will look.
Related reading
If your site went down tonight, where would your customers go to find out why?