Slack Outage History

Slack experienced a partial outage affecting Apps/Integrations/APIs and the Messaging components, with reports of custom apps/bots not sending messages and Slack Connect issues including difficulties @-mentioning channel members. The incident began at 1:45 AM UTC and was resolved by 3:29 AM UTC, lasting about 1 day, 1 hour and 44 minutes. Slack issued 2 status updates during the incident to communicate the degraded state and progress toward restoration. The disruption primarily impacted integrations and messaging workflows, with the Events API noted in official updates; no full-service outage across Slack services was reported.

Slack users worldwide encountered trouble loading or using the service, with issues signing in, loading workspaces, and sending messages. The outage affected multiple Slack components including Apps/Integrations/APIs, Messaging, Login/SSO, Workflows, and Connectivity, leading to degraded collaboration across teams in North America, Europe, and Asia. The incident began at Feb 26, 2025 3:29 PM UTC and lasted until Feb 27, 2025 12:44 AM UTC, for an approximate duration of 9 hours and 15 minutes.

Slack issued five status updates during the incident, including updates at Feb 26, 2025 3:50 PM UTC, Feb 26, 2025 3:59 PM UTC, and Feb 26, 2025 4:34 PM UTC, with a final update at Feb 27, 2025 12:44 AM UTC when services were restored. The outage affected users around the world, with reports of login problems, trouble loading, and failed message delivery, and the service returned to normal after the final update.

Slack experienced a partial outage affecting iOS users on app version 25.02.30, where @channelname, @here, and @everyone mentions did not notify the intended groups in channels. The issue affected two components, Messaging and Notifications. The incident began at 4:00 PM UTC and was resolved by 11:35 PM UTC, lasting 7 hours and 35 minutes. Slack issued two status updates during the event, apologizing for the inconvenience and promising to share more information as it became available. After the second update, the service returned to normal for affected users.

Slack experienced a sequence of partial outages affecting a subset of workflows rather than a global outage. The incidents began on Feb 14, 2025 3:44 PM UTC and persisted through Feb 17, 2025 11:44 PM UTC, with degradation focused on channel-related tasks. Initially, some users could not add multiple existing workspace members to channels by email address, and the Workspace/Org Administration component was listed as degraded. A later issue affected non-English iOS users who were unable to set the default status, with the Notifications component also degraded.

Slack documented the events on its status page with four official updates, tracking investigation and remediation efforts. The degradation progressed from an initial warning to eventual restoration, with the final update marking the affected components as up at Feb 17, 2025 11:44 PM UTC. The incident spanned roughly three days and affected specific features rather than a broad service outage.

Slack reported a disruption affecting the Workflow Builder feature, with users experiencing issues when adding or triggering steps. Some users may have seen errors such as 'We had a problem loading your spreadsheet' while workflows failed to load or run. The incident affected the Workflows component and resulted in degraded automation for approximately 2 hours and 40 minutes, from 7:44 PM UTC to 10:24 PM UTC. Slack issued two status updates during the event, first noting an investigation into the errors with workflow steps and later confirming restoration of normal Workflow Builder functionality.

Slack experienced a degraded experience in the Messaging component as custom emoji failed to load for users. The incident began at Feb 11, 2025 9:44 PM UTC when Slack moved to a degraded state and indicated ongoing investigation. The issue persisted until Feb 12, 2025 11:14 PM UTC when the status returned to normal. The incident lasted about 25 hours and 30 minutes, with two official status updates issued during the period.

The Slack search functionality experienced errors when using search filters, causing degraded search results for some users. The issue began at 6:39 AM UTC when the Search component was listed as degraded, and affected attempts to filter search queries. The outage lasted approximately 2 hours and 36 minutes, with normal search restored by 9:15 AM UTC. Slack issued 2 official status updates during the incident, documenting the investigation and resolution.

Slack documented the incident on their status site, confirming an investigation and then recovery as updates were posted. The issue affected only the search feature and did not appear to impact other Slack services.

Slack users experienced problems rendering and searching for emojis, causing a brief degradation of emoji-related messaging. The incident began on 5:24 PM UTC and was resolved by 6:39 PM UTC, lasting about 1 hour and 15 minutes. The affected component was Messaging, impacting emoji rendering and emoji search within Slack messages.

Slack published three status updates during the incident, describing ongoing investigation and eventual restoration of emoji functionality. The event appeared global with no regional pattern reported.

Slack experienced a brief disruption affecting the ability to switch workspaces by clicking workspace icons in the left sidebar, impacting the Workspace/Org Administration component. The incident began at Feb 6, 2025 3:09 AM UTC and was resolved by Feb 6, 2025 4:25 AM UTC, lasting about 1 hour 16 minutes. Slack issued two status updates during the incident.

Slack experienced an extended outage impacting admin-facing features, including loading the People page in the admin dashboard, workspace and org administration pages, and mobile notifications for Slack Connect channels. The issue started on 11:00 AM UTC and lasted for about 37 hours before resolution. Admin workflows were disrupted globally, with users reporting delays loading admin pages and inconsistent notifications.

Slack published five status updates during the incident as engineers investigated and mitigated the problems. The outages affected multiple components, namely Search, Workspace/Org Administration, and Notifications. By 12:09 AM UTC the affected components had returned to normal, and operations resumed.