PagerDuty Outage History

PagerDuty reported a potential issue at 18:00 UTC affecting a broad set of components across the US and EU, including Jira Cloud, Zendesk, Slack, Microsoft Teams, Email, Runbook Automation, REST API, and Webhooks. During the incident some users may have experienced delays or interruptions in alerting and incident workflows while the platform was investigated. The service posted two status updates and, by 18:25 UTC, indicated restoration with most components returning to normal. The outage lasted approximately 25 minutes, beginning at 6:00 PM UTC and ending at 6:25 PM UTC.

PagerDuty's status page showed an investigation into a potential issue affecting a broad set of services and integrations across US and EU regions. The updates stated that if any impact was confirmed, PagerDuty would communicate within 15 minutes; otherwise the notification would be removed. The incident appeared to affect a wide range of components, including core services, Log In and SSO, Incident Workflows, Email, Push, SMS, Voice, REST API, Jira Cloud and Server, Zendesk, Slack, Microsoft Teams, Webhooks, and more, across both US and EU regions. The event did not indicate a confirmed outage, and services were restored after about 1 hour 25 minutes.

Timeline: The issue began at Apr 26, 2025 12:25 AM UTC and was resolved by Apr 26, 2025 1:50 AM UTC. The incident lasted approximately 1 hour and 25 minutes, and the PagerDuty status page posted two updates during the event, moving from investigation to back to normal.

PagerDuty experienced a regional outage affecting core services across US and EU regions, disrupting incident management for many users. Dozens of components, including Services, Notification Delivery, Email, Slack, REST API, Jira Cloud, and more, were impacted, leading to delayed or missing alerts and automation. The incident began at 7:55 PM UTC and was resolved by 8:35 PM UTC, lasting roughly 40 minutes.

During the outage, PagerDuty issued two status updates on the status page. The initial update indicated Investigating Potential Issue, and the follow-up confirmed recovery as affected components returned to normal. The issue demonstrates how many interconnected PagerDuty services can be impacted in a short window and how the company communicates during an incident.

PagerDuty reported a potential issue affecting a broad set of services across the US and EU regions, with numerous components briefly listed under warning during the incident. The status page indicated a potential impact while investigators reviewed the situation, and there was no explicit confirmation of a widespread outage in the updates.

The incident began at 8:55 AM UTC and was resolved by 9:15 AM UTC, lasting about 20 minutes. The provider issued 2 status updates during the incident, with affected components across US and EU regions returning to normal after the investigation.

PagerDuty experienced a brief potential issue affecting a broad set of services across the US and EU. The incident was first acknowledged at 3:00 PM UTC as 'Investigating Potential Issue', with numerous components listed as impacted across PagerDuty's ecosystem, including Analytics, Change Events, Log In and SSO, Incident Timeline and Alert Logs, Services, Email, Push, Slack, Jira Cloud, Runbook Automation, and more. The outage lasted about 35 minutes and was resolved by 3:35 PM UTC. The PagerDuty status page issued two updates during the incident, confirming recovery for the affected components.

PagerDuty briefly investigated a potential issue beginning at Apr 21, 2025 4:35 PM UTC after the status page flagged a broad set of components with a warning. There was no confirmed impact communicated, and the incident was resolved by Apr 21, 2025 5:05 PM UTC, lasting roughly 30 minutes with all components returning to the normal state.

The PagerDuty incident caused a brief period of degraded performance across multiple components spanning the US and EU. Users could experience delays or missing notifications, disrupted incident timelines, and interruptions in several integrations. The outage began at Apr 19, 2025 6:30 AM UTC and was resolved by Apr 19, 2025 6:45 AM UTC, lasting about 15 minutes.

PagerDuty experienced a brief UI page loading issue affecting customers in the US and EU service regions. Some users could not load certain pages in the PagerDuty UI. The outage began at 2:40 PM UTC and was resolved by 2:55 PM UTC after the PagerDuty team issued two updates. The incident impacted two components (Web Application for US and Web Application for EU) and lasted about 15 minutes before service returned to normal.

The PagerDuty status page listed a brief investigation into a potential issue affecting the Jeli component. There was no confirmed service impact reported, and the incident was resolved about 55 minutes later. The incident began at Apr 14, 2025 10:35 PM UTC and ended at Apr 14, 2025 11:30 PM UTC with two status updates over the course of the event as the team worked to confirm impact and restore normal operation.

PagerDuty experienced a brief outage affecting US and EU regions. All PagerDuty services reported 500 errors across the UI and API, causing temporary unavailability for users and impacting a wide set of components. The incident lasted about 10 minutes, from 4:30 PM UTC to 4:40 PM UTC, with recovery observed as services began to come back online.

Status updates on the PagerDuty status page indicated an ongoing investigation and noted signs of recovery, with communication pointing to a near-term update as the team worked to restore functionality. By the end of the window, services across US and EU regions had largely recovered.