Slack Outage History

The Slack Messaging component experienced a degradation in email delivery that prevented some users from receiving email confirmation codes and invitations. As a result, affected users could not complete email-based login or accept invitations. The outage began at Feb 25, 2026 12:29 AM UTC and was resolved by Feb 25, 2026 4:54 AM UTC, lasting roughly 4 hours and 25 minutes.

Slack issued a series of status updates from the incident start through resolution, detailing investigation progress, root causes, and fix rollout. The final update noted that the Messaging component had recovered. In total, Slack published 6 status updates during the incident, with root causes including a suppression list subtype causing blocks and a missing data field in the email validation system before the fix was deployed.

Slack experienced a disruption impacting Direct Messaging, with users unable to add people to multi-person direct messages and some errors when sending messages. The issue affected Slack's Messaging component and persisted for several hours. The outage began on 2:39 PM UTC and was resolved by 7:24 PM UTC, for a duration of roughly 4 hours and 45 minutes. Users reported difficulties with direct messaging during the incident, and some updates noted ongoing investigation and stabilization efforts.

Slack experienced a prolonged connectivity outage that prevented many users from accessing Slack via web browsers and impacted app integrations relying on Incoming Webhooks. The incident began at Feb 18, 2026 10:44 AM UTC and persisted for about 37 hours, ending with services restored at Feb 20, 2026 12:29 AM UTC. In addition to general access issues, Slack noted that Incoming Webhooks could silently fail during app installations, affecting certain Apps/Integrations/APIs during the early phase of the incident. The outage affected multiple regions as users reported access problems across different networks.

Slack issued four official updates during the incident. The initial update at Feb 18, 2026 10:44 AM UTC marked a transition from a nominal connectivity state to a degraded condition. A second update at Feb 18, 2026 2:04 PM UTC warned about issues generating Incoming Webhooks and moved Apps/Integrations/APIs to warn. The third update at Feb 18, 2026 6:34 PM UTC described users unable to access Slack via various browsers, with antivirus conflicts noted, and Apps/Integrations/APIs improving to up. The final update at Feb 20, 2026 12:29 AM UTC indicated Connectivity had returned to up.

Overall, the incident showed a prolonged connectivity problem with some API integration issues resolving sooner; however, the primary access interruption endured for most of the event, prompting ongoing monitoring of service availability.

Slack experienced a brief connectivity incident that affected a subset of Slack workspaces. Users reported intermittent access to messages and channels during the event. The outage began at Feb 12, 2026 11:09 PM UTC and was resolved by Feb 12, 2026 11:30 PM UTC, lasting about 21 minutes.

The Slack status page issued 2 updates during the incident. The first update indicated that a subset of workspaces were affected and that engineers were actively investigating. The second update announced that connectivity had been restored and services were returning to normal.

Slack reported a partial outage impacting Apps/Integrations/APIs, preventing users from installing third-party apps into Slack workspaces. When attempting to authorize apps, users could encounter a blank screen that prevented installations from completing. The incident began at Feb 11, 2026 1:40 AM UTC as the issue moved from up to warning, and Slack noted it was investigating multiple potential causes.

The problem was resolved by Feb 11, 2026 3:25 AM UTC, with the Apps/Integrations/APIs component returning to normal. The incident lasted about 1 hour and 45 minutes, and Slack issued two status updates during the event to outline progress and restoration.

Slack experienced an issue with scheduled workflows, causing authentication errors that prevented the Send a message step from executing as expected. Other workflow types, such as link trigger workflows, were not affected. The outage primarily impacted users relying on automated scheduled messages.

The outage began on 11:19 AM UTC and was resolved by 8:14 PM UTC, lasting about 8 hours and 55 minutes. Slack posted two status updates during the incident as the team investigated and then restored the functionality, and the incident moved from a warning to resolved. User reports were limited, with a single report from Pune, India noting trouble during the outage.

Slack experienced an outage where the App History and Chat tabs were not loading for users on desktop and web. Some users saw blank screens when attempting to access these tabs, while Slack mobile remained functional. The issue affected Apps/Integrations/APIs. The outage began at 12:54 PM UTC and was resolved by 5:04 PM UTC, lasting approximately 4 hours and 10 minutes. Slack issued two status updates during the incident.

Slack reported an issue where Windows desktop notification pop-ups were not appearing for some users, though notification sounds could still play. The problem affected the Notifications component and began at Feb 3, 2026 2:39 PM UTC and was resolved by Feb 3, 2026 5:44 PM UTC, lasting about 3 hours. Slack rolled back the latest release to restore the popup functionality and issued progress updates via its status page during the incident.

Slack experienced a multi-stage degradation affecting channel creation and visibility, Salesforce Channel functionality, and workflow editing. Initial symptoms included channels renamed with a 'ZC:' prefix or missing discussions, and Salesforce automation events failing to dispatch. The incident began on 3:54 PM UTC and stretched across several days as Slack worked to identify and mitigate the problem, with the Messaging and Apps/Integrations/APIs components most affected.

Over the course of the incident, Slack issued eight official updates across the status page. A feature degradation around 12:39 AM UTC caused some Free, Trial, and Pro plan workspaces to appear blurred. By 2:19 AM UTC engineers rolled out a fix for Salesforce Channels, including clearing cached channel data. Issues around workflows (notably editing existing workflows) persisted and were addressed progressively, with the final update around 6:24 PM UTC indicating the Workflows component was back to normal and related issues stabilized.

Slack experienced degraded performance with trouble loading and performing actions across the platform. Users reported issues related to App Management, and the incident affected multiple Slack components, including Apps/Integrations/APIs, Workspace/Org Administration, Login/SSO, and Messaging, leading to delays and partial functionality for app management tasks and related features.

The Slack status page documented an upstream provider issue causing email delivery delays, with updates issued throughout the incident. The issue involved several components and persisted from 7:44 PM UTC until it was resolved by 8:14 AM UTC, spanning roughly 12 hours and 30 minutes. The provider released 8 status updates during the incident, and services returned to normal after the upstream issue was addressed.