Slack Outage History

Slack experienced intermittent issues affecting Search and Apps/Integrations/APIs, including enterprise search and workflow connectors. Slack attributed the problem to an upstream provider issue and began investigating. The incident began on Jul 18, 2025 4:54 PM UTC and was resolved by Jul 18, 2025 6:19 PM UTC, lasting about 1 hour 25 minutes. The provider issued two status updates during the event, and services for the affected components were restored by the end of the window.

Slack experienced intermittent issues beginning at Jul 15, 2025 6:54 PM UTC, primarily affecting third-party app message components and causing occasional errors when using blocks in messages. Around Jul 15, 2025 8:44 PM UTC, new impact emerged as some users could not accept workspace invites, with the new-user creation button greyed out. A follow-up at Jul 15, 2025 10:19 PM UTC showed partial recovery for some components while others remained affected. The issues recurred on Jul 16, 2025 2:04 PM UTC as Slack again flagged problems with third-party app message components, but were finally resolved by Jul 16, 2025 2:09 PM UTC, with Slack listing 5 status updates over the course of the incident. Affected components included Apps/Integrations/APIs, Login/SSO, and Workspace/Org Administration.

Slack experienced a partial outage affecting the Apps/Integrations/APIs component, with some third-party apps experiencing connection issues. Users may have seen an "invalid argument error" when using the block_suggestion API. The outage began on Jul 15, 2025 8:34 AM UTC and was resolved on Jul 15, 2025 2:20 PM UTC, lasting roughly 5 hours and 46 minutes. The incident prompted Slack to provide status updates as it investigated and worked toward a fix.

During the incident the provider issued 2 status updates at Jul 15, 2025 8:34 AM UTC and Jul 15, 2025 2:20 PM UTC, reflecting the transition from up to warn and back to up as remediation progressed. The disruption was confined to Apps/Integrations/APIs and affected some third-party apps, rather than the entire Slack service.

Slack experienced a search disruption on api.slack.com starting at 4:39 AM UTC, with server errors when performing searches or accessing resources. The issue appeared focused on the search feature and gradually evolved to involve related API documentation/search components. By 5:19 PM UTC, the search function had returned to normal, but Apps/Integrations/APIs entries were affected and issued a degraded state. By 9:59 PM UTC, the Apps/Integrations/APIs component had recovered and overall services were restored. The incident lasted about 17 hours and 20 minutes, with multiple official updates issued during the period.

Slack experienced a brief outage affecting image and file uploads, with uploads appearing stuck or continuously loading. The issue was centered on the Files component, impacting users attempting to attach or send images and files. The incident began at 19:09 UTC when Slack marked the Files component as degraded, with user reports emerging around 20:31 UTC (including a report from New York). The problem persisted until it was resolved by 21:05 UTC, lasting approximately 1 hour and 56 minutes.

The Slack search function experienced a brief outage starting at Jul 1, 2025 7:24 PM UTC, with the Slack status page listing the affected components as Search and Workspace/Org Administration. Users reported that search queries returned no results, and this may have affected related admin pages such as Managing Members. The incident lasted about 2 hours and 45 minutes, with the issue resolving by Jul 1, 2025 10:09 PM UTC.

Slack issued two status updates during the incident. The first indicated an active investigation and an expected update within 30 minutes, and the second confirmed the issue had been resolved as the affected components returned to normal.

Slack experienced a brief issue affecting iOS users where sending messages could fail or be posted to an unintended thread within Slack's Messaging component. The outage began on 2:39 PM UTC and was resolved by 2:59 PM UTC, lasting about 20 minutes. Slack's status page indicated an investigation and promised updates within 30 minutes; the incident concluded with the Messaging component returning to normal after two official status updates.

Slack reported that legacy webhooks may be causing issues with app configurations, potentially impacting apps and integrations across Slack workspaces. 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. The issue affected the Apps/Integrations/APIs component. Slack issued two status updates during the incident, describing the problem and later confirming resolution.

Slack reported a degraded experience in Workflow Builder, impacting Add spreadsheet row and related steps. Users automating workflows encountered errors like 'The service used for this step isn't available.' The incident began on 7:04 PM UTC and was resolved by 8:35 PM UTC, lasting about 1 hour and 31 minutes. The Workflows component moved from up to warn and back to up, and Slack issued 2 status updates during the incident.

Slack experienced intermittent issues affecting messaging and thread loading starting Jun 6, 2025 4:19 PM UTC when the status page moved from up to warn in some areas. Reports described a persistent 'Join Channel' button sticking for some users after joining a channel and problems loading threads and the Activity view in specific channels. The issues spanned Messaging and Connectivity components and recurred in updates on Jun 9, 2025 6:29 AM UTC and Jun 9, 2025 12:09 PM UTC before improving.

Slack published several status updates as engineers investigated and implemented mitigations, with the service returning to normal by Jun 10, 2025 9:09 PM UTC. User reports were limited but included feedback from Chandigarh about thread loading and messaging performance, helping illustrate the scope of the impact.