Status Reports

A status report communicates an incident on a status page. It has a title, affected components, and a timeline of messages with dates and incident states.

Publish and update

Create a report from the status page in the dashboard. Use the composer to write and preview the message, choose affected components and their impact, and review the subscriber notification choice before publishing.

Add updates as the incident moves through investigating, identified, monitoring, and resolved. Choose the state that reflects current evidence; resolving a report is a communication action and does not prove a monitor or service has recovered.

Dashboard attribution helps your team identify who created or edited an update. Public visitors receive the report content and dates without dashboard user profiles.

Reports and detected incidents

A monitor's detected failure and a public report are distinct records. Review the customer impact and affected components when creating public communication rather than treating every failed check as a published incident.

See Publish a status report for the workflow and Maintenance for planned work.