PagerDuty Outage History

The outage began on 2:10 PM UTC and was resolved by 2:55 PM UTC. PagerDuty announced it was investigating a potential issue at the start time, which affected dozens of components and integrations, including Voice, Services, Email, Push notifications, Slack, Jira Cloud, and more, leading to degraded performance and intermittent issues with alerting, notification delivery, and incident workflows. The incident lasted about 45 minutes. The provider issued 2 status updates during the incident to communicate the investigation and resolution.

PagerDuty experienced a multi-service incident beginning at 4:50 PM UTC that caused degraded notification delivery and incident-management capabilities across dozens of components and integrations, including Incident Timeline and Alert Logs, Services, Notification Delivery, Email, Slack, Microsoft Teams, Jira Cloud, REST API, and Webhooks. Users likely saw delays or gaps in alerts, incident updates, and automated workflows during this period. The outage lasted approximately 3 hours and 35 minutes.

PagerDuty experienced a degraded alerting incident that affected notification pipelines across the platform. Users reported not receiving alerts, the Events API was down, and some pages failed to reach downstream integrations. The issue impacted multiple notification channels including Email, Slack, SMS, Push, Webhooks, and Teams, and affected core incident tooling. The outage began at Aug 28, 2025 4:05 AM UTC and was resolved by Aug 28, 2025 10:20 AM UTC, lasting approximately 6 hours and 15 minutes.

The provider issued 2 status updates during the incident. Based on user reports, the disruption appeared broad and global, with affected users across multiple regions experiencing delayed or missing alerting.

The Microsoft Teams (US) integration with PagerDuty experienced a brief degraded state beginning at 2:30 PM UTC when PagerDuty announced it was investigating a potential issue. The issue affected the Teams channel, potentially delaying or interrupting PagerDuty notifications delivered to Teams. The incident lasted about 35 minutes and was resolved by 3:05 PM UTC.

The incident was communicated via the PagerDuty status page, with two updates during the event: one noting an investigation and another confirming the Teams integration returned to full operation at 3:05 PM UTC.

PagerDuty experienced a brief potential issue that triggered a broad investigation across multiple components. The status page indicated an investigation began at Aug 7, 2025 4:10 PM UTC and was resolved about 25 minutes later, with all services returned to normal by Aug 7, 2025 4:35 PM UTC.

The incident involved a broad set of subsystems across US and EU regions, and PagerDuty issued two status updates during the event. No confirmed user impact was reported.

PagerDuty Web Applications (EU and US), Mobile Applications (US and EU), and Incident Workflows (US) experienced degraded performance beginning at 03:50 UTC. Users across US and EU regions faced intermittent access and delays when using dashboards, alerts, and incident response tools. The outage began on Jul 24, 2025 3:50 AM UTC and was resolved by Jul 24, 2025 5:40 AM UTC. The provider issued four status updates during the incident, starting with an investigation and concluding with restoration of all affected components.

PagerDuty reported a brief potential issue affecting a broad set of components across US and EU regions. The incident began at 7:00 PM UTC and was resolved by 7:15 PM UTC, lasting about 15 minutes. The status page showed an Investigating Potential Issue update and then returned to normal, with the incident affecting multiple components including Email, Analytics, Login and SSO, Incident Timeline and Alert Logs, Services, and Push among others. The PagerDuty team issued 2 status updates during the incident, and services were restored promptly.

PagerDuty briefly flagged a potential issue on its status page. The incident began at Jul 21, 2025 8:05 AM UTC when the page indicated Investigating Potential Issue, and it was resolved by Jul 21, 2025 9:20 AM UTC about 1 hour 15 minutes later, with the status returning to normal. There was no described impact to customers or services during the event.

PagerDuty experienced a brief degraded performance affecting numerous components across US and EU regions. The incident began on Jul 11, 2025 5:00 PM UTC and was resolved by Jul 11, 2025 5:40 PM UTC, lasting about 40 minutes. PagerDuty issued 2 status updates during the event, noting an investigation into a potential issue and later restoration of services. Impact included components such as Account Settings, REST API, Webhooks, Push, Log In and SSO, Analytics, Incident Timeline and Alert Logs, and integrations with Jira Cloud, Slack, Email, and other services, with users reporting interruptions to incident management workflows and notifications.

PagerDuty experienced a brief degraded performance event beginning at Jul 1, 2025 4:20 PM UTC, affecting a broad set of components in the US and EU. The incident listed multiple components as degraded, including Incident Timeline and Alert Logs, Services, Notification Delivery, and various integrations, which could have caused intermittent alerting and workflow delays for users. The outage lasted approximately 20 minutes and was resolved by Jul 1, 2025 4:40 PM UTC.

During the incident, PagerDuty issued 2 status updates, and all components returned to the normal state by the end of the event.