Trigger an incident
A trigger event goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with PagerDuty.
One integration key, and a confirmed outage opens an incident that follows your escalation policy and closes itself when the site is back.
What lands in PagerDuty
Everything the alert pipeline sends into PagerDuty is on this list, and nothing beyond it. Read it once and you know what your team will see.
Resolve it automatically
The recovery sends a resolve event for the same incident, so nobody has to close a page for a site that is already back.
Speak Events API v2
Every event goes to the fixed enqueue endpoint in the schema PagerDuty documents, with no webhook body template in between.
Deduplicate by incident
A stable dedup key per incident means a repeated event updates the incident you already have instead of opening a second one.
Set the severity
A warning arrives as warning and an outage as critical, so your urgency rules can tell the two apart without reading the text.
Pass the details along
Status code, response time, customer, your custom fields and the link to the screenshot ride along in the custom details of the event.
A service per monitor
Each channel carries its own routing key, so a client's outage opens on the service that client's team is on call for.
Send a test event
The dashboard fires a test event while you set it up, so a mistyped integration key is caught before the first real page.
Keep the routing key encrypted
The integration key is stored encrypted rather than as plain text in the channel configuration.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Add the integration to a service
In PagerDuty open the service that should receive the incidents, go to Integrations and add one.
Routing key
R0123456789ABCDEF0123456789ABCDStored encrypted
2. Pick Events API v2 and copy the key
Choose Events API v2 as the integration type and copy the integration key it generates.
3. Paste it into Uptimeify
Add the key as a PagerDuty channel, assign the monitors it covers, and send the test event.
Before you connect PagerDuty.
Yes. The recovery sends a resolve event carrying the same dedup key as the trigger, so PagerDuty closes the incident it opened rather than leaving a stale page behind.
No. The dedup key is per incident, so repeated events land on the one incident. How many re-checks it takes before an outage counts as confirmed is yours to set per package.
Yes. Every channel carries its own routing key, and you assign monitors and clients to it. A client's outage then opens on the service that client's team is on call for.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over PagerDuty, email, webhook or Slack do not draw on it.
The delivery is retried on its own ladder, and each attempt lands on the Alerts tab under History & Logs, so a key that quietly stopped working is visible instead of just silent.
Every alert, where your team already works.
Connect PagerDuty once, and every confirmed outage opens an incident that resolves itself when the site is back.