Slack Outage History

Some users in the EMEA region experienced failures receiving SMS-based 2FA codes when attempting to sign into Slack, preventing them from completing the login process. The incident affected the Login/SSO component and lasted 38 minutes. The issue was investigated and resolved, though specific resolution details were not provided in the available updates.

Slack experienced a 1.1-hour incident where administrators encountered errors when managing members, sending invites, or running macros on their workspaces due to a recent system change. The issue affected workspace and organization administration functions, preventing some admins from adding new members via the Admin page. Slack identified the problematic change and resolved the incident by rolling it back, while users could work around the issue by inviting members through the Slack client workspace menu.

Slack experienced a 52-minute service incident where some users encountered trouble loading or connecting to the platform, including thread loading failures, client booting issues, and message delivery problems. The incident affected Slack's connectivity and messaging components. The issue was investigated with multiple potential contributing factors identified, and service was restored after the investigation was completed.

Slack experienced a 59-minute partial service degradation affecting usergroups, caused by a recent deployment. Users encountered issues with user groups including failed @mentions and groups appearing unavailable. The incident was resolved after Slack identified the deployment trigger and restored functionality.

Slack experienced severe latency issues affecting all services including messaging, notifications, login, files, and integrations for 26 minutes. All core Slack functionality was impacted by the performance degradation. The incident was investigated and resolved by the Slack Engineering team.

Slack experienced a 16.4-hour service incident affecting workflows, messaging, apps/integrations/APIs, and canvases, with users unable to edit messages, rename channels, create channels, manage permissions, update statuses, or save canvas edits. The incident involved two phases: an initial disruption affecting core functionality like workflows and messaging that was largely resolved after several hours, followed by a secondary issue causing persistent permissions-related problems and canvas editing failures. Resolution required multiple configuration adjustments and deployments over an extended period to fully restore all affected services.

Slack experienced a global issue where users encountered slow or failing file and emoji uploads due to a frontend error. The problem affected file attachments and emoji uploads, causing them to take longer than expected or fail to complete. Slack identified the root cause, deployed a fix, and was monitoring the environment to confirm full resolution of the 1.6-hour incident.

Slack experienced a 1-hour incident affecting file uploads, message edits, channel renames, channel creations, and third-party integrations, with users reporting inability to send files, GIFs, screenshots, and various app/messaging errors. The issue was caused by resource exhaustion and connectivity failures in internal infrastructure components responsible for processing background tasks. The incident was resolved by reverting a recent configuration change, which stabilized the affected systems and reduced error rates.

Slack experienced elevated error rates and latency affecting Enterprise Key Management (EKM) customers globally, causing issues with sending messages and loading channels. The incident impacted messaging, connectivity, files, and apps/integrations/APIs components. The service disruption lasted 12 minutes and was classified as a minor incident.

Slack customers using Enterprise Key Management (EKM) experienced issues with sending messages, loading channels, and delays with notifications and activity feeds due to problems with an upstream provider. The incident initially appeared resolved around 11:10 AM PDT but then recurred with elevated error rates and latency affecting EKM customers globally. Slack deployed cache configuration fixes and worked with their upstream provider who implemented a resolution, with error rates eventually returning to normal levels.