Opened and closed automatically
Confirmed failures open an incident; confirmed recoveries close it. Nobody has to remember to update the status page while they’re busy fixing the actual problem.
Incident Management
A confirmed failure opens an incident with the facts already in it: what, since when, and from where. You add the human part. Recovery closes it.
Included on every plan. Nothing here is an add-on.
Incident · INC-0418
Checkout Service degraded: p95 512 ms over the 400 ms threshold. Confirmed from NYC and Frankfurt.
Slow query on the orders table after this morning’s migration. Rolling back the index change.
Rollback complete. p95 back under 150 ms from all regions; watching for 20 minutes.
Checkout Service recovered. Total duration 40 minutes.
Confirmed failures open an incident; confirmed recoveries close it. Nobody has to remember to update the status page while they’re busy fixing the actual problem.
Investigating, Identified, Monitoring and Resolved, with templates for the updates you end up writing over and over. Optional postmortems publish alongside the incident.
For what monitors can’t see: a partner outage, a data issue, a bad deploy caught by hand. Same timeline, same subscriber updates.
Scheduled windows notify subscribers, silence alerts for the duration, and are excluded from uptime history, so planned work doesn’t look like downtime.
Partial degradation
Checkout is slower than usual. Investigating · updated 4 min ago
Every part of StatusCheck is on every plan. These are the pieces this one talks to most.
StatusCheck opens in batches. Join the waitlist and we’ll email you once, when it’s your turn. The free plan needs no card.