PagerDuty Outage History

PagerDuty experienced an outage that produced 500 errors affecting login and access to the website. User reports began around 4:00 PM UTC and the issue persisted for about 23 minutes, with the service showing a 500 error page from 4:04 PM UTC and resolving by 4:27 PM UTC. The disruption appeared across multiple regions, indicating a widespread impact on the platform.

The provider did not publish any official status updates during this window. StatusGator logged an Early Warning Signal indicating issues starting at 4:04 PM UTC and ending at 4:27 PM UTC, with a large volume of user reports suggesting broad impact on login and page loading across North America, Europe, and beyond.

The incident began at 9:10 PM UTC, with PagerDuty stating they were investigating a potential issue. The issue affected multiple alerting and incident-management components across US and EU, including Push, Email, Notification Delivery, and Incident Timeline and Alert Logs. Users could experience degraded alert delivery or limited visibility into incident timelines during this period.

PagerDuty issued 2 status updates during the incident, and by 9:50 PM UTC all listed components were reported back to normal, ending a roughly 40-minute window of degraded service.

The PagerDuty status page showed a potential issue starting at 6:30 PM UTC, with a broad set of components across the US and EU listed as affected and the issue described as delayed Updates for Operations Console Data. This led to degraded visibility into incident timelines, logs, dashboards, and related data for users relying on the Operations Console. The outage lasted about 45 minutes, beginning at 6:30 PM UTC and concluding by 7:15 PM UTC. Three official status updates were issued during the incident.

The incident began at 3:10 PM UTC, with PagerDuty listing a potential issue and initiating investigations that spanned numerous components in US and EU regions. The event could have affected alerting and incident communications for some users, impacting a broad set of areas including Incident Timeline and Alert Logs, Notification Delivery, REST API, and Webhooks. Four official updates were issued during the incident as investigators worked to determine impact.

The issue was resolved by 4:00 PM UTC, with affected components returning to normal (up). The outage lasted about 50 minutes, from 3:10 PM UTC to 4:00 PM UTC, and the geographic footprint included PagerDuty services in the US and EU regions.

PagerDuty reported a brief incident affecting responder notifications for customers in the US region. Some responder requests were delayed or failed to send, potentially impacting on-call escalation and incident workflows. The issue affected the Responder Requests (US) component.

The outage began at 2:45 PM UTC and was resolved by 3:05 PM UTC, lasting roughly 20 minutes. The provider issued 2 status updates during the event as they investigated and resolved the issue.

An outage impacted PagerDuty's voice notifications and notification delivery across the United States and European Union. Users could not receive voice calls and notifications during the incident, affecting four components: Notification Delivery (US), Notification Delivery (EU), Voice (US), and Voice (EU). The issue began at 11:35 AM UTC and was resolved by 11:55 AM UTC. The EU regions recovered earlier, with EU components returning to normal by 11:40 AM UTC while US components remained impacted until the final resolution.

The provider issued 3 status updates during the incident.

PagerDuty experienced a brief outage affecting the ability to create new services with alert grouping enabled. The issue impacted the Services components in the US and EU regions. The incident began at 6:10 PM UTC and was resolved by 6:20 PM UTC, lasting about 10 minutes. PagerDuty issued two status updates during the incident, the first noting the issue and ongoing investigation and the second confirming recovery as services returned to normal.

PagerDuty announced an investigation into a potential issue affecting a broad set of services in US and EU. The incident began at Mar 3, 2025 4:17 PM UTC and was resolved by Mar 3, 2025 4:30 PM UTC, lasting about 13 minutes. The status page showed many components temporarily degraded or listed as under investigation before returning to normal. The provider issued 2 status updates during the incident. User reports indicated a moderate level of issues during the window, suggesting localized disruption but no confirmed widespread outage.

PagerDuty's Web App experienced a brief outage with 500 errors, causing UI loading issues and sign-in disruptions for users across multiple regions. The outage began at 4:09 PM UTC and was resolved by 4:17 PM UTC. StatusGator detected the issue at Mar 3, 2025 4:09 PM UTC, ahead of any official PagerDuty updates. No PagerDuty status updates were published during the incident.

PagerDuty reported a brief degradation of notification services starting at 9:30 PM UTC, affecting email notifications and related delivery channels across the US and EU regions. A broad set of components were listed as degraded, including Email, Push, Notification Delivery, Live Call Routing, Incident Timeline and Alert Logs, and several dashboards, which could have caused delays or missing alerts for users.

The incident ended at 9:50 PM UTC with services restored. PagerDuty published two status updates during the event to communicate the investigation and restoration across multiple components.