Why a status page earns trust
A status page is a public page where you publish your service's current state, active incidents, and planned maintenance. Its real job is to answer one question before your support inbox fills up: "is it down for everyone, or just me?" A page that is honest during a bad hour builds more trust than a wall of green ever does, because customers judge you on how you communicate under pressure.
The goal is a page customers can rely on without contacting you — self-service that is faster for them and cheaper for you.
Current status and components
Lead with the current state, broken down by component rather than a single site-wide light. Separating "API", "dashboard", and "email delivery" lets a customer see that the part they use is fine even when something else is degraded, and it stops one small problem from looking like a total outage. Attach each component to real monitoring so the status reflects measured reality, not a switch someone forgot to flip.
Incident updates people can act on
When something breaks, publish an incident and keep it updated on a rhythm. A good update says what is affected, what you know, what you are doing, and when the next update will come — even if the next update is only "still investigating". Committing to a cadence is what stops customers from refreshing and guessing. Post a clear resolution when it is over, and keep the timeline visible so the history is honest.
Scheduled maintenance
Announce planned work before it happens, with the window and the expected impact, so a deliberate change is never mistaken for an outage. Maintenance notices also give customers a chance to plan around the window. A status page that distinguishes planned maintenance from unplanned incidents reads as a service that is in control of its own changes.
History, subscriptions, and what to leave off
Show uptime history so the page has context beyond this moment, and let visitors subscribe for updates so they do not have to keep checking. PageLantern hosts public status pages that show the live state of the monitors you attach, publish incident timelines and maintenance windows, and let visitors subscribe for email updates.
Leave off anything you cannot keep accurate. A metric nobody updates, or internal detail that only invites confusion, erodes the trust the page exists to build. Fewer things, kept truthful, beats a dashboard of stale numbers.