Slack Outage History

Slack experienced degraded performance with trouble loading and performing actions across the platform. Users reported issues related to App Management, and the incident affected multiple Slack components, including Apps/Integrations/APIs, Workspace/Org Administration, Login/SSO, and Messaging, leading to delays and partial functionality for app management tasks and related features.

The Slack status page documented an upstream provider issue causing email delivery delays, with updates issued throughout the incident. The issue involved several components and persisted from 7:44 PM UTC until it was resolved by 8:14 AM UTC, spanning roughly 12 hours and 30 minutes. The provider released 8 status updates during the incident, and services returned to normal after the upstream issue was addressed.

The Slack checkout flow experienced a partial outage affecting the ability to add new payment methods. Affected users globally encountered errors during checkout, with the issue traced to the Workspace/Org Administration component. The incident began on Jan 14, 2026 9:24 PM UTC and lasted until Jan 14, 2026 11:24 PM UTC, spanning roughly 2 hours.

Slack posted three official status updates during the incident. The initial warning appeared at Jan 14, 2026 9:24 PM UTC, followed by a mid-incident note at Jan 14, 2026 11:19 PM UTC indicating ongoing fixes with no ETA. The issue was resolved by Jan 14, 2026 11:24 PM UTC, with the Workspace/Org Administration component returning to normal.

Slack experienced a brief outage affecting Connectivity and Messaging components. The incident began at Jan 8, 2026 10:34 PM UTC and was resolved by Jan 8, 2026 11:44 PM UTC, lasting roughly 1 hour and 10 minutes. Slack issued two status updates during the incident to document the degraded state and subsequent restoration, with the outage appearing limited to these components and not indicating broader service-wide impact.

Slack experienced a brief issue loading thread conversations, impacting how users view and participate in threaded messages. The incident began at 12:34 AM UTC and was resolved by 2:10 AM UTC, lasting about 1 hour and 36 minutes. The problem was centered on the Messaging component and affected threaded conversations across the platform. The service issued updates at Dec 24, 2025 12:34 AM UTC and Dec 24, 2025 2:04 AM UTC describing the issue and progression toward resolution, with the incident closed by Dec 24, 2025 2:10 AM UTC.

Slack experienced degraded performance impacting Workflows and Apps/Integrations/APIs. The incident began at 5:14 PM UTC and was resolved by 9:54 PM UTC, lasting about 4 hours and 40 minutes. Users attempting automated workflows or using third-party app integrations may have experienced interruptions during this period.

Slack's status page documented the degraded state for the affected components, with two official status updates issued during the incident. The issue was subsequently resolved and services returned to normal operation.

Slack Threads loading and viewing issues disrupted messaging across Slack clients, with users experiencing difficulty when opening or following threaded conversations. The degradation affected the Messaging component (Threads) and persisted for most of the incident.

The incident began at Dec 8, 2025 11:29 PM UTC when Slack reported a degraded state, followed by updates at 6:59 AM UTC and 5:34 PM UTC. The service was restored with the status returning to up at 5:39 PM UTC. The outage lasted approximately 18 hours and 10 minutes, during which Slack issued four status updates describing the investigation and resolution.

Slack users worldwide experienced slow behavior and delays for certain actions, with the Search component listed as degraded. Users reported longer response times when performing searches and other interactions, indicating degraded performance across the platform. The issue persisted for most of the day, lasting from 4:29 AM UTC to 9:14 PM UTC.

The outage began on 8:09 PM UTC and was resolved by 6:04 AM UTC, lasting approximately 9 hours and 55 minutes. Slack reported a search-related incident affecting the Search component, with users potentially experiencing increased latency or errors when attempting to search.

Slack experienced a partial outage beginning at 10:44 AM UTC, with a subset of users unable to sign in and intermittent connectivity to Slack features.

During the incident, Slack published three status updates. A mid-incident update around 11:39 AM UTC noted problems with Login/SSO for some users while Connectivity was affected. Login/SSO recovered, and Connectivity returned to normal by 12:54 PM UTC. The total duration was about 2 hours and 10 minutes, and the issue impacted two components: Login/SSO and Connectivity.

Slack experienced a brief sign-in issue affecting a subset of users, tied to the Login/SSO component. The outage began on 11:34 PM UTC and was resolved by 12:09 AM UTC, lasting about 35 minutes. During this window, some users were unable to sign in to Slack. Slack issued an initial status update acknowledging the sign-in problem and promising more details, followed by a second update confirming the service had returned to normal as the Login/SSO component stabilized.