A status page is a public dashboard that displays the current health of a service and the history of past incidents. Status pages set customer expectations during outages, cut inbound support volume, and act as the single source of truth communications teams…
Also known as: Status page, Public status page, System status
Modern status pages support three surfaces: component health (per-service up/down/degraded), incident history (with post-mortem write-ups), and subscription (email, RSS, webhook, or Slack push when status changes).
Good status pages are hosted on a separate origin from the product so that a full outage still leaves the status page reachable. Lemwatch runs status pages on isolated infrastructure and supports vanity URLs like status.yourbrand.com via custom CNAME.
Silence during an outage is worse than the outage. A live status page turns 200 angry support tickets into 200 customers refreshing the same page — and gives your team the breathing room to actually fix the issue.
See it in the product: Branded status pages.