PagerDuty Outage History

PagerDuty briefly listed Runbook Automation as a potential issue, triggering a short warning on the status page. The incident began at Jun 24, 2025 10:40 PM UTC and was resolved by Jun 24, 2025 10:55 PM UTC, lasting about 15 minutes. PagerDuty stated they were investigating a potential impact and would update if there was confirmed disruption. There were no reported user impacts, and Runbook Automation returned to full operation after the brief warning. The status page issued two updates during the incident, and the issue was contained to the Runbook Automation component without broader effects.

PagerDuty reported a brief incident beginning at 8:50 PM UTC with an investigation into a potential issue affecting a broad set of components across regions. The issue was later identified as related to Schedule Overrides, with updates noting potential impact on alert delivery and integrations. The incident did not result in a full outage, but users may have experienced degraded alerting and intermittent service impact during the window. By 9:10 PM UTC, all components had returned to normal and the status page indicated a resolution. The incident included two official status updates during its duration.

PagerDuty's status page showed an investigation into a potential issue affecting the Schedules and Escalation Policies (US). The incident began at Jun 11, 2025 9:45 PM UTC and lasted about 35 minutes, resolving when the status returned to up at Jun 11, 2025 10:20 PM UTC. The page indicated an investigation into a potential impact; no confirmed customer impact was disclosed, and the US component briefly moved to a warning before returning to normal. A total of two official status updates were logged during the event.

PagerDuty's Jeli component experienced a brief outage that prevented users from editing and/or creating Jeli opportunities. The incident began at 5:25 PM UTC and was resolved about 10 minutes later at 5:35 PM UTC. There were no broader service impacts indicated beyond Jeli during this window.

The provider posted two status updates during the incident, first noting an issue with Jeli and that investigations were underway, and later confirming restoration of the Jeli functionality.

PagerDuty experienced a brief degraded state beginning at 9:15 PM UTC when the status page flagged Investigating Potential Issue. A broad set of components across the US and EU were listed as affected, including Services, Notification Delivery, Incident Timeline and Alert Logs, Runbook Automation, and related features. The incident lasted about 30 minutes and all components returned to normal by 9:45 PM UTC.

During the event, PagerDuty issued two status updates outlining the investigation and subsequent restoration of services. The outage indicated a partial disruption across multiple PagerDuty functions, which was resolved within the half-hour window as systems recovered to their standard operational state.

PagerDuty experienced webhook delivery issues affecting a broad set of integrations. Users relying on PagerDuty for notifications and automations may have encountered delays or incomplete alerts across services like Slack, Jira, Zendesk, REST API, and other integrations. The incident began at May 30, 2025 6:55 PM UTC and was resolved by May 30, 2025 7:40 PM UTC, lasting about 45 minutes.

The PagerDuty status page logged two updates during the incident, acknowledging Webhook Delivery Issues and indicating investigations, followed by a resolution as components returned to normal.

PagerDuty reported a potential issue affecting a broad set of its components across the US and EU, including Responder Requests, Services, Incident Timeline and Alert Logs, Notification Delivery, Log In and SSO, and multiple integrations. Users could have experienced interruptions or degraded functionality related to alerting, incident management, and authentication during the event.

The incident began at 4:45 PM UTC when the status page moved to Investigating Potential Issue and was resolved by 5:40 PM UTC. The outage lasted approximately 55 minutes. PagerDuty issued 2 status updates during the incident before services returned to normal.

On May 26, 2025 1:15 AM UTC, PagerDuty flagged an incident titled Incident Types UI issue, indicating a potential impact across a broad set of components in US and EU regions. The issue appeared to degrade multiple user-facing features and dashboards, with the status page listing many components as affected during the incident.

The issue persisted for about 25 minutes and was resolved by May 26, 2025 1:40 AM UTC, after which PagerDuty indicated all components had returned to normal operation. The incident affected dozens of components across the platform, including Slack integration, incident timelines, services, and APIs, across US and EU regions.

PagerDuty Runbook Automation briefly experienced a potential issue and was listed as degraded on the status page. The incident lasted about 55 minutes, starting at May 5, 2025 8:10 AM UTC and ending at May 5, 2025 9:05 AM UTC when the component returned to normal. PagerDuty issued 2 official updates during the incident describing the investigation and resolution. There were no confirmed customer-facing outages or widespread impacts reported. The Runbook Automation component was the only affected element.

PagerDuty experienced a temporary issue affecting mobile notifications for the US and EU Mobile Apps. The incident began on 6:40 PM UTC and was resolved by 11:20 PM UTC, lasting about 4 hours and 40 minutes. During the event, Mobile Application (US) and Mobile Application (EU) were listed in a degraded state on PagerDuty's status page. PagerDuty issued two status updates: first indicating an investigation into a potential notifications issue, and later confirming the issue had been resolved as services returned to normal.