Incident timeline
An incident opens by itself and writes its own timeline as it runs.
0
notes to take by hand
1
timeline per incident
5 min
to a first draft review
Opens on its own
Severity comes from the rule that fired, and the right person is paged.
Everything in order
Checks, pages, messages and updates land on a single timeline.
Ready for the review
Export the timeline as a postmortem draft after the fix.
In detail
It opens itself
When two regions agree, an incident opens with the right severity and the right person already paged.
One place for the story
Failed checks, pages, acknowledgements, messages and status updates land in order, each with a timestamp. Anyone joining late can read it from the top and catch up in a minute.
After the fix
A postmortem draft built from the timeline
Time to acknowledge and time to resolve, worked out for you
A shareable link for people who were not on the call
All features
Uptime checks
Every service checked once a minute from six regions.
Incident timeline
One running record from the first failed check to the fix.
Status pages
A public page that updates before customers start asking.
On-call schedules
Fair rotations that everyone on the team can read.
Alert rules
Decide who hears about what, and how loudly.
Response time
Spot the slowdown before it turns into an outage.
