Downtime that pages
the right person.
When you already run on-call through PagerDuty, your uptime checks should feed it. UptimeClaw triggers a PagerDuty incident the moment a monitor fails — so your existing rotation, escalation policy, and SLAs take over automatically.
Let your escalation policy do its job.
Chat alerts are great for visibility, but accountability needs structure: who's on call, who gets escalated to if they don't ack, and what the SLA clock says. That's PagerDuty's job. UptimeClaw's role is to hand it a clean, accurate trigger — a real incident when the site is genuinely down, and an automatic resolve when it recovers, so on-call isn't left closing stale pages.
- Trigger a PagerDuty incident on downtime
- Auto-resolve the incident on recovery
- Monitor detail (status, region, response time) in the incident
- Pair with WhatsApp/Slack for parallel visibility
PagerDuty alerts FAQ
Does it resolve incidents automatically?
Yes — when the monitor recovers, UptimeClaw resolves the PagerDuty incident, so on-call isn't stuck closing pages by hand.
Will my escalation policy still apply?
Yes. UptimeClaw triggers the incident; PagerDuty handles on-call routing, acknowledgements, and escalation exactly as you've configured them.
Can I also get a WhatsApp or Slack alert?
Yes — run PagerDuty for accountability and WhatsApp/Slack for immediate human visibility, in parallel or as an escalation order.
Hand outages
to your on-call.
Trigger and auto-resolve PagerDuty incidents from your monitors. Free to start.