Slack Outage History

Slack experienced a partial outage in the admin dashboard, with Org Admins reporting troubles loading the People page and other admin pages. The issue could also affect the Enterprise Grid workspace discovery page. The disruption centered on the admin interface and the Search component, resulting in degraded admin workflows but not a global Slack service outage.

The incident lasted approximately 3 hours and 16 minutes, from 10:29 PM UTC to 1:45 AM UTC. Slack issued 2 status updates during the incident as the team investigated and then restored affected pages, with a final update confirming the resolution.

Slack experienced a brief degradation affecting signing in with Google and Google Sheets steps in Slack Workflows. Some customers may have encountered errors when signing in with Google, and Workflows steps that write to Google Sheets could fail. The incident began at 7:40 PM UTC and was resolved by 9:04 PM UTC, lasting about 1 hour and 24 minutes. Slack posted two official updates during the incident, noting the degraded functionality and later confirming restoration. The issue affected two components: Workflows and Connectivity.

Slack experienced a brief outage affecting loading of threads and notifications. Some users were unable to load threaded conversations or receive notifications for about 20 minutes. The incident began at 5:04 PM UTC and was resolved by 5:24 PM UTC. Slack posted two status updates during the event, noting an investigation and later confirming restoration of services. The disruption appeared limited in scope with no reports of widespread outages beyond the affected features.

Slack experienced degraded performance in Slack AI search, with slower response times when using the AI-powered search feature. The issue affected the Search component and impacted users attempting to locate information through Slack AI. The incident began at 4:25 PM UTC and was resolved by 6:14 PM UTC, lasting about 1 hour and 49 minutes.

Slack's status page acknowledged the issue, stating that investigators were looking into slower Slack AI search. The page published two updates during the incident to communicate progress and the eventual recovery.

Slack experienced a brief UI issue where Threads in the sidebar could appear bolded even when there was no new content. The symptom affected the Messaging and Notifications components and could confuse users without impacting message delivery.

The incident started at 2:35 PM UTC and was resolved by 9:54 PM UTC. Slack posted two official updates during the incident, describing the investigation and confirming resolution, after which normal behavior returned. The issue did not indicate a wider outage beyond the UI labeling.

Slack experienced multi-component mobile app issues beginning Jan 24, 2025 12:10 AM UTC. The incident affected four components—Connectivity, Workflows, Messaging, and Notifications—causing crashes in the Intune App for Android when users tap the Activity tab, workflows failing with an unexpected_builtin_exception, and issues such as missing message fields on iOS and sporadic notification delivery. The result was partial outages and degraded functionality across Slack’s mobile apps for several days.

Slack issued nine official updates during the incident as teams investigated and worked toward restoration. The incident began at the start time above and connectivity was back to up by Jan 28, 2025 1:25 AM UTC, with components returning to normal in a staged fashion by the end of the period.

Slack experienced a brief disruption delivering SMS-based two-factor authentication messages, potentially blocking login for some users. Slack stated that the two-factor authentication provider was experiencing issues and recommended using backup codes to sign in. The issue began at 7:09 AM UTC and was resolved by 7:14 AM UTC, lasting about 5 minutes. The incident involved the Login/SSO component and Slack issued 3 official updates during the outage.

The incident began on Jan 15, 2025 10:44 PM UTC with a degraded experience for Slack Notifications. By Jan 16, 2025 7:29 PM UTC, the issue affected Enterprise Key Management (EKM) enrolled workspaces, causing errors when using Slack features such as sending messages or triggering workflows. The impact touched four components: Notifications, Messaging, Workflows, and Connectivity. A partial restoration occurred for Messaging, Workflows, and Connectivity by Jan 16, 2025 7:54 PM UTC, with Notifications returning to normal by Jan 17, 2025 5:09 AM UTC. The outage lasted roughly 1 day and 6 hours. Slack issued four status updates during the incident to guide users through the recovery.

From Jan 6, 2025 3:14 PM UTC Slack began listing issues that affected multiple features: scheduled workflows not triggering; sidebars not showing badges for new DMs and channel notifications; and difficulty switching between workspaces for some accounts. The problems spanned three components and produced degraded usability for users across affected areas, including missed automations and reduced visibility of new messages.

Slack provided a series of status updates between Jan 6, 2025 3:14 PM UTC and Jan 10, 2025 8:59 PM UTC as engineers investigated and worked to restore service. The updates show the three components oscillating between up and warn at various times, with the Notifications component recovering by the final update. The incident lasted roughly four days, and the latest communication indicates gradual restoration rather than a single global outage.