Status pages: should a small business have one?
What a status page does, when a small business benefits from one, what it must not depend on, and the lighter alternatives that often suffice.
The short answer
A status page is a public page, hosted separately from your systems, that tells customers whether your service is working, what components are affected during an incident, what you are doing about it and when to expect the next update. Its value is that customers stop calling and start waiting, and that they hear about the problem from you rather than discovering it alone. It is worth having when customers depend on your service in real time: a client portal, an application they work in, a store in peak season, an API partners integrate with. For a brochure website it is unnecessary. Whatever the size, it must be hosted independently of everything it reports on, or it goes down with the incident it should explain. For many small businesses a lighter alternative suffices: a prepared notice for your channels and a holding page served by the network layer when the origin is down.
When it is worth it
| Situation | Status page? | Why |
|---|---|---|
| Brochure website | No | An outage is an inconvenience; a holding page and a social notice suffice |
| Store, especially in peak | Yes, or a prepared alternative | Customers mid-purchase need to know whether to wait or come back |
| Client portal or application | Yes | Customers’ work depends on it; support volume during incidents is high |
| API or integration partners depend on | Yes | Partners need machine-readable and human-readable status |
| Multiple services with different components | Yes | Customers need to know which part is affected |
| Contractual service levels | Yes | The page is the public record of incidents against targets |
Setting one up
- Choose a hosted status service on its own infrastructure; point a subdomain at it.
- Define the components customers care about, in their language: website, ordering, login, portal, API.
- Connect monitoring so component states update automatically where possible, with manual override.
- Write incident templates: investigating, identified, monitoring, resolved, with plain language.
- Offer subscription by email or feed.
- Link it from the footer, the support pages and the holding page.
- Practise: post a test incident and see how it reads on a phone.
The lighter alternative
For a business whose site is not depended on minute to minute: a holding page served by the network layer when the origin is unreachable, saying the site is temporarily unavailable and how to reach you; a prepared notice for your social channels and email signature; and the incident plan naming who posts it. It costs nothing, covers the brochure case and can be upgraded to a full status page when the business grows into one.
What this means for you
Have a status page if customers depend on your service in real time, hosted independently, with components in their language, monitoring connected, templates ready and a named person to post. Otherwise, prepare the lighter alternative. Either way, decide before the incident who tells customers what is happening, because the telling is what they remember.
Frequently asked questions
Is a status page not admitting that we have outages?
Every service has incidents; the question is whether customers hear about them from you or discover them alone. A status page that says what is happening and when it will be fixed reduces support contact, builds trust and shows competence. Silence during an incident is what damages reputation, not the page that explains it.
Can our website host its own status page?
No, because when the website is down the status page is down with it. A status page lives on separate infrastructure, a separate domain or subdomain pointed at a hosted status service, so it is reachable exactly when it is needed. That separation is the whole point of the page.
What should it show?
The components customers care about, each with a state; current incidents with plain-language updates and times; scheduled maintenance; and a way to subscribe to updates. Not internal metrics, not a dashboard, not marketing. A customer should understand in five seconds whether the thing they need is working and what to expect.