Incident response template
- Confirm the outage from an external monitor before escalating.
- Assign one incident owner and one communications owner.
- Record first seen time, affected URL, expected status, actual status, and recent deploy context.
- Notify the responsible channel with the current customer impact and the next update time.
- Update the status page when the incident is confirmed, degraded, monitoring, and resolved.
- Close the incident with root cause, recovery time, prevention notes, and follow-up owner.
Incident summary: <service> returned <actual status> instead of <expected status> at <time>. Owner: <name>. Next update: <time>.Public demo
Review the real product screens with read-only mock data
Open the demo workspace to inspect monitors, incidents, domains, alert channels, status pages, projects, issues, automated test runs, releases, artifacts, audit history, and umbrella reports without creating an account.