PagerDuty Outage History

The PagerDuty incident began at 9:20 AM UTC with an initial investigation into a potential issue. The status page indicated problems with schedule change notifications and affected a broad set of integrations across US and EU regions, potentially impacting alert delivery and escalation workflows.

A follow-up update at 9:50 AM UTC framed the issue as related to schedule change notifications, with the team continuing to investigate. By 10:40 AM UTC the issue was resolved and affected components returned to normal, marking the incident as completed after roughly 1 hour and 20 minutes. The incident included 3 official status updates. Affected areas included multiple integrations such as Slack, Jira Cloud, Microsoft Teams, Zendesk, Incoming Email, and other services across US and EU regions.

PagerDuty reported an investigation into a potential issue at 7:35 PM UTC. A broad set of components across the platform were listed as warn or under investigation, including Integrations, Incident Workflows, Web Application, and Notifications, reflecting widespread but not necessarily service-wide disruption. The status page noted that if an impact was confirmed, updates would follow within 15 minutes. The incident lasted about 3 hours and resolved by 10:35 PM UTC. Two status updates were issued during the incident.

The incident affected PagerDuty's US region email components, specifically Integrations / Incoming Email (US) and Notification Delivery / Email (US). The issue began at 10:40 AM UTC when the status changed from up to warn and lasted for about 1 hour 40 minutes, with the system returning to normal at 12:20 PM UTC. PagerDuty issued two status updates during the event, indicating an active investigation and eventual resolution. The impact appears to be degraded email processing, potentially delaying or interrupting email delivery for integrations and notifications in the US region.

PagerDuty experienced a brief degraded email delivery issue affecting the US region, with two components listed as impacted: Integrations / Incoming Email (US) and Notification Delivery / Email (US). The incident began at 10:25 AM UTC and was resolved by 10:30 AM UTC, lasting about 5 minutes.

The PagerDuty status page noted an investigation into a potential slow email event, followed by restoration to normal operation. The provider issued 2 status updates during the incident to inform users about the affected components.

PagerDuty reported a brief administrative incident affecting the ability to edit teams or delete users in the US and EU service regions. The outage lasted about 30 minutes, beginning at Feb 13, 2026 2:40 PM UTC and ending at Feb 13, 2026 3:10 PM UTC. Affected components were Users and Teams in the US and EU regions. The status page included two updates during the event, after which functionality was restored.

PagerDuty reported a brief potential issue affecting the Incident Workflows (US) component, with the status changing from up to warn starting at Jan 28, 2026 6:55 PM UTC. The incident prompted the PagerDuty status page to indicate investigation of the problem, and two status updates were issued during the event. The issue was cleared and the component returned to normal by Jan 28, 2026 8:15 PM UTC. The incident spanned about 1 hour 20 minutes.

The updates and status transitions show a short-lived potential issue rather than a full outage, and PagerDuty resumed normal operations after the event. The affected component was Incident Workflows (US), and the system appears to have recovered with no lasting impact noted in the updates.

PagerDuty reported an issue affecting the Web Application in the EU region, with users experiencing 500 errors. The outage began at 3:55 PM UTC and was resolved by 4:15 PM UTC, lasting about 20 minutes. The incident prompted two status updates describing the ongoing investigation and subsequent restoration of the EU Web Application.

PagerDuty flagged a potential platform issue across multiple components on Jan 14, 2026 8:05 PM UTC. The status page indicated an ongoing investigation with updates promised if any impact was confirmed, listing a broad set of components across US and EU regions (including Users and Teams, Change Events, Integrations, and Web Applications). The incident lasted about 14 hours and 25 minutes and was resolved by Jan 15, 2026 10:30 AM UTC.

During the event, the PagerDuty status page posted two updates: an initial Investigating Potential Issue and a subsequent resolution. No further details on user-facing impact were provided in the updates, and services returned to normal after the incident was marked resolved.

PagerDuty experienced a partial outage starting at Jan 14, 2026 12:15 AM UTC, with a broad set of services across the platform flagged as potentially impacted. The issue touched many components including Integrations, Schedules and Escalation Policies, Notifications, Web Applications, and incident-management tooling, which could have affected alert delivery, third-party integrations, and related dashboards. The outage persisted for about 6 hours and was resolved by Jan 14, 2026 6:15 AM UTC.

PagerDuty's status page documented an investigation into a potential issue and showed a progression from a warning state back to normal as services recovered. The incident prompted two official status updates, outlining the investigation and eventual resolution as the affected components returned to expected operation.

PagerDuty reported an incident affecting the Slack integration for US customers, causing delays in posting alerts to Slack. The outage began at Jan 9, 2026 9:00 AM UTC and was resolved by Jan 9, 2026 10:40 AM UTC, lasting 1 hour 40 minutes. The provider issued two status updates during the incident as the Slack (US) integration transitioned from down to up.