Slack Outage History

Slack experienced a minor service incident where some users, particularly those on Windows and Chrome, were unable to load Threads and received "Try Again" error messages. The connectivity issues affected the Threads feature specifically, preventing users from accessing threaded conversations. The incident lasted 2.5 hours with Slack investigating throughout the duration.

Slack experienced an issue where custom statuses set to expire at specific times were not automatically clearing as expected. The problem affected the messaging component and impacted users who relied on automatic status expiration functionality. The incident lasted 2 hours and was classified as a minor service disruption.

Slack experienced a messaging service incident where some users globally had trouble sending messages for 2.6 hours. The engineering team identified and deployed a fix by processing affected service PODs, which resulted in significant recovery across the platform. The incident was resolved after monitoring confirmed system stability was restored.

Slack experienced an 11.6-hour incident where users encountered intermittent issues with Slackbot responses and AI-powered features including Search Answers, Meeting Notes, Translation, and Workflows. The problem was initially caused by a third-party infrastructure issue, but secondary caching problems prolonged the outage even after the upstream provider resolved their issues. Slack resolved the incident by deploying configuration fixes and an emergency fix to address the caching issues, with significant recovery observed across all affected services.

Slack experienced an issue where the Slackbot button in the top navigation bar disappeared for users on build 121247, with some users also reporting problems with updates not displaying properly without closing and reopening the application. The incident affected Apps/Integrations/APIs and Messaging components for 1.7 hours. Slack identified the cause, deployed a fix, and resolved the issue, though some users needed to reload Slack for the button to reappear normally.

Slack experienced a 2.7-hour incident where some users encountered elevated error rates and degradations when sending and receiving messages across the platform. The issue was caused by two database shards becoming overloaded, which led to query failures and messaging problems. The incident was resolved by deploying a fix to the affected shards and unpausing ProcessMessage jobs that had been temporarily halted.

Slack experienced a messaging incident where some users had difficulty sending messages and loading message history due to high resource utilization on Slack's systems. The issue affected only a small subset of users, who could work around the problem by retrying failed message sends or history loads. The incident lasted 1.5 hours while Slack's team investigated logs and diagnostic information to resolve the underlying resource constraints.

Slack experienced connectivity issues that prevented some customers from loading certain features, including activity and notification badge counts, and caused errors when using the service. The incident affected notifications and general connectivity for 1 hour. The team resolved the issue by rolling back a recent feature change and increasing infrastructure capacity to restore normal service levels.

Customers experienced authorization failure errors when attempting to connect to the Slack MCP server, affecting third-party Slack integrations and the Apps/Integrations/APIs component. The incident lasted 1.1 hours while Slack investigated and resolved the connectivity issues.

Slack experienced intermittent SSO login failures that prevented some users from accessing their workspaces for 2.4 hours. The issue specifically affected the Login/SSO components, causing authentication problems for users attempting to sign in. The incident was classified as minor and the team worked to investigate and resolve the login failures.