Every incident, with the evidence attached
Incidents open and resolve off monitor state. Each one carries the region timeline, the captured request and response with secrets redacted, and a traceroute with a plain-language read on where the loss begins.
#4821 P1 acknowledged by danaExample of what this check records. Real data appears in the dashboard.
How it works
It opens itself
When the regions agree the monitor is down.
You act
Acknowledge, set priority, add notes, resolve by hand when you must, hide it from the public page.
It closes itself
When the monitor recovers, with PagerDuty and subscribers told.
What you can set
| Setting | Options |
|---|---|
| Diagnostics | Per-region events, request and response capture (cookies and tokens redacted), traceroute and analysis |
| Controls | Acknowledge, priority, notes, manual resolve, hide from public |
| Storm grouping | More than five opens in a minute collapse into one summary per contact |
Pairs well with
Join the waiting list
We open gostatus to a few teams at a time. Leave your email and we will write when it is your turn.
Join the waiting list