PagerDuty outage history

PagerDuty experienced a regional issue in the EU where the Analytics Dashboard stopped updating, limiting visibility into analytics data for affected customers. The incident began at 8:00 AM UTC and was resolved by 11:15 AM UTC, lasting about three hours. During the incident, the EU Analytics component moved from up to warn before returning to up, per status updates.

The impact was localized to the EU region, with the Analytics Dashboard in that region being the primary affected component.

PagerDuty experienced an outage affecting SMS and Voice notification delivery for users on the Reliance Jio carrier network in India. While PagerDuty’s platform remained operational, some mobile alerts and voice notifications did not reach recipients on that network. The disruption began at Jul 21, 2026 11:15 PM UTC and persisted through ongoing monitoring.

Updates from PagerDuty described the cause as a carrier-level infrastructure problem outside PagerDuty's control. The affected delivery paths include SMS and Voice, and the status moved through monitoring updates until a recovery was observed by Jul 29, 2026 5:55 PM UTC when the affected components returned to up. A report from Chennai at 11:10 AM UTC noted the PagerDuty site not loading, aligning with the localized disruption. The impact appeared regional to India rather than global.

An issue with PagerDuty's Workflow Automation prevented saving Incident Type triggers when added to an Incident Workflow, impacting automated incident responses for customers across all regions. Users attempting to save new triggers could experience failures, disrupting workflow setup. The incident began at 11:40 AM UTC and was resolved by 1:45 PM UTC.

PagerDuty flagged a brief issue affecting Incident Voice Notifications, causing voice alerts to announce incidents with incomplete titles. This impacted users relying on voice channels across all service regions (EU and US). The event began when the Voice Notification components moved to a degraded state at 6:45 AM UTC and was resolved when they returned to normal at 8:20 AM UTC, for a duration of about 1 hour 35 minutes. PagerDuty's status updates noted that the issue affected the content of voice notifications, and that both the EU and US voice notification delivery paths were restored to normal as the incident concluded.

PagerDuty Advance in the US service region encountered delays and timeouts affecting users performing Advance-related actions. The incident began at 9:11 PM UTC and lasted about 34 minutes, with event ingestion and incident notification delivery remaining unaffected. The issue was resolved by 9:45 PM UTC as PagerDuty Advance returned to normal operations.

Users in the US and EU reported an issue updating or deleting shift-based schedules, impacting on-call rotations and scheduling workflows. The disruption appeared to affect the ability to manage shift-based schedules and could interfere with incident response timelines. The incident started at 7:10 PM UTC and was resolved about 15 minutes later, by 7:25 PM UTC.

The PagerDuty incident began at 9:20 AM UTC with an initial investigation into a potential issue. The status page indicated problems with schedule change notifications and affected a broad set of integrations across US and EU regions, potentially impacting alert delivery and escalation workflows.

A follow-up update at 9:50 AM UTC framed the issue as related to schedule change notifications, with the team continuing to investigate. By 10:40 AM UTC the issue was resolved and affected components returned to normal, marking the incident as completed after roughly 1 hour and 20 minutes. The incident included 3 official status updates. Affected areas included multiple integrations such as Slack, Jira Cloud, Microsoft Teams, Zendesk, Incoming Email, and other services across US and EU regions.

PagerDuty reported an investigation into a potential issue at 7:35 PM UTC. A broad set of components across the platform were listed as warn or under investigation, including Integrations, Incident Workflows, Web Application, and Notifications, reflecting widespread but not necessarily service-wide disruption. The status page noted that if an impact was confirmed, updates would follow within 15 minutes. The incident lasted about 3 hours and resolved by 10:35 PM UTC. Two status updates were issued during the incident.

The incident affected PagerDuty's US region email components, specifically Integrations / Incoming Email (US) and Notification Delivery / Email (US). The issue began at 10:40 AM UTC when the status changed from up to warn and lasted for about 1 hour 40 minutes, with the system returning to normal at 12:20 PM UTC. PagerDuty issued two status updates during the event, indicating an active investigation and eventual resolution. The impact appears to be degraded email processing, potentially delaying or interrupting email delivery for integrations and notifications in the US region.

PagerDuty experienced a brief degraded email delivery issue affecting the US region, with two components listed as impacted: Integrations / Incoming Email (US) and Notification Delivery / Email (US). The incident began at 10:25 AM UTC and was resolved by 10:30 AM UTC, lasting about 5 minutes.

The PagerDuty status page noted an investigation into a potential slow email event, followed by restoration to normal operation. The provider issued 2 status updates during the incident to inform users about the affected components.