Slack Outage History

Slack experienced a brief degraded performance where images, icons, files, and other media failed to load on Slack.com pages and in the Slack app, including admin pages. The issue affected two components: Workspace/Org Administration and Connectivity, causing missing media and partially loaded content across Slack surfaces.

Slack experienced a brief degradation in the Login/SSO component beginning at Apr 13, 2025 4:09 PM UTC. Authentication-related issues may have prevented some users from logging in during the incident. The disruption lasted about 1 hour and 10 minutes, until Apr 13, 2025 5:19 PM UTC when the Login/SSO component returned to normal operation. Slack's status page updated to reflect the degraded state and subsequent recovery during this window.

Slack reported issues delivering login/confirmation code emails, causing some users to not receive codes or to find them in spam folders. The problem affected the Login/SSO component and prompted user reports, including a notification from a user in St. Petersburg. The incident began on Mar 28, 2025 2:29 AM UTC and was resolved by Apr 3, 2025 4:59 PM UTC, lasting roughly 6 days and 14 hours.

Slack posted two status updates during the incident: the initial degraded login email delivery notice with guidance to whitelist Slack senders, followed by a final update confirming the issue was resolved and the status back to normal.

Impact appeared limited to email delivery for login-related codes, with limited user reports indicating disruption for some users.

Slack experienced an outage affecting iOS users where channels and messages would not load. Some users on iOS encountered difficulties loading content, disrupting navigation and chat usage. The outage began at 5:34 PM UTC and lasted approximately 2 hours and 45 minutes, with connectivity restored by 8:19 PM UTC.

Slack provided updates via its status page, issuing 2 updates during the incident as engineers investigated and worked to restore access. The Connectivity component returned to normal by the resolution time above.

A brief degradation affected Slack's Workspace/Org Administration component. The issue began at 4:59 PM UTC and was resolved by 5:39 PM UTC, with the component returning to normal shortly thereafter. Slack's status page indicated a short disruption and a subsequent restoration of full functionality without additional updates.

Slack experienced degraded connectivity starting at 9:25 PM UTC when the Connectivity component moved from up to warn. The issue affected messaging and collaboration, with users potentially experiencing delays or inability to send messages and use presence features. The incident lasted about 3 hours, and the Connectivity component returned to up at 12:24 AM UTC.

Slack posted two official updates during the incident detailing the degraded connectivity and restoration progress, and the service was restored by 12:24 AM UTC.

Slack experienced a temporary degradation in search functionality, with users reporting that search queries did not return results. The issue affected the Search component and related Workspace/Org Administration tools, hindering people from locating messages. The outage began at 8:09 PM UTC and was resolved by 8:54 PM UTC, lasting about 35 minutes.

The Slack status page issued three updates during the incident. The initial notice at Mar 10, 2025 8:09 PM UTC indicated that search issues were being investigated. A follow-up at Mar 10, 2025 8:24 PM UTC confirmed ongoing problems and noted the scope included Workspace/Org Administration. The issue was marked resolved at Mar 10, 2025 8:54 PM UTC with Search and Workspace/Org Administration returning to normal.

Slack experienced a partial outage starting on Feb 27, 2025 1:45 AM UTC that affected custom apps not sending messages and Slack Connect. The issues were linked to the Events API and reflected an ongoing problem around loading Slack. Users relying on bots, automated workflows, and cross-workspace collaboration saw degraded messaging. The outage affected 2 components: Apps/Integrations/APIs and Messaging, and persisted until Feb 28, 2025 3:29 AM UTC, a duration of about 25 hours and 44 minutes. The provider issued 2 status updates during the incident.

Slack faced a global degradation starting at 3:29 PM UTC, with five components affected: Connectivity, Apps/Integrations/APIs, Messaging, Workflows, and Login/SSO. Users across the world reported trouble loading Slack, signing in, or sending messages, leading to widespread disruption over the next several hours. The outage lasted about 9 hours and 15 minutes and was resolved by 12:44 AM UTC.

Slack’s status page documented ongoing investigation with updates at 3:50 PM UTC, 3:59 PM UTC, and 4:34 PM UTC as the issue progressed, before service returned to normal. User reports from multiple regions—including North America, Europe, and Asia—described login issues, workspace loading problems, and messages not sending, indicating a widespread impact across the platform.

The Slack iOS app on version 25.02.30 experienced an outage where specific @-mentions, including @channelname, @here, and @everyone, did not notify channel members and related notifications did not fire as expected. This degraded the messaging experience for affected users and impacted the Messaging and Notifications components. The outage began on 4:00 PM UTC and was resolved by 11:35 PM UTC, lasting approximately 7 hours and 35 minutes. Slack issued two official status updates during the incident, describing the problem and its resolution, and functionality for mentions and notifications was restored. The issue appeared to be isolated to a subset of iOS users rather than the entire Slack service.