PagerDuty Outage History

PagerDuty reported a brief investigation into a potential issue, with a broad set of internal components across US and EU flagged as warning during the event. The incident began at Oct 28, 2025 4:30 PM UTC and lasted about 30 minutes, ending at Oct 28, 2025 5:00 PM UTC. No user reports were observed, and PagerDuty indicated that if there were confirmed impacts they would provide updates within 15 minutes. The company issued 2 status updates during the incident. All affected components returned to normal after the event.

PagerDuty experienced a brief potential issue starting at 2:50 AM UTC, with the status page indicating Investigating Potential Issue and a broad set of components entering a degraded state (warn) across US and EU regions. The incident appeared to affect a wide range of PagerDuty services and integrations, including Runbook Automation, Incident Timeline and Alert Logs, Services, Notification Delivery, Email, Slack, Jira Cloud, Zendesk, REST API, and more. The outage lasted about 5 minutes and was resolved by 2:55 AM UTC.

During the incident, two status updates were published by PagerDuty as the issue was investigated and then resolved. No user reports were recorded during the event.

An incident began at Oct 20, 2025 7:25 AM UTC with delayed notifications in PagerDuty's US region. The issue then expanded to affect Workflow Automations, causing lists to fail to load and new automation runs to fail to start. Across US and EU components, users experienced degraded notification delivery and disrupted automation workflows for an extended period, with the outage lasting roughly 22 hours and 35 minutes until the affected components were returned to normal by Oct 21, 2025 6:00 AM UTC.

PagerDuty flagged a potential issue at Oct 19, 2025 2:30 PM UTC and began investigating across multiple components. The incident appeared to affect dozens of PagerDuty services and integrations across US and EU regions, with the status page noting an ongoing investigation and no confirmed impact at that time.

The issue was resolved about 20 minutes later, with status restored to normal at Oct 19, 2025 2:50 PM UTC. PagerDuty issued two status updates during the incident, describing the investigation and subsequent recovery. The incident involved a broad set of services, including Runbook Automation, REST API, Slack, Email, Jira Cloud, Zendesk, and Live Call Routing, among others.

PagerDuty experienced a brief investigation into a potential issue affecting a broad set of services across US and EU regions. Users may have encountered degraded alert delivery and related functionality during the incident window. The impact referenced multiple components including Incident Timeline and Alert Logs, Notification Delivery, Email, Push, Slack, and Microsoft Teams, among others.

The incident lasted about 1 hour and 20 minutes, beginning at Oct 15, 2025 10:15 PM UTC and resolving by Oct 15, 2025 11:35 PM UTC. PagerDuty issued two status updates during the event: the initial update indicated an investigation, and the subsequent update confirmed resolution and a return to normal service. The issues affected services across US and EU regions, with components returning to an unchanged state after remediation.

PagerDuty experienced a brief outage beginning at 4:40 PM UTC with an initial investigation into a potential issue. The incident affected a broad set of components across US and EU regions, including Services, REST API, Email, Push, Slack, and other integrations, causing degraded performance or partial outages for some users. The outage lasted about 35 minutes and was resolved by 5:15 PM UTC. The PagerDuty status page provided updates as the issue was assessed and resolved, with two official status updates during the incident.

On Oct 14, 2025 9:40 PM UTC PagerDuty reported Investigating Potential Issue as a broad set of components across the US and EU showed degraded signals. The status page indicated a potential impact across Workflow Automation, Incident Timeline and Alert Logs, Services, Notification Delivery, and Login/SSO, with many integrations like Jira Cloud, Slack, Microsoft Teams, and others affected. Users likely experienced delays or partial outages in alerting, incident management, and related services during the incident.

By 11:45 PM UTC the status page indicated the issue had been resolved and the affected components returned to normal. The outage lasted approximately 2 hours and 5 minutes, with the incident spanning US and EU regions.

The incident began at Sep 24, 2025 10:10 AM UTC when PagerDuty announced investigations into reports of slowness. A follow-up at Sep 24, 2025 11:05 AM UTC noted performance issues affecting the Web UI and a broad set of components across US and EU regions.

PagerDuty reported a brief investigation into a potential issue that affected a broad set of components across US and EU. Dozens of PagerDuty services appeared degraded (warn) during the event, including Notification Delivery, REST API, Jira Cloud, Slack, Microsoft Teams, and other integrations. The incident began at Sep 12, 2025 2:30 PM UTC and was resolved by Sep 12, 2025 2:55 PM UTC as the status returned to up. The provider issued two official updates during the incident, announcing the investigation and later confirming recovery.

PagerDuty announced an investigation into a potential issue at Sep 2, 2025 4:20 PM UTC, listing a broad set of components that could be affected. The issue appeared to impact a wide range of PagerDuty services and integrations, including Voice, the REST API, Notification Delivery, and popular third‑party tools such as Slack, Jira Cloud, and Microsoft Teams. User reports were minimal, indicating limited observable impact. The incident lasted approximately 2 hours and 10 minutes, with services returning to normal by Sep 2, 2025 6:30 PM UTC.

PagerDuty posted two status updates during the incident, the first at Sep 2, 2025 4:20 PM UTC and the second at Sep 2, 2025 6:30 PM UTC. The updates described the ongoing investigation and later the restoration of services. The root cause and full scope were not disclosed in the updates.