Status page template: what to include
A practical checklist for the components, wording and structure of a status page your customers can trust.
A status page is the first place customers look when something breaks. A good one answers three questions fast: is it just me, what is affected, and when will it be fixed?
Start with the components
List every service your customers depend on — the website, the API, sign-in, payments, email — and show each one with its own current status. Group related services so a partial outage reads clearly.
Write incident updates people can act on
Update on a cadence, not only at the start and end. Say what is affected, what you know, what you are doing, and when the next update comes. Avoid jargon and never blame a provider without context.
Automate the boring 95%
Most of the time nothing is wrong, so let your monitoring keep the page current automatically and make manual overrides the exception. UptimeCadet's status pages update from live check results and add a read-only API for embeds.