Does Nodown resolve PagerDuty incidents automatically?

Yes. When a monitor recovers, Nodown sends a RESOLVE event to PagerDuty using the same dedup key as the original trigger. The incident closes automatically without manual action.

Can I use Nodown with PagerDuty's free plan?

Yes, as long as your PagerDuty account supports Events API v2. The free PagerDuty developer plan includes this. Check your PagerDuty plan for team and service limits.

Will I get duplicate incidents if multiple regions detect the same failure?

No. Nodown only sends one incident trigger per failure event, using a dedup key tied to the monitor ID. Subsequent failed checks during the same incident do not create new incidents.

All integrations

Nodown + PagerDuty

Route Nodown incidents to your PagerDuty on-call rotation.

Connect PagerDuty free View pricing

Free to start · No credit card required

What an alert looks like

PagerDuty alert

TRIGGER | api.yourapp.com is DOWN
Service: Production API
Severity: critical
Body: 503 Service Unavailable — 4 regions confirming
Dedup key: nodown-monitor-abc123

Why teams use Nodown with PagerDuty

Nodown integrates with PagerDuty to create, resolve, and update incidents automatically. When a monitor fails, an incident opens in PagerDuty and pages your on-call engineer through your existing escalation policy.

Automatic incident lifecycle

Nodown opens a PagerDuty incident on failure and resolves it automatically when the monitor recovers — no manual intervention required.

Uses your existing escalation policy

Incidents route through whatever on-call policy you have configured in PagerDuty — rotations, escalations, and acknowledgement flows all work as normal.

Deduplication built-in

Nodown sends a dedup key with every incident so repeated failure checks do not create duplicate PagerDuty incidents during an ongoing outage.

Severity mapping

Map Nodown alert types to PagerDuty severity levels. Set production monitors to critical, secondary monitors to warning.

How to connect PagerDuty to Nodown

Set up takes about 2 minutes. No code required.

1

Create a PagerDuty integration key

In PagerDuty, open the service you want Nodown to trigger incidents on. Go to Integrations → Add Integration → Events API v2. Copy the Integration Key.
2

Add the integration in Nodown

Go to Alerting → Integrations → New Integration → PagerDuty. Paste the Integration Key, name the integration, and click Test to verify the connection.
3

Assign to critical monitors

Open your production monitors, add the PagerDuty integration under Alert Channels. PagerDuty is typically combined with Slack — Slack for team visibility, PagerDuty for on-call paging.

Get started free

Frequently asked questions

Does Nodown resolve PagerDuty incidents automatically?: Yes. When a monitor recovers, Nodown sends a RESOLVE event to PagerDuty using the same dedup key as the original trigger. The incident closes automatically without manual action.
Can I use Nodown with PagerDuty's free plan?: Yes, as long as your PagerDuty account supports Events API v2. The free PagerDuty developer plan includes this. Check your PagerDuty plan for team and service limits.
Will I get duplicate incidents if multiple regions detect the same failure?: No. Nodown only sends one incident trigger per failure event, using a dedup key tied to the monitor ID. Subsequent failed checks during the same incident do not create new incidents.