Slack Outage History

Slack experienced a degraded state affecting Apps/Integrations/APIs as some Slack Apps using dropdown controls displayed 'We cannot display this message.' The issue appeared in the latest version of Slack and prompted an investigation. The incident began at Aug 28, 2025 12:44 PM UTC and was resolved by Aug 28, 2025 3:24 PM UTC, lasting about 2 hours and 40 minutes.

Slack posted two official status updates during the incident, describing the investigation and subsequent resolution. The Apps/Integrations/APIs component returned to normal after the fix.

Slack experienced a brief degradation in messaging with some users seeing trouble loading threads and a \"Something's fishy!\" error. The incident began at Aug 25, 2025 9:29 PM UTC and was resolved by Aug 25, 2025 9:54 PM UTC, lasting about 25 minutes. Slack issued 2 status updates during the incident, listing the Messaging component as affected and indicating that the issue was under investigation with updates to follow. The outage was resolved with messaging services restored.

Slack experienced a brief connectivity issue affecting some standalone workspaces, preventing users from loading Slack or connecting to messages. The outage lasted about 55 minutes, from Aug 24, 2025 3:04 PM UTC to Aug 24, 2025 3:59 PM UTC.

Slack experienced a partial outage affecting a subset of users in the Europe Central region, with the Slack sidebar content failing to load on the web and desktop apps. Messaging and other core features remained available. The outage began on 10:39 AM UTC and was resolved by 11:44 AM UTC, lasting about 1 hour and 5 minutes.

Slack issued 2 status updates over the course of the incident to communicate progress and restoration. The issue was confined to the Connectivity component and did not indicate a broader, global impact.

The Slack sign-in flow on mobile browsers experienced a redirect loop after entering the six-digit code, preventing users from signing in at slack.com/signin. Sign-ins via a workspace URL or the Slack app were not affected. The incident began at 8:59 PM UTC and was resolved by 12:19 AM UTC, lasting approximately 3 hours and 20 minutes. Slack issued two official updates during the incident as it investigated and worked to restore sign-in for affected users.

Slack posted two official updates during the incident as it investigated the cause within the Login/SSO component and applied a fix. The issue was limited to mobile sign-in flows at slack.com/signin; login from workspace URLs or the Slack app remained available. The incident concluded with service restored to normal by 12:19 AM UTC.

Slack experienced delays in email delivery, including login and password reset messages, causing some users to receive authentication-related emails hours after they were expected. The outage began at Aug 7, 2025 9:39 PM UTC and was resolved by Aug 8, 2025 6:19 PM UTC, lasting approximately 20 hours and 40 minutes. This degraded login reliability and delayed notifications for a portion of users. Slack issued two status updates during the incident: the initial alert describing the delay and ongoing investigation, and a follow up noting that email delivery was returning to normal. The issue affected 2 components: Workspace/Org Administration and Login/SSO. User reports remained limited in volume throughout the incident.

Slack reported that some users encountered error messages when attempting to change appearance preferences. The issue affected the Apps/Integrations/APIs component, causing a degraded experience for users trying to modify themes or appearance settings within Slack.

The incident began at Aug 6, 2025 1:19 AM UTC and was resolved by Aug 6, 2025 3:09 AM UTC, lasting approximately 1 hour and 50 minutes. Slack posted two official updates during the event to inform users about the investigation and restoration of normal functionality.

The outage began at Jul 30, 2025 10:59 PM UTC and was resolved by Jul 30, 2025 11:29 PM UTC. Slack experienced a brief degradation affecting two components: Messaging and Connectivity, leading to intermittent messaging and connectivity issues for users during the window. The incident involved two official status updates from Slack before service returned to normal.

Slack experienced regional connectivity issues in Asia-Pacific, impacting some users' ability to load Slack and causing the app to refresh or restart for others. The issues were observed in APAC, including the Philippines, and affected four components: Connectivity, Search, Apps/Integrations/APIs, and Login/SSO. The incident began on Jul 27, 2025 12:54 AM UTC and was resolved by Jul 30, 2025 9:44 PM UTC. Slack posted six official updates during the incident as it worked to restore normal service and confirm recovery.

Slack reported a UI issue where the See More button did not function for messages from apps and integrations, preventing users from expanding content in those messages. The issue affected the Apps/Integrations/APIs component and disrupted viewing additional details within bot and integration messages. The incident began on 7:04 AM UTC and was resolved by 8:59 AM UTC, lasting approximately 1 hour and 55 minutes. Slack issued 2 status updates during the incident and worked toward a fix.