PagerDuty incident

Delays to Escalations and Responder notifications

Minor Resolved View vendor source →

PagerDuty experienced a minor incident on June 10, 2026 affecting Responder Requests (US) (Responder Requests (US)) and Schedules and Escalation Policies (US) (Schedules and Escalation Policies (US)), lasting 45m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2026, 12:47 AM UTC
Resolved
Jun 10, 2026, 01:33 AM UTC
Duration
45m
Detected by Pingoru
Jun 10, 2026, 12:47 AM UTC

Affected components

Responder Requests (US) (Responder Requests (US))Schedules and Escalation Policies (US) (Schedules and Escalation Policies (US))

Update timeline

  1. investigating Jun 10, 2026, 12:47 AM UTC

    We are investigating an incident where PagerDuty customers in the US Service Region are experiencing issues with delays in timed escalations. Impacted customers may see a delay in an incident automatically moving to the next level on an Escalation Policy. Additionally, add responder and status...

  2. investigating Jun 10, 2026, 01:12 AM UTC

    We are monitoring improvements in an incident with delays in timed escalations, add responder notifications, and status update notifications for PagerDuty customers in the US Service Region. We have deployed a fix, and we expect systems to continue to improve. We will provide further updates...

  3. resolved Jun 10, 2026, 01:33 AM UTC

    We have resolved an incident where PagerDuty customers in the US service region experienced issues with delays in timed escalations, add responder notifications, and status update notifications. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to...