PagerDuty paging for confirmed outages
Send confirmed outages to PagerDuty using an Events API v2 routing key. PingInsight triggers an incident when quorum confirms a monitor is down and resolves it automatically on recovery — so your existing on-call rotations and escalation policies take over without anyone touching PingInsight. Deduplication keys keep a single ongoing outage as one PagerDuty incident rather than a storm of pages.
Set up in minutes
In-app path: Alerting → Channels → Add channel → PagerDuty
- 1.Create an Events API v2 integration on a PagerDuty service and copy the routing key.
- 2.Add a PagerDuty channel under Alerting and paste the routing key.
- 3.Attach it to the monitors you want to page on.
- 4.Send a test alert to confirm an incident triggers and resolves.
What you can do
- ✓Page on-call through PagerDuty for high-severity outages
- ✓Auto-resolve PagerDuty incidents when service recovers
- ✓Let PagerDuty's escalation policies route the alert
- ✓Keep monitoring and paging in the tools you already run
A sample PagerDuty alert
!PingInsight→ PagerDutynow
PagerDuty incident triggered Title: api.example.com is DOWN Severity: critical Source: PingInsight (HTTP check) Details: HTTP 503 · confirmed by 2 of 3 regions → auto-resolves when the monitor recovers
Exact formatting varies by PagerDuty; the live alert includes the monitor, confirming regions, and the precise downtime on recovery.
Frequently asked questions
- Why didn't a PagerDuty incident trigger?
- Confirm you pasted an Events API v2 routing key (not an older integration key) and that it belongs to an active PagerDuty service with an escalation policy attached. PingInsight only pages on confirmed outages, so a single-region blip that never reaches quorum won't trigger one.
- Will PagerDuty incidents resolve on their own?
- Yes. PingInsight sends a resolve event with the same deduplication key when the monitor recovers, so the matching PagerDuty incident closes automatically and the recovery shows the exact downtime. No manual cleanup is needed.
- Should I use PagerDuty's escalations or PingInsight's?
- Pick one owner for paging logic to avoid double-paging. If PagerDuty is your system of record, route to it and let its escalation policies and on-call schedules do the work; reserve PingInsight's built-in escalations (Business and above) for channels like email or chat.
See all alerting integrations or read about incident management.
Start monitoring in under a minute
Free forever, no credit card. Upgrade when you need finer intervals.