Status Page

A status page is a dedicated communication channel — usually public or login-gated — where you show component health, post incident updates, and announce maintenance windows. It answers the question customers ask first during an outage: “Is it just me, or is something wrong on your side?”

Status pages are part of external incident communication, distinct from internal war rooms. They should be driven by the same facts your team tracks internally, but written for a non-technical audience.

Why it matters

Proactive updates reduce support tickets, prevent duplicate bug reports, and signal competence. Silence during a visible outage erodes trust faster than the technical failure itself. The incident commander or a dedicated comms lead usually owns what goes on the page while engineers fix the problem.

Incido’s Incido status pages ties component health, incident stages, and subscriber notifications together so customer messaging stays aligned with your internal timeline.

Example

Checkout errors spike at 11:05. By 11:12 the comms lead publishes: “We are investigating elevated errors on Checkout. Payments may fail. Next update by 11:30.” Subscribers get email; the public page shows degraded status on the Payments component. At 11:40, an update marks the incident resolved. Support volume stays manageable because customers self-serve status.

Common mistakes

• Waiting until the fix ships — an early “investigating” update beats perfect certainty.
• Internal jargon — “shard rebalance” means nothing to customers; describe impact.
• Contradicting the page in social media — one voice, one timeline.
• Never testing maintenance messaging — scheduled work needs the same clarity as incidents.

Use the status page update template for consistent tone and timing. Connect page updates to incident stages so resolved means resolved for customers, not just for engineers.