Slack Outage History

Slack AI search experienced slower response times, impacting users attempting to search conversations and content with Slack AI. The issue affected the Search component and caused delays in results. The incident lasted approximately 1 hour and 49 minutes, from 4:25 PM UTC to 6:14 PM UTC.

The Slack status page documented the response with two updates: the initial notice at 4:25 PM UTC and a follow-up at 6:14 PM UTC confirming the issue was resolved.

Slack experienced a brief UI issue where Threads in the sidebar appeared bolded to indicate new content, even when there was none. The problem affected the Messaging and Notifications components and could lead to confusion for users until resolved. The incident began at Jan 28, 2025 2:35 PM UTC and was resolved by Jan 28, 2025 9:54 PM UTC, lasting about 7 hours and 19 minutes. Slack issued two status updates: one noting the issue and ongoing investigation, and another confirming the resolution as the UI returned to normal.

Slack began reporting an incident at Jan 24, 2025 12:10 AM UTC after the Intune App for Android crashed when users tapped the Activity tab. The issue expanded to affect multiple Slack components, including Connectivity, Workflows, Messaging, and Notifications, with intermittent behavior and degraded functionality for some users. There were additional reports affecting iOS messaging for some users, including missing message fields. Over the next days, Slack issued several status updates noting investigations and partial recoveries as components fluctuated between degraded and recovering. The situation spanned from Jan 24, 2025 12:10 AM UTC to Jan 28, 2025 1:25 AM UTC, with Connectivity returning to normal by Jan 28, 2025 1:25 AM UTC.

Slack reported a degraded login/SSO experience beginning at 3:59 AM UTC. Some users could not receive SMS-based two-factor authentication codes, which could block sign-ins. Slack noted that the two-factor authentication provider was experiencing issues and that backup codes could be used to sign in while the problem was being addressed.

Slack issued 2 status updates during the incident. In the update at 7:09 AM UTC, Slack explained the SMS 2FA problem and that the service would continue to monitor and provide an update. The issue was resolved by 7:14 AM UTC, with the Login/SSO component returning to normal. The incident lasted approximately 3 hours and 15 minutes.

Slack EKM users experienced errors when using core features like sending messages and triggering workflows, impacting enterprise workspaces enrolled in Enterprise Key Management. Users in these environments reported interruptions while trying to send messages or automate workflows.

The Slack outage began on Jan 6, 2025 3:14 PM UTC with scheduled workflows not triggering, and extended across multiple client features through Jan 10, 2025 8:59 PM UTC. Users reported degraded experiences including sidebars not highlighting new DMs and channel notifications, and occasional difficulty switching between workspaces. The problems affected several components (Workflows, Notifications, and Connectivity), leading to intermittent failures and incomplete automation across desktop and web clients. While some workarounds were noted (such as using the mobile app or refreshing the Slack client), the incident persisted for days with varying impact and visibility. The outage lasted roughly four days until recovery progressed for multiple features.

Slack issued several status updates during the incident, acknowledging issues across the affected components and stating that the team was actively investigating and working toward a fix. By Jan 10, 2025 8:59 PM UTC, the last affected component, Notifications, had recovered, with other features showing earlier improvements. The incident demonstrates how intermittent issues in multiple Slack features can disrupt daily collaboration, even as services return to normal.