Incidents
When something breaks, you get the whole story
An incident opens only when several regions agree a monitor is down. From there you get a full event timeline, and you acknowledge and resolve it by hand or let it auto-resolve on recovery.
Full event timeline
Every change is on the timeline — open, acknowledge, resolve — with timestamps and the person behind each.
Acknowledge and resolve
Ack to stop escalation. Resolve by hand, or let it auto-resolve once the target recovers.
No false alarms
Multi-region consensus and maintenance windows keep blips and planned work from paging you.
Feeds your status page
Resolved incidents roll up into the 90-day history on your status page automatically, so customers see an honest track record.
Lifecycle
Opened on agreement.
Resolved on recovery.
Consensus decides when an incident is real. You decide when it is handled. Everything in between is on the timeline.
Opens on consensus
An incident opens only when several regions agree the monitor is down, so a single network blip never pages you.
Acknowledge it
Ack from the dashboard. Acknowledging stops the escalation clock immediately.
Resolve it
Resolve by hand, or let it auto-resolve once the regions report the target healthy again.
Review what happened
Every open, acknowledge, and resolve stays on the timeline with timestamps and the actor, so reviewing the incident afterward is just reading the record.