PagerDuty Outage History

PagerDuty experienced an incident where customers in the US service region encountered delays in applying schedule overrides to their on-call schedules. The issue affected the Schedules and Escalation Policies component, causing recently applied schedule overrides to take longer than normal to become active. The incident was resolved after 3.2 hours.

PagerDuty experienced an issue with their Schedules API that affected both US and EU REST API endpoints for 28 minutes. The incident was classified as minor, with mobile and web UIs remaining unaffected, and event ingestion and incident notification delivery continuing to operate normally. A fix was deployed and systems showed improvement during monitoring.

PagerDuty Advance experienced delays and timeouts for 1.4 hours, while event ingestion and incident notification delivery remained unaffected. The service team actively monitored the situation and observed improvements during the incident. The issue was resolved with systems returning to normal operation.

PagerDuty customers across all service regions experienced issues with Slack functionality due to an ongoing incident at Slack, affecting notification delivery and incident card updates. The outage impacted both EU and US Slack components for 10 hours. The Slack-related issues have been resolved and PagerDuty continues monitoring the situation.

PagerDuty customers across all service regions experienced issues with Slack functionality due to an ongoing incident at Slack's infrastructure. The outage affected Slack notification delivery for PagerDuty users. The issue was resolved after 44 minutes with improvements observed in Slack notification delivery.

PagerDuty experienced issues affecting their EU service region, impacting multiple core services including SMS, voice, email, web application, Events API, webhooks, and various dashboard components. The incident lasted approximately 1 hour before a fix was deployed and systems began recovering. All EU-region functionality was restored after the fix implementation.

PagerDuty experienced issues with their AIOps and Event Intelligence features for customers in the US Service Region, affecting incident correlation capabilities including intelligent change correlation and probable origin detection. The incident was classified as minor and lasted approximately 1.3 hours. PagerDuty identified the root cause and implemented remediation to resolve the correlation issues.

PagerDuty experienced an incident where Jeli customers in the US Service Region were unable to access Jeli opportunities for 24 minutes. The core PagerDuty services including event ingestion and incident notification delivery remained unaffected during this time. The issue was resolved after investigation and monitoring.

PagerDuty experienced event processing issues affecting customers in both US and EU regions between 9:01 UTC and 9:50 UTC, impacting the Events API in both regions. The incident lasted approximately 1 hour with no ongoing impact reported after resolution. PagerDuty identified the issue and confirmed that event processing returned to normal operation.

PagerDuty experienced delayed event processing that affected the Events API in the US region for 28 minutes. The issue impacted event ingestion and incident notification delivery for a subset of customers. The service was restored after deploying a fix and taking corrective action.