PagerDuty incident

Investigating Potential Issue with Phone Notifications

Minor Resolved View vendor source →

PagerDuty experienced a minor incident on March 21, 2026, lasting 34m. The incident has been resolved; the full update timeline is below.

Started
Mar 21, 2026, 06:25 PM UTC
Resolved
Mar 21, 2026, 06:59 PM UTC
Duration
34m
Detected by Pingoru
Mar 21, 2026, 06:25 PM UTC

Update timeline

  1. identified Mar 21, 2026, 06:25 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Mar 21, 2026, 06:38 PM UTC

    We are investigating an issue within PagerDuty impacting call/voice notifications in the US Service region. All core PagerDuty functionality, including API-based event ingestion, event orchestration, incident creation, email notifications and Push/SMS notifications, remain fully operational. We...

  3. investigating Mar 21, 2026, 06:52 PM UTC

    We are continuing to investigate an issue within PagerDuty impacting call/voice notifications in the US Service region; this issue impacts a small number of PagerDuty customers. All core PagerDuty functionality, including API-based event ingestion, event orchestration, incident creation, email...

  4. resolved Mar 21, 2026, 06:59 PM UTC

    We have resolved an issue within PagerDuty impacting call/voice notifications in the US Service region; this issue impacted a small number of PagerDuty customers. All core PagerDuty functionality, including API-based event ingestion, event orchestration, incident creation, email notifications and...