Incident management from detection to postmortem

From a confirmed outage to an open incident — automatically

The slowest part of an incident is often the start: noticing, confirming, and getting everyone looking at the same thing. PingInsight closes that gap. When a monitor's failure clears multi-location quorum and the consecutive-failure threshold, it can open an incident automatically — no one has to be watching a dashboard for the response to begin.

Because detection is built on the 1-second engine and millisecond-stamped probes, the incident starts with an accurate start time instead of a rounded guess, which makes everything downstream — duration, communication, and the eventual postmortem — more trustworthy.

The incident lifecycle: Investigating → Identified → Monitoring → Resolved

Every incident moves through a clear, familiar lifecycle that customers and stakeholders already understand. Investigating means you know something is wrong and are looking into it. Identified means you've found the cause. Monitoring means a fix is in place and you're watching to confirm it holds. Resolved means it's over.

Each status change is posted as a timeline update that flows straight onto your status page and out to subscribers, so the people affected always see exactly where things stand without having to ask.

Auto-resolve with the exact duration

When the underlying monitor recovers, PingInsight can resolve the incident automatically and stamp it with the exact downtime — derived from the same millisecond-precise probe data that detected the outage. Instead of an approximate “about ten minutes,” the record shows the real interval, which is what you want for SLO reporting, customer communication, and an honest postmortem.

Postmortems that close the loop

Resolving an incident isn't the end of the work. Every incident can carry a written postmortem so the team captures what happened, why, and what changes prevent a repeat. Keeping the timeline and the postmortem together — with accurate timestamps already filled in — turns each incident into a durable record you can learn from rather than a Slack thread that scrolls away.

Escalations and on-call rotations (Business and above)

Detection only helps if the right person actually responds. On Business and above, PingInsight runs ordered escalation policies — if the first responder doesn't acknowledge in time, the alert escalates to the next step — and timezone-aware on-call rotations with overrides for holidays and hand-offs. Alerts reach your team through any of eleven channels: email, Slack, Discord, Telegram, Microsoft Teams, PagerDuty, Google Chat, ntfy, Mattermost, Rocket.Chat, and signed webhooks.

Scheduled maintenance windows

Planned work shouldn't look like an outage or page your on-call. Schedule a maintenance window in advance and PingInsight pre-notifies your subscribers, displays the window on your status page, and suppresses alerts for the affected monitors while it's active — so expected downtime stays expected and your alert history stays clean.