Short version: a status page earns trust when it's independently hosted, updated fast and honestly during incidents, and specific about impact. The most common mistakes are hosting it on the same infrastructure as your app, going quiet during incidents, and using vague language that hides the real impact.
Do these
- Host it independently. Your status page must survive your own outage. Serve it from separate infrastructure, ideally with a cached last-good snapshot so it renders even if your backend is down. PingInsight does this with SSR/ISR rendering.
- Update fast, then keep updating. The first update should go out within minutes of confirming an incident — even "we're investigating" beats silence. Then update on a predictable cadence until resolved.
- Be specific about impact. "Some users may experience errors creating invoices" tells customers what to expect. "We're experiencing issues" tells them nothing.
- Use a clear lifecycle. Investigating → Identified → Monitoring → Resolved gives readers a mental model of where things stand.
- Write a postmortem. After significant incidents, publish what happened, the impact, and what you're changing. This is where trust is actually built.
- Let people subscribe. Email and RSS/Atom so customers and your own support team get pushed updates instead of refreshing.
Avoid these
- Don't co-host with your app. The classic failure: the status page goes down with everything else.
- Don't go dark. Silence during an incident reads as either "they don't know" or "they're hiding it." Both erode trust.
- Don't sugar-coat. Vague language fools no one and frustrates the customers who are actively affected.
- Don't fake the history. Uptime bars built on coarse monitoring round in your favor; eventually someone notices the gap between your page and their experience.
Automate what you can
Manual status updates lag reality. Connect your status page to monitoring so a confirmed outage can open an incident automatically and auto-resolve with the exact downtime duration when service recovers. Combined with 1-second detection, your page reflects what's actually happening — to the second.
See great status page examples for patterns worth copying.