Issue Identified - Slack Outage
This summary is created by Generative AI and may differ from the actual content.
Overview
On May 14, 2026 between 14:01 UTC and 15:39 UTC, PagerDuty customers in the US and EU service regions experienced a disruption of Slack‑based incident management. During this window Slack notifications and incident‑card interactions were unavailable, while PagerDuty’s core platform, event‑ingestion pipeline, and web UI remained fully operational.
Impact
All PagerDuty customers using the Slack integration in both US and EU regions were unable to receive Slack notifications or interact with incident cards. All other notification channels (email, phone, push, webhooks) continued to function normally. No impact on event ingestion or the web application was reported.
Trigger
An outage in the Slack platform itself caused the Slack API to become unavailable, breaking PagerDuty’s integration that relies on that API.
Detection
PagerDuty observed that the Slack integration began experiencing failures at 14:01 UTC, indicating a loss of communication with Slack’s API. The postmortem does not attribute this awareness to a specific monitoring system.
Resolution
When Slack’s API returned to full operation at 15:39 UTC, PagerDuty’s Slack integration automatically recovered, restoring notification delivery and incident‑card functionality. PagerDuty continued to monitor the situation until the external issue was resolved.
Root Cause
The incident was caused by an external outage of the Slack platform, which prevented PagerDuty from communicating with Slack’s API and therefore disabled the Slack integration.