Slack experienced a major outage on February 26, 2025, affecting users globally. The issue began around 11 AM ET (4 PM GMT), preventing many from logging in, sending messages, and using workflows. The downtime caused disruptions, particularly for businesses relying on Slack for communication and collaboration.
Users reported being stuck on the login screen, while others could access messages but could not send new ones. Some also faced difficulties with API-related functions and third-party integrations. Reports on Downdetector indicated a spike in complaints, suggesting the issue was widespread. However, we use Slack at GizChina and everything worked as usual, messages, uploads, and voice notes all went through like there was no issue.
Slack gradually restores functionality
As the day progressed, Slack began restoring services, though inconsistencies remained. By the evening, some users were able to log in and send messages, but others still faced issues, especially on desktop. Emoji reactions and other minor functions were also slow to recover.
By 10:30 PM ET, Slack’s status page still showed partial disruptions, particularly in messaging and API-related features. Some users reported being able to send messages on mobile but not on desktop. Others found their accounts logged out and had trouble signing back in, even after restarting their devices.
Company response and ongoing concerns
Slack shared news on the issue and gave updates on its status page. The firm said the problem was due to database shard fails and noted it was focusing on fixes to bring the service back. In a statement, Slack told users it was working fast to solve the issue, adding that full recovery needed careful work on the backend systems. While things got better through the day, the firm said full stability was still not reached. This adds to Slack’s past yearly outages in recent years. Users and firms who depend on the tool may see this as a worry, especially as real-time work tools are key for remote work today.
