Slack Outage History

Slack faced APAC connectivity issues, with some users unable to load Slack.

The impact affected four Slack components across the Asia-Pacific region, including Connectivity, Search, Apps/Integrations/APIs, and Login/SSO, with users in the Philippines also experiencing problems. Slack issued six status updates during the incident, which began on Jul 27, 2025 12:54 AM UTC and was resolved by Jul 30, 2025 9:44 PM UTC.

The updates described ongoing investigations and intermittent issues such as app refresh events, and Slack reported restoration of services as components returned to normal.

Slack experienced a brief outage where the See More button stopped working for messages from apps and integrations, preventing loading of extended content. The issue affected the Apps/Integrations/APIs component and persisted from 7:04 AM UTC to 8:59 AM UTC, lasting about 1 hour and 55 minutes before services returned to normal. Slack issued two status updates during the incident to acknowledge the problem and confirm resolution.

The Slack status page reported intermittent trouble with enterprise search and several integrations, including workflow connectors. This caused degraded functionality for users relying on search and connected apps. The problem began at Jul 18, 2025 4:54 PM UTC and was resolved by Jul 18, 2025 6:19 PM UTC.

Slack described the issue as related to an upstream provider problem, affecting the Search component and Apps/Integrations/APIs. The incident lasted about 1 hour and 25 minutes and included two official status updates on the Slack status page.

Slack experienced a multi-component incident starting at 6:54 PM UTC, with degraded third-party app message components that could produce an invalid argument error when using the block suggestion API. By 8:44 PM UTC, the impact extended to workspace invites, causing new users to see a greyed-out Invite button and preventing account creation. A subsequent update confirmed ongoing issues with core components before some recovery began on 2:09 PM UTC. The incident affected several Slack components, including Apps/Integrations/APIs, Login/SSO, and Workspace/Org Administration. Slack issued five official status updates across the incident, with recovery observed by 2:09 PM UTC as components moved back to up. The outage lasted roughly 19 hours and 15 minutes, affecting user experiences around app integrations and onboarding flows on a global scale.

Slack reported issues affecting some third-party apps, with connection problems and potential invalid argument errors in the Block Suggestions API. The event was tracked under a degraded state for Apps/Integrations/APIs, impacting developers and workflows relying on Slack integrations. The incident underscores how external app connections can affect overall productivity when integration APIs behave unexpectedly.

The Slack search feature on api.slack.com experienced degraded performance with server errors when performing searches or loading results. API documentation search also faced issues, hindering users from locating resources. The disruption affected two components: the Search service and the Apps/Integrations/APIs group. The incident began at 4:39 AM UTC and was resolved by 9:59 PM UTC, lasting roughly 17 hours and 20 minutes, with Slack providing three updates to communicate investigation progress and recovery.

During the incident, Slack continued to publish status updates detailing ongoing investigation and paths toward resolution, until the issue was cleared and services returned to normal.

Slack experienced a brief degradation in image and file uploads affecting the Files component. Uploads could appear stuck or continue loading for some users. The incident began at 7:09 PM UTC and was resolved by 9:05 PM UTC, lasting approximately 1 hour and 56 minutes. Slack posted two status updates during the incident, acknowledging the issue and providing progress as engineers investigated before service was restored.

Slack experienced a partial outage affecting search functionality and related admin workflows. Some users reported that searches did not return results and admin pages such as Managing Members could be impacted. The incident began at 7:24 PM UTC and lasted until 10:09 PM UTC, a duration of about 2 hours and 45 minutes. A sample user report from Los Baños, Philippines at 7:28 PM UTC described 'Unable to Search'. Slack issued 2 status updates during the incident as they investigated and iterated on remediation.

Slack reported a brief incident where messages on iOS were not sending correctly, including thread replies being posted to the wrong thread. The issue affected the Messaging component and lasted about 20 minutes. The incident began at 2:39 PM UTC and was resolved by 2:59 PM UTC. Slack issued 2 status updates during the incident.

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.