Slack Outage History

Slack experienced a thread loading issue within the Messaging component, preventing threaded conversations from rendering for users. The outage began at 12:34 AM UTC and was resolved by 2:10 AM UTC, lasting about 1 hour and 36 minutes. Slack issued three status updates during the incident, acknowledging the problem, noting ongoing investigation, and confirming resolution.

Impact was limited to the threads feature in Slack's Messaging component, with users potentially unable to load or participate in threaded conversations.

Slack experienced degraded performance affecting Workflows and Apps/Integrations/APIs, with some users reporting intermittent automation and integration issues. The incident began at 5:14 PM UTC when Slack moved into a degraded state and lasted until 9:54 PM UTC, a duration of about 4 hours and 40 minutes. A user in Belgrade, Serbia reported issues during the incident, indicating limited but noticeable impact for a subset of users.

Slack's status page documented the degraded period for the two components, and updates were provided as the incident progressed. The incident was resolved with the affected components restored to normal by 9:54 PM UTC.

The Slack Threads issue affected the Threads feature within Slack's Messaging component, causing users to experience difficulties loading or viewing threads. The incident began at Dec 8, 2025 11:29 PM UTC and was resolved by Dec 9, 2025 5:39 PM UTC, lasting roughly 18 hours and 10 minutes. The issue appeared to be isolated to Threads, with other Slack functionality unaffected. Affected area included the Messaging: Threads pathway.

Slack issued 4 status updates documenting the incident. Updates progressed from an initial notification about a Threads issue to follow-ups noting that loading or viewing threads was impacted, with the service returning to normal after the final update at Dec 9, 2025 5:39 PM UTC.

Slack experienced slow behavior with delays when performing actions, affecting users across the platform. The Search component was specifically listed as degraded, impacting search-related workflows for some users. The issue appeared to be broader than a single feature, with multiple actions experiencing latency.

Slack experienced an incident affecting the Search component, with end users seeing latency or errors when attempting to search. The issue was limited to search and did not indicate a broader Slack outage. The outage began on 8:09 PM UTC and lasted approximately 9 hours and 55 minutes, with the Search feature returning to normal by 6:04 AM UTC. The incident involved 2 official status updates from Slack during its course, detailing the investigation and subsequent resolution.

Slack experienced a partial outage affecting a subset of users attempting to sign in. The Login/SSO component entered a degraded state at 10:44 AM UTC, with an update at 11:39 AM UTC noting that some users could not log in or access certain features while the issue was investigated. A follow-up update indicated that Login/SSO had recovered, but Connectivity remained degraded for a period. The incident involved two components and impacted user access to Slack services for a couple of hours. The outage began on 10:44 AM UTC and was resolved by 12:54 PM UTC.

Slack experienced an outage affecting sign-in for a subset of users, with some users unable to sign in. The Login/SSO component was listed as degraded. The incident began at Nov 20, 2025 11:34 PM UTC and was resolved by Nov 21, 2025 12:09 AM UTC, lasting about 35 minutes. Slack posted two status updates during the event: an initial notice about login difficulties and ongoing investigation, followed by a confirmation that the issue was resolved and services were back to normal. The impact appeared limited to the sign-in flow, with no broader outages reported.

Slack's AI search and AI Explain features experienced slowness, causing delays in AI-generated results. Other Slack search functions remained available. The incident began at Nov 12, 2025 3:19 PM UTC and was resolved by Nov 12, 2025 6:24 PM UTC. The Slack status page issued 2 updates, with the Search component listed as degraded before returning to normal. The impact was limited to AI-powered search tasks while standard search continued functioning.

Slack experienced a brief connectivity disruption that prevented some users from connecting to or loading Slack. The outage began on Nov 10, 2025 6:29 PM UTC and was resolved by Nov 10, 2025 8:34 PM UTC, lasting a little over two hours. During the incident, the Connectivity component was listed as degraded, and some users reported intermittent access.

The Slack status page documented the incident as an investigation with the impact described as 'Some users may have trouble connecting to or loading Slack.' Slack issued two official status updates as the situation progressed, and connectivity was restored by the end of the window.

Some Slack users were unable to sign in due to a blank login page, affecting the Login/SSO component. The issue prevented access to Slack across workspaces, and Slack advised a workaround: visit slack.com, select your workspace, after which the login page for all workspaces should appear.

The incident began on 10:29 PM UTC and was resolved by 11:24 PM UTC, lasting about 55 minutes. The Slack status page published two updates during the incident to acknowledge the issue and confirm restoration of the login flow.