PagerDuty outage history

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.

PagerDuty experienced a regional issue in the EU where the Analytics Dashboard stopped updating, limiting visibility into analytics data for affected customers. The incident began at 8:00 AM UTC and was resolved by 11:15 AM UTC, lasting about three hours. During the incident, the EU Analytics component moved from up to warn before returning to up, per status updates.

The impact was localized to the EU region, with the Analytics Dashboard in that region being the primary affected component.

PagerDuty experienced an outage affecting SMS and Voice notification delivery for users on the Reliance Jio carrier network in India. While PagerDuty’s platform remained operational, some mobile alerts and voice notifications did not reach recipients on that network. The disruption began at Jul 21, 2026 11:15 PM UTC and persisted through ongoing monitoring.

Updates from PagerDuty described the cause as a carrier-level infrastructure problem outside PagerDuty's control. The affected delivery paths include SMS and Voice, and the status moved through monitoring updates until a recovery was observed by Jul 29, 2026 5:55 PM UTC when the affected components returned to up. A report from Chennai at 11:10 AM UTC noted the PagerDuty site not loading, aligning with the localized disruption. The impact appeared regional to India rather than global.

An issue with PagerDuty's Workflow Automation prevented saving Incident Type triggers when added to an Incident Workflow, impacting automated incident responses for customers across all regions. Users attempting to save new triggers could experience failures, disrupting workflow setup. The incident began at 11:40 AM UTC and was resolved by 1:45 PM UTC.