Turn downtime into a PagerDuty incident automatically
UptimeEye opens a PagerDuty incident the moment a check fails and resolves it the moment the service recovers — so your on-call rotation only gets paged for things that are real.
No credit card · Free tier · Commercial use allowed
Auto-open, auto-resolve
A verified failure triggers an incident; recovery resolves the same incident automatically via its dedup key. No stale pages left open.
Only real incidents page someone
Multi-region confirmation runs before the trigger fires, so your rotation isn't woken by a single flaky check.
Included, not an enterprise upsell
The PagerDuty integration works on every plan, including Free — no separate 'incident management' tier to unlock it.
How to set up PagerDuty alerts
What you'll need: A PagerDuty service · An Events API v2 integration (routing) key
- 1
Add an Events API v2 integration in PagerDuty
In PagerDuty, open your service → Integrations → Add integration, choose “Events API v2”, and copy the Integration (routing) Key.
- 2
Paste the routing key into UptimeEye
In UptimeEye, open Notifications → New channel → PagerDuty and paste the Integration Key.
- 3
Attach it to what you monitor
Add the channel to any monitor, cron job, SSL check, or status page — on every plan, including Free. Send a test alert to confirm it lands where your team actually looks.
What triggers a PagerDuty alert
Downtime & recovery
When a monitored website, API, or server goes down — confirmed from multiple regions — and again the moment it recovers.
SSL & domain expiry
Early warnings before a TLS certificate or domain expires, so you renew before it takes the site offline.
Cron & scheduled-task failures
Dead Man's Switch alerts when a scheduled job fails or misses its window, so silent background jobs never rot unnoticed.
Ways teams use it
- Page the on-call engineer the instant a production endpoint fails, then auto-resolve when it's back.
- Escalate a missed cron job (dead man's switch) so a silent nightly job never rots unnoticed.
- Route SSL-expiry warnings to a low-urgency service so certs get renewed before they page anyone.
PagerDuty monitoring FAQ
Do incidents resolve on their own?
Yes. UptimeEye sends a resolve event with the same dedup key when the monitor recovers, so the PagerDuty incident closes automatically instead of lingering.
Which key do I need — API token or routing key?
The Events API v2 Integration Key (also called the routing key) from a service integration. You do not need a global PagerDuty API token.
Is PagerDuty limited to paid plans?
No. Like every notification channel in UptimeEye, PagerDuty is available on every plan, including the free tier.
Will flapping create a flood of incidents?
Failures are confirmed from multiple regions first, and recovery resolves the existing incident rather than opening a new one, which keeps flapping from spamming your rotation.