Slack Outage History

The outage began with degraded connectivity on 10:44 AM UTC and expanded to include issues generating Incoming Webhooks. Over the course of the incident, Slack issued four official updates, including a note at 2:04 PM UTC about webhook generation problems and a subsequent update at 6:34 PM UTC describing widespread browser access failures. Users reported being unable to reach Slack through multiple browsers, with some reports mentioning antivirus software conflicts. The incident persisted for about 1 day and 13 hours, finally resolving with connectivity restored by 12:29 AM UTC and the Apps/Integrations/APIs returning to normal.

A brief connectivity incident affected a subset of Slack workspaces, with some users unable to access Slack or experiencing intermittent connectivity. The outage began on 11:09 PM UTC and was resolved by 11:30 PM UTC, lasting about 21 minutes. Slack documented the incident on its status page, initially noting investigation and a planned update within 30 minutes, and later confirming restoration.

Slack users were unable to install third-party apps to their workspaces; attempting to authorize apps yielded a blank screen, preventing installations. The issue affected the Apps/Integrations/APIs component. The outage began at 1:40 AM UTC and was resolved by 3:25 AM UTC, lasting roughly 1 hour and 45 minutes. Slack documented the incident with status updates as they investigated and worked toward a resolution, issuing 2 updates during the incident.

Slack experienced degraded performance for its scheduled workflows, with authentication errors preventing the Send a message step from executing as expected. Other workflow types, such as link trigger workflows, were not affected. The incident began at Feb 6, 2026 11:19 AM UTC and was resolved by Feb 6, 2026 8:14 PM UTC, lasting about 8 hours and 55 minutes. A small number of user reports surfaced during the incident. The Slack status page issued two updates—one acknowledging the issue and noting investigation, and a follow-up confirming recovery.

Slack experienced a temporary outage of the App History and Chat tabs on desktop and web clients, with users seeing blank screens when attempting to access these tabs. Mobile apps were not affected. The issue was confined to the Apps/Integrations/APIs area and did not appear to impact other Slack features. The outage began at Feb 5, 2026 12:54 PM UTC and was resolved by Feb 5, 2026 5:04 PM UTC, lasting roughly 4 hours and 10 minutes. Slack issued two status updates during the incident, confirming the investigation and subsequent restoration of access once the issue was resolved.

Overall, the disruption appeared limited to desktop and web usage and correlates with the announced component issues; access to App History and Chat tabs returned after the incident, and Slack's updates indicated the problem was resolved.

Slack experienced an outage affecting Windows desktop notifications where notification pop-ups did not appear on screen for some users, though alert sounds could still be heard. The issue impacted the Notifications component for Windows users and degraded alert visibility. The outage began on 2:39 PM UTC and was resolved by 5:44 PM UTC, lasting roughly 3 hours and 5 minutes.

Slack's status page indicated a rollback of the latest Windows desktop notifications release to restore pop-up behavior. Over the incident, Slack issued 3 status updates as the team worked toward a fix, and the Notifications component returned to normal operation once the changes were rolled out.

Slack faced a multi-faceted outage beginning Jan 30, 2026 3:54 PM UTC that impacted messaging features, including channel visibility and discussions, with channels renamed and conversations not appearing where expected. A separate set of events errors related to Salesforce Automation were reported at Jan 30, 2026 10:19 PM UTC. By Jan 31, 2026 12:59 AM UTC a fix for Salesforce Channels was deployed and cached channel data was cleared to restore functionality.

The incident continued into early February, including a feature degradation that caused workspaces to appear blurred for some Free/Trial/Pro users, reported at Feb 1, 2026 12:39 AM UTC and addressed by Feb 1, 2026 2:19 AM UTC. Workflows-related issues emerged on Feb 2, 2026 11:09 AM UTC and persisted through Feb 2, 2026 5:54 PM UTC before being resolved by Feb 2, 2026 6:24 PM UTC. Slack issued eight status updates across four affected components: Messaging, Apps/Integrations/APIs, Workspace/Org Administration, and Workflows.

Slack experienced degraded actions and email delivery delays beginning on 7:44 PM UTC and lasting for about 12.5 hours, with multiple components affected. Users reported trouble performing App Management tasks such as creating apps, viewing client secrets, installing or deleting internal apps, and editing event subscriptions, while email delivery experienced delays due to an upstream provider issue. The incident impacted several areas of Slack, including Apps/Integrations/APIs, Workspace/Org Administration, Login/SSO, and Messaging.

Slack faced a partial outage affecting the ability to add payment methods during checkout. A small percentage of users globally encountered a 'Something’s gone wrong' error when attempting to add payment methods, tied to the Workspace/Org Administration component. The incident was global in scope but not regionally isolated and lasted about 2 hours, from Jan 14, 2026 9:24 PM UTC to Jan 14, 2026 11:24 PM UTC.

Slack posted an update at Jan 14, 2026 11:19 PM UTC noting ongoing fixes and monitoring, with no ETA. The status was returned to up by Jan 14, 2026 11:24 PM UTC.

Slack experienced a brief degradation affecting Connectivity and Messaging. The issue began at 10:34 PM UTC and was resolved by 11:44 PM UTC, lasting roughly 1 hour and 10 minutes. Slack posted two status updates during the incident, acknowledging the degraded state and confirming restoration. Users likely encountered intermittent connectivity and delays in sending or receiving messages during the disruption, with two core components affected: Connectivity and Messaging.