PagerDuty incident

Issue Identified calling the Schedules API

Minor Resolved View vendor source →

PagerDuty experienced a minor incident on June 3, 2026 affecting REST API (US) (REST API (US)) and REST API (EU) (REST API (EU)), lasting 30m. The incident has been resolved; the full update timeline is below.

Started
Jun 03, 2026, 01:48 PM UTC
Resolved
Jun 03, 2026, 02:18 PM UTC
Duration
30m
Detected by Pingoru
Jun 03, 2026, 01:48 PM UTC

Affected components

REST API (US) (REST API (US))REST API (EU) (REST API (EU))

Update timeline

  1. investigating Jun 03, 2026, 01:48 PM UTC

    We are investigating an incident where some PagerDuty customers in the EU Service Region are experiencing issues with the schedules API. Impacted customers may see 401 unauthorised errors when querying the schedules API. Event ingestion and incident notification delivery are not affected. We will...

  2. investigating Jun 03, 2026, 02:14 PM UTC

    We are monitoring improvement in an incident with the Schedules API. We have deployed a fix, and we expect systems to continue to improve; Mobile and Web UIs were not impacted. Event ingestion and incident notification delivery are not affected. We will provide an update within the next 15...

  3. resolved Jun 03, 2026, 02:18 PM UTC

    We have resolved an incident with the Schedules API. We have deployed a fix, and we expect systems to continue to improve; Mobile and Web UIs were not impacted. Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact to...