PagerDuty outage history

PagerDuty experienced a brief outage in incident notification delivery that prevented alerts from reaching users through Email (US), Voice (US), SMS (US), and Push (US) channels. The issue was first noted as an investigation at Oct 23, 2026 10:36 PM UTC, then escalated to a partial outage by 10:50 PM UTC, affecting on-call responders who rely on timely notifications. All affected channels were restored by 11:10 PM UTC, with the incident lasting roughly 34 minutes as visibility and status were updated on PagerDuty’s page.

PagerDuty faced a partial outage affecting notification delivery across multiple channels in the US, including Voice, Email, SMS, and Push, and it also impacted integrations with Microsoft Teams and Slack, as well as the Web Application and related status tools. The incident began when the Notification Delivery components were first listed as degraded at 9:40 PM UTC, and the impact expanded to the Incident Timeline and Alert Logs, Status Page, and other services as teams depended on alerts.

By 11:25 PM UTC, the service returned to normal, with all affected components moving back to an up state. PagerDuty's status updates documented the investigation and subsequent restoration, indicating notification delivery had resumed across Voice, Email, SMS, Push, and the affected integrations.

PagerDuty experienced a regional disruption in the US Service Region that affected escalation of incidents and the sending of responder invitations. While event ingestion and incident notification delivery remained functional, on‑call responders could take longer to be escalated to and invited to incidents. The impact began at 3:10 PM UTC and was resolved by 3:25 PM UTC. The PagerDuty status page described the issue as 'Issue Identified - Delayed escalation of incidents and responder request invitations' and indicated that the team was investigating before returning to normal operations.

Users in PagerDuty's US service region experienced a brief disruption affecting event ingestion and notification delivery. Affected components included the Events API, Web Application, REST API, Incident Workflows, and multiple notification channels (Voice, Email, SMS, Push). Users may have encountered issues creating incidents, attaching alerts, acknowledging incidents, or using the web UI and Ops Console. The outage began at 1:25 AM UTC and was resolved by 1:40 AM UTC, lasting about 15 minutes.

PagerDuty's status page indicated that the issue was identified and remediation followed with services returning to normal by 1:40 AM UTC, with the impact confined to the US region.

Users across PagerDuty service regions experienced delays in Incident Workflows, with latency observed when running JavaScript actions within workflows. Event ingestion and incident notification delivery themselves were not affected.

The issue began at Sep 25, 2026 1:40 PM UTC and was resolved by Sep 25, 2026 3:00 PM UTC, with the problem affecting US and EU regions. PagerDuty's updates indicated the investigation and subsequent recovery to normal operations.

Users in the US service region may have experienced 500 errors when using PagerDuty's MCP, while event ingestion and incident notification delivery remained unaffected. The incident began at 4:05 PM UTC and centered on the PagerDuty Advance component. The service returned to normal after about an hour, with MCP operations restored by 5:00 PM UTC.

PagerDuty experienced a brief degradation in Event Processing for the US region, affecting the Events API (US). The incident began at 2:36 PM UTC with PagerDuty’s status page indicating an active investigation into an issue impacting event processing in the US region. The incident lasted about 35 minutes before the Events API (US) returned to normal, with service restored by 3:10 PM UTC. Updates confirmed the issue and subsequent recovery, though specific user impact details were not provided.

Users signing in to PagerDuty’s Web Application in the US and EU saw an erroneous login banner stating that their notifications were paused. The message was inaccurate and caused confusion, but did not indicate a broader outage of PagerDuty services. The issue began at 8:01 AM UTC and was resolved by 8:15 AM UTC as the banner was corrected and normal operation resumed.

PagerDuty reported a brief degradation affecting Incident Workflows for some customers in the US service region. Users may have seen Incident Workflows fail to start or complete, while event ingestion and incident notification delivery remained unaffected. The disruption began at 10:25 PM UTC and was resolved by 11:30 PM UTC, impacting Incident Workflows / Incident Workflows (US) and PagerDuty Advance.

Status page updates described an ongoing investigation into Incident Workflows and the SRE Agent Connector in the US region, with PagerDuty Advance also impacted. By the end of the window, the affected components returned to normal and services were restored.

PagerDuty reported a brief degradation in the ability to post new incidents to external status pages, impacting the Status Page / External Status Page components in the US and EU. Users attempting to publish updates to their external pages may have seen errors or delays. The incident began at 5:25 AM UTC and was resolved by 5:35 AM UTC after engineers investigated and remediation completed.