PagerDuty Outage History

PagerDuty reported a potential issue across a broad set of services and integrations in US and EU regions, prompting an investigation. A large number of components were listed with a warning during the event, suggesting a possible impact on notification delivery, integrations, events processing, and related services. The outage began on Dec 17, 2025 7:25 AM UTC and was resolved by Dec 17, 2025 7:40 AM UTC, lasting about 15 minutes.

During the incident, PagerDuty issued two status updates on their public page: an initial note indicating they were investigating a potential issue, followed by a recovery update as services returned to normal. By the time the incident concluded, affected components across US and EU regions had returned to normal.

PagerDuty reported a potential issue at Dec 15, 2025 9:20 PM UTC that affected a broad set of components across US and EU regions, including Services, Webhooks, Events API, Account Settings, Live Call Routing, Web Application, Mobile Application, and several Integrations. Customers may have experienced degraded performance or intermittent issues across the platform and integrations during this period.

By Dec 15, 2025 9:35 PM UTC, most services had recovered to normal, with only Mobile Application components (US/EU) remaining degraded. The Mobile Apps were fully restored by Dec 15, 2025 10:30 PM UTC. PagerDuty issued three status updates during the incident, and the overall degraded period lasted about 1 hour and 10 minutes.

PagerDuty experienced delays in Incident Workflows in the US region, specifically for actions that run JavaScript steps. This caused slower automated incident responses for some users, while other incident response and notification features continued to function normally.

The outage began at 6:35 PM UTC and was resolved by 8:20 PM UTC, lasting about 1 hour and 45 minutes. The PagerDuty status page published 2 updates during the incident, and the US region component returned to normal operation after the resolution. The effect appeared limited to the US region and did not impact PagerDuty functions outside this region.

PagerDuty experienced an EU-wide issue with notification delivery that affected all customers in the EU Service Region. Users reported delays in alert delivery and, in some cases, notifications not arriving at devices. The outage began on Dec 3, 2025 9:45 PM UTC and was resolved by Dec 4, 2025 12:15 AM UTC, lasting approximately 2 hours and 30 minutes.

On Nov 23, 2025 10:05 PM UTC, PagerDuty moved from Up to Warn with the message Investigating Potential Issue. A broad set of components, including Email, Push, SMS, Web and Mobile Applications, REST API, Analytics, and related incident-management tools, were listed as affected across US and EU regions. The update indicated a potential impact while the issue was investigated, but no confirmed outage was stated at that time. Users may have experienced degraded performance or delays across affected services during the window.

PagerDuty logged a brief investigation starting at Nov 17, 2025 10:10 PM UTC after indicating a potential issue affecting the Runbook Automation component. The incident lasted about 40 minutes, with the Runbook Automation status returning to normal at Nov 17, 2025 10:50 PM UTC. PagerDuty issued 2 status updates during the event, and no confirmed widespread impact was reported.

PagerDuty reported that some customers in the US service region experienced delays in webhook processing, signaling a degraded webhook service. The outage began on 10:15 AM UTC and was resolved by 11:05 AM UTC.

PagerDuty issued 2 status updates during the incident to communicate the issue and its resolution. The disruption was limited to the US region, and affected webhook delivery could impact automations and integrations relying on PagerDuty webhooks.

The incident began at Nov 11, 2025 2:05 PM UTC when PagerDuty flagged a potential issue with the Slack integration experiencing delays. The status page noted an investigation and potential impact to Slack and other integrations across the platform. The disruption lasted about 35 minutes, and users likely observed delays in sending or receiving alerts and notifications via affected channels.

A follow-up update at Nov 11, 2025 2:40 PM UTC indicated restoration and that all components had returned to normal. PagerDuty issued 2 status updates during the incident. The incident affected the Slack integration and multiple other integrations including Email, Jira Cloud, and Microsoft Teams, which were briefly impacted before full recovery.

PagerDuty reported a brief issue affecting the ability to view Past Incident Details for some customers in the United States. The incident began at Nov 7, 2025 3:15 PM UTC and was resolved by 3:40 PM UTC, lasting about 25 minutes. PagerDuty issued 2 status updates during the incident, noting that viewing Past Incident Details was affected and that the service was monitoring and working to restore access. The incident is resolved and US services returned to normal.

The PagerDuty status page reported a potential issue beginning at Nov 4, 2025 1:25 PM UTC, prompting an investigation that affected multiple core components across US and EU regions. During the investigation, users may have experienced intermittent issues or degraded capability as PagerDuty assessed whether there was an actual impact across services such as incident management, notifications, and integrations.

At Nov 4, 2025 3:10 PM UTC PagerDuty indicated the issue had been resolved and all listed components returned to normal. The incident lasted approximately 1 hour and 45 minutes, with updates describing recovery of services from the warn state back to up across affected areas, including incident workflows, notification delivery, and integrations like Jira, Slack, and Webhooks.