Slack Outage History

Slack reported connection issues affecting Microsoft-related connectors, including Calendar, OneDrive, and Teams, within Slack's Apps/Integrations/APIs. Users may have encountered errors when attempting to use these connectors. The outage began at 8:24 AM UTC and was resolved by 1:24 PM UTC, lasting about 5 hours.

Slack's status page documented the incident with two official updates: one to warn of the issue and another to confirm restoration of connectivity. The service returned to normal as the connectors were re-enabled and status shifted back to a healthy state.

Slack experienced an incident affecting the Apps/Integrations/APIs component, causing trouble installing custom apps and integrations. For some users the OAuth permission dialog's 'Allow' button was disabled, preventing app installations. The outage lasted approximately 4 hours and 15 minutes, from 12:49 AM UTC to 5:04 AM UTC. The provider issued 2 status updates over the incident as it worked to resolve the issue.

Slack's Messaging component briefly displayed incorrect user statuses across mobile, web, and desktop clients, causing presence indicators to appear wrong (e.g., Active users shown as Away). The issue disrupted collaboration for about 1 hour, beginning at Aug 28, 2025 6:04 PM UTC and ending at Aug 28, 2025 7:09 PM UTC. Slack published two status updates during the incident describing the investigation and eventual restoration of normal operation.

The Slack Apps experience an outage affecting Apps/Integrations/APIs, with some users seeing the message 'We cannot display this message' when interacting with dropdown options. This caused dropdowns to fail to render and disrupted workflows that rely on app integrations. The incident began on 12:44 PM UTC and was resolved by 3:24 PM UTC, lasting roughly 2 hours and 40 minutes.

Slack's status page documented the issue as an investigation beginning at 12:44 PM UTC and showed two official updates during the incident before the service returned to normal. The issue appeared isolated to the Apps/Integrations/APIs area rather than a global Slack outage.

Slack experienced a brief degradation in its Messaging component affecting the ability to load threads. Some users reported errors such as 'Something's fishy!' while loading threads. The outage began at 9:29 PM UTC and was resolved by 9:54 PM UTC, lasting approximately 25 minutes. Slack posted two status updates during the incident, confirming ongoing investigation and later confirming resolution. The impact appeared to affect thread loading for a subset of users and did not indicate a regional pattern.

Slack experienced a brief outage affecting standalone workspaces, with users reporting trouble loading or connecting to Slack. The issue began at 3:04 PM UTC and ended around 3:59 PM UTC, lasting approximately 55 minutes. Slack documented the incident on its status page, focusing on the Connectivity component and providing three updates as engineers investigated and resolved the problem. During the disruption, users in affected workspaces could have experienced delays or inability to load Slack, access channels, or send messages until service was restored.

Slack reported a partial outage affecting a subset of users in the Europe (central) region, with the Slack sidebar not loading on web and desktop apps. Messaging remained functional, so users could still send and receive messages. The incident began on 10:39 AM UTC and was resolved by 11:44 AM UTC, lasting about 1 hour and 5 minutes. Slack listed the Connectivity component as degraded and issued 2 status updates during the event. The geographic footprint was regional to Europe (central).

Slack users attempting to sign in from mobile browsers via slack.com/signin encountered a redirect loop after entering the six-digit login code, blocking sign-in for some. Sign-in from a workspace URL or the Slack mobile app remained available. The issue affected the Login/SSO component. The incident began at 8:59 PM UTC when the service entered a degraded state and was resolved by 12:19 AM UTC, lasting about 3 hours and 20 minutes. The provider issued two status updates during the incident.

Slack experienced degraded email delivery beginning at Aug 7, 2025 9:39 PM UTC, with login-related emails and other account notifications arriving after hours. This partial outage affected two Slack components, Workspace/Org Administration and Login/SSO, disrupting login workflows and onboarding for a subset of users. Reports were limited, suggesting a non-global impact focused on email delivery timing.

The incident lasted roughly 20 hours and 40 minutes, from Aug 7, 2025 9:39 PM UTC to Aug 8, 2025 6:19 PM UTC. Slack issued two status updates during the event, noting delays in email delivery and later restoring normal service as email delivery returned to normal. By Aug 8, 2025 6:19 PM UTC, the status had been updated back to operational.

Impact was indicated by a small number of user reports describing delayed login and verification emails; once resolved, Slack restored normal email delivery and affected users regained access and notifications.

Slack experienced issues with changing appearance preferences, with some users receiving error messages when attempting to adjust appearance settings. The incident affected the Apps/Integrations/APIs component and lasted about 1 hour and 50 minutes, from 1:19 AM UTC to 3:09 AM UTC. Slack issued two status updates during the event, informing users of the investigation and later confirmation that the issue had been resolved.