Appearance
Status pages
An organisation can maintain multiple status pages. Each page has an internal name, public slug, title, description, public state, and ordered widgets. One page is the organisation default.
Build each status page from HTTP endpoint, user-impact monitor, heartbeat, incident timeline, and markdown widgets. This lets you choose the exact service view for its audience.
Use a page for a customer, product, region, or service boundary when its selected signals can be shared safely. Keep internal hostnames, secrets, customer identifiers, and diagnostic details out of titles, descriptions, markdown, and incident updates.
Hiding a monitor from a page does not disable monitoring. Making a page private hides its public route without deleting its configuration.
Operational incidents can be published to selected pages. Public status updates are a communication record, not the internal acknowledgement and escalation timeline.