Slack Outage History

Slack experienced a brief degradation in the Apps/Integrations/APIs area caused by legacy webhooks that could affect app configurations. The incident began at Jun 23, 2025 10:54 AM UTC and was resolved by Jun 24, 2025 1:44 AM UTC, lasting approximately 14 hours and 50 minutes. Slack communicated that legacy webhooks may be causing issues with app configurations and that they were investigating, with the status transitioning the Apps/Integrations/APIs component from warning to up as remediation completed. The impact appeared limited to app configuration workflows within Slack, with no widespread service outages reported.

Slack experienced a temporary degradation in the Workflow Builder feature, with errors when executing steps such as Add spreadsheet row. Users attempting to run workflows involving these steps may have seen messages like 'The service used for this step isn't available.' The incident lasted about 1 hour and 31 minutes, beginning at 7:04 PM UTC and ending at 8:35 PM UTC. Slack posted two status updates during the incident as the team investigated and then confirmed resolution for the Workflows component.

Slack experienced intermittent issues affecting messaging and connectivity, spanning from 4:19 PM UTC to Jun 10, 2025 9:09 PM UTC. The incident began with a persistent "Join Channel" button affecting some channels and users, and later expanded to trouble loading content in threads and the Activity view. While some recovery occurred over the course of the incident, messaging remained degraded for a period before full restoration. The event involved two components — Messaging and Connectivity — and reflected an extended disruption across multiple days.

Slack experienced a partial outage affecting messaging and connectivity. Some users reported trouble connecting to Slack, loading the app, or sending and receiving messages. The incident began at Jun 5, 2025 4:34 PM UTC and was resolved by Jun 5, 2025 5:49 PM UTC, lasting about 1 hour 15 minutes.

Slack's status page listed the affected components as Messaging and Connectivity. The page showed updates including an initial note that Slack was investigating a new incident, followed by a confirmation that the issue had been resolved and services were back to normal. Slack issued 2 status updates during the incident.

Slack reported a brief outage affecting organizational dashboards, with dashboards not loading and search results potentially incomplete or inaccurate. The issue centered on the Workspace/Org Administration component, hindering admins and teams relying on organization-level dashboards. The incident began at Jun 2, 2025 6:04 PM UTC and was resolved by Jun 2, 2025 8:39 PM UTC, lasting about 2 hours and 35 minutes. Slack issued three official updates during the event, and the Workspace/Org Administration component transitioned from a degraded state back to normal as the issue was resolved.

Slack experienced a brief connectivity disruption that prevented some users from connecting to Slack or sending messages. The incident began at 12:59 AM UTC and was resolved by 2:34 AM UTC, lasting about 1 hour and 35 minutes. Slack noted that a small number of users were affected and treated the incident with high priority, publishing two status updates during the event as the team worked to restore service. The disruption primarily affected the Connectivity component, and Slack returned to normal once the issue was resolved.

Slack users experienced connectivity problems and were unable to load threads, hindering collaboration and messaging. The incident began at 10:39 PM UTC with a connectivity issue and by 11:40 PM UTC multiple components were affected, including Connectivity, Workflows, Canvases, Search, Apps/Integrations/APIs, Login/SSO, Messaging, and Files. The outage lasted about 1 hour 30 minutes and was resolved by 12:09 AM UTC.

The Slack system experienced a degraded notification experience where users did not receive alerts for channel messages or direct messages when the channel or DM window was open. The issue affected the Notifications component and was actively investigated; the outage began on May 7, 2025 2:09 PM UTC and was resolved by May 7, 2025 6:24 PM UTC, lasting about 4 hours and 15 minutes.

Slack posted two updates on its status site during the event, describing the investigation and the resolution. This was treated as a degraded notification experience rather than a full outage, with effects felt by users relying on channel and direct message alerts across affected regions.

The Slack Messaging component experienced a partial outage that affected message sending and loading the Threads view. From May 6, 2025 3:29 AM UTC to May 6, 2025 6:24 AM UTC, some users could not send messages to specific channels or conversations, and the Threads view displayed a 'Something's fishy!' error or failed to load.

Slack issued three status updates during the incident, reflecting ongoing investigation and eventual restoration. The outage lasted about 2 hours and 55 minutes, with service returning to normal after the final update at May 6, 2025 6:24 AM UTC.

Slack experienced a brief degradation of the Messaging component between 12:39 AM UTC and 1:19 AM UTC, lasting 40 minutes. During this window, users may have encountered delays or failures sending or receiving messages, while other Slack services remained available. The Slack status page indicated a degraded Messaging component and later confirmed recovery as the component returned to normal operation. The impact was confined to the Messaging service.