Slack Outage History

Slack experienced an outage affecting connectivity to the service, with users reporting trouble connecting to or loading Slack. The outage began on 12:54 AM UTC and was resolved by 5:19 AM UTC, lasting about 4 hours and 25 minutes. The connectivity component was affected, and some users may have been unable to sign in, load channels, or send messages during the incident.

Slack's status page indicated an ongoing investigation with an impact to end users: some users may experience issues connecting to or loading Slack. The service issued 2 status updates over the course of the incident before connectivity was restored.

Slack experienced a brief connectivity issue affecting users' ability to connect to Slack services or causing errors for those already connected. The incident impacted the Messaging and Connectivity components and lasted about 30 minutes, beginning at Nov 6, 2025 1:29 AM UTC and resolving by Nov 6, 2025 1:59 AM UTC.

Slack's status page documented an initial investigation and a later update confirming restoration of services, with two official updates issued during the incident.

Slack's Workflows component experienced degraded performance as External Trigger Schedule Logic runs malfunctioned, making new Data Sources unavailable in the Workflow Builder until the first schema sync completes. This impacted users relying on Workflow Builder features that use external triggers, with new data sources inaccessible during the incident. The issue began at 11:15 AM UTC and was resolved by Nov 5, 2025 1:34 PM UTC, lasting approximately 2 hours and 19 minutes.

Slack experienced a brief degradation of its Search feature, with some users seeing delays or an unresponsive search bar when querying recent messages or files. The incident affected the Search component and lasted about 30 minutes, beginning at 5:34 PM UTC and ending at 6:04 PM UTC. Slack’s status updates acknowledged the issue, noted that the team had identified the problem and were actively working on a fix, and promised another update within about an hour; the Search component returned to normal later in the timeline.

Slack experienced a search-related outage beginning at Oct 29, 2025 5:34 PM UTC after the Slack status page flagged trouble with the Search component, downgraded to a warning. This affected users attempting to locate conversations or files using Slack search, reducing functionality for the duration of the incident. The outage lasted approximately 1 day, 23 hours, 20 minutes, until Oct 31, 2025 4:54 PM UTC when the Search component returned to normal.

Slack issued two status updates during the incident to acknowledge the issue and confirm recovery. User reports from around the world described difficulties with search across channels and messages, indicating a broad but not universal impact during the affected period.

Slack experienced an extended incident starting at Oct 20, 2025 2:59 PM UTC that disrupted core collaboration features. The initial impact was on Huddles, with users reporting they remained stuck in a huddle after attempting to leave. Over the next day, Slack noted degraded connectivity, issues with Apps/Integrations/APIs, and workflows. On Oct 22, 2025 5:04 AM UTC, Search failures were identified, with indexing problems affecting recent messages and files. Later updates around Oct 22, 2025 3:04 PM UTC described intermittent problems with sending messages and loading file previews. The issues appeared to be global rather than isolated to a single region.

Recovery progressed over the next days, with the Huddles component restored by Oct 23, 2025 10:29 PM UTC. Slack's status updates during the incident covered Huddles, Connectivity, Apps/Integrations/APIs, Workflows, Search, Messaging, and Files, indicating a broad, multi-faceted incident. The outage lasted from Oct 20, 2025 2:59 PM UTC to Oct 23, 2025 10:29 PM UTC, with users gradually seeing improvements as components returned to normal following multiple updates.

Slack experienced a multi‑component outage starting on Oct 20, 2025 8:20 AM UTC, with users reporting intermittent issues loading threads, canvases, and messages. The incident affected core features including Huddles, Canvas/Canvases, Connectivity, and Messaging, causing delays in collaboration for about 3 hours and 9 minutes. Slack issued a series of updates as engineers investigated and worked to restore functionality.

The provider issued five status updates over the course of the incident, and by Oct 20, 2025 11:29 AM UTC components began returning to normal. Reports came from multiple regions in Europe (including the United Kingdom, Austria, and Poland), indicating regional impact before broader restoration.

Slack Messaging experienced a brief degradation in performance, affecting messaging delivery for about 30 minutes. The incident began at 5:29 PM UTC and was resolved by 5:59 PM UTC. The Slack status page recorded two updates during the incident, noting a degraded Messaging component followed by restoration to normal service.

Slack experienced a brief disruption to its search functionality, with some searches not completing or returning partial results, and org/workspace dashboards may fail to load. The issue affected the Search component and lasted about 25 minutes, from 4:24 PM UTC to 4:49 PM UTC.

The Slack status page posted two updates during the incident: first at Oct 15, 2025 4:24 PM UTC describing the search failures, and second at Oct 15, 2025 4:49 PM UTC confirming resolution. Users likely experienced intermittent search results and dashboard loading issues during the window.

Slack experienced degraded performance affecting custom-built internal apps and the Apps/Integrations/APIs component. Some custom apps were not functioning and returning errors. The incident began at Sep 27, 2025 12:04 AM UTC and was resolved by Sep 27, 2025 12:49 AM UTC, lasting roughly 45 minutes. The impact was limited to apps and integrations, with core Slack messaging remaining available.

Slack posted two updates during the incident. The first announced an investigation into trouble with custom apps, and the second confirmed the Apps/Integrations/APIs component was restored and the incident resolved.