Slack Outage History

Slack experienced a temporary slowdown in AI Search Answers and AI Explain, with AI-generated summaries taking longer to return results. Other search features remained available. The incident lasted from 3:19 PM UTC to 6:24 PM UTC (about 3 hours 5 minutes), and the Search component was listed as degraded during the period. The Slack status page issued two updates during the incident, beginning with an investigation and followed by a resolution as services returned to normal.

Slack experienced a connectivity incident beginning at 6:29 PM UTC, with some users unable to connect to or load Slack. The outage lasted approximately 2 hours and 5 minutes and was resolved by 8:34 PM UTC. The issue affected the Connectivity component and caused user-facing connection problems during the window.

Slack's status page issued 2 updates during the incident, acknowledging the issue and later confirming restoration. The disruption was limited to connectivity for Slack, with other functionality remaining available.

Slack experienced a brief issue where some users saw a blank login page when attempting to sign in, preventing access to Slack workspaces. The problem affected the Login/SSO component. The incident began at 10:29 PM UTC and was resolved by 11:24 PM UTC. Slack posted two updates during the outage, noting that they were investigating the issue and later confirming it was resolved. A workaround was provided: if you encounter a blank page, go to slack.com and select your workspace to reveal the login form.

Slack experienced connectivity issues affecting the ability to connect to or load Slack. The incident began at 12:54 AM UTC when Slack’s status page moved to a warning with the message 'Trouble connecting to or loading Slack.' Some users reported problems accessing the app or loading messages. The outage lasted approximately 4 hours and 25 minutes and was resolved by 5:19 AM UTC. The event involved the Connectivity component and was accompanied by limited user reports across the period. The provider issued two status updates during the incident, reflecting ongoing connectivity concerns before restoration.

Slack’s connectivity disruption was documented as a partial outage affecting user access rather than a full service downtime. Access was restored after the final update, and the status returned to up.

Slack experienced a brief connectivity disruption starting at Nov 6, 2025 1:29 AM UTC, with users reporting they could not connect to Slack services or were seeing errors when already connected. The issue affected two components, Connectivity and Messaging, resulting in degraded performance and intermittent access for a short period.

Slack's status page described the incident as a connectivity issue and noted ongoing investigation. The problem was resolved by Nov 6, 2025 1:59 AM UTC with services restored. The provider issued 2 status updates during the incident, and the outage lasted about 30 minutes.

Slack's Workflow Builder data sources were temporarily unavailable due to an issue with External Trigger Schedule Logic runs, causing new Data Sources to be unavailable until the first schema sync completes. This disrupted automation for users relying on Workflow Builder, as new data sources could not be created or used during the incident.

Timeline and communication: The issue was identified around 11:15 AM UTC. Slack listed a degraded state for the Workflows component at Nov 5, 2025 1:04 PM UTC, with restoration reported by 1:34 PM UTC. The status page included 2 updates during the incident.

Impact and duration: The impact appeared focused on the Workflows component, with no indication of broader Slack service disruption. The outage lasted approximately 2 hours and 19 minutes, ending with data source availability restored for new Workflow Builder data sources.

Slack experienced a brief degradation of the Search feature, starting at Nov 3, 2025 5:34 PM UTC with some users reporting delays or an unresponsive search when looking for recent messages or files. The issue was logged as Search Failures on Slack's status page and was resolved by Nov 3, 2025 6:04 PM UTC. The incident affected the Search component and led to slower or stalled search results for about 30 minutes before service returned to normal. Slack issued updates acknowledging the investigation and later confirming resolution.

Slack experienced issues with its search feature, preventing some users from locating messages. The problem affected the Search component and disrupted workflows that rely on finding past conversations. The outage began at Oct 29, 2025 5:34 PM UTC and persisted until Oct 31, 2025 4:54 PM UTC when it was resolved.

Slack posted two official updates during the incident, first acknowledging an ongoing investigation and later confirming resolution. The incident lasted about 47 hours and 20 minutes.

Slack users faced interruptions across several features, most notably huddles where some participants could not exit and remained stuck, and intermittent problems with search indexing and file previews. The issues affected seven Slack components: Huddles, Messaging, Files, Search, Connectivity, Apps/Integrations/APIs, and Workflows. End users experienced difficulties leaving huddles, sending messages, and loading file previews or search results during the incidents.

Slack users experienced intermittent loading issues affecting multiple features, including threads, canvases, and Huddles. Users reported difficulties sending messages and using various components such as Connectivity, Messaging, Login/SSO, Notifications, Search, Files, Apps/Integrations/APIs, Workflows, and Workspace Administration, indicating a broad but not complete disruption. Observations came from Europe, with reports from Slough (UK), Vienna (Austria), and Poznań (Poland).

Slack began communicating the incident at Oct 20, 2025 8:20 AM UTC and issued a total of five status updates as engineers worked to restore services. The outage was resolved by Oct 20, 2025 11:29 AM UTC, with affected components returning to normal. The outage lasted about 3 hours and 9 minutes and stages moved from initial warning to partial recovery over the course of the incident.