Slack login, workspaces loading failures, and general Slack functionality issues

Update timeline

1. investigating Nov 28, 2025, 10:44 AM UTC

   We are currently investigating an issue where a subset of users may be unable to log into Slack or use certain features. We apologise for the inconvenience and will provide another update as soon as we have more details to share.

2. identified Nov 28, 2025, 11:16 AM UTC

   We have identified an unhealthy database that is contributing to the current issue. We are working on restoring the database to a healthy state, which we anticipate will resolve the problem. We will update you as soon as we have more information.

3. investigating Nov 28, 2025, 11:46 AM UTC

   We are actively working to resolve the current platform functionality issues, which have evolved to include connectivity problems, workspace loading failures, and server errors for some users. Our current efforts remain focused on restoring the unhealthy database identified earlier. We will update you as soon as we have more information.

4. investigating Nov 28, 2025, 12:18 PM UTC

   We’ve also noticed instances getting out of memory errors, causing system instability. We are provisioning the service to larger and more stable servers. We continue to monitor everything for stability. We will update you as soon as we have more information.

5. investigating Nov 28, 2025, 12:54 PM UTC

   Service has been fully restored for all affected users. The database connection issue, which was caused by high memory usage, was resolved by upscaling server capacity. All Slack features and functionalities are now loading correctly. We apologize for the disruption and thank you for your patience while we resolved this incident.

6. resolved Dec 01, 2025, 05:19 PM UTC

   Starting around 1:45 AM PST until 4:30 AM PST on November 28, 2025, some users encountered connectivity issues, including difficulty accessing and loading their workspaces and receiving "Server error" messages. We traced this issue to a backend database service reaching unexpected capacity limits, which led to a spike in error rates and request timeouts. We immediately increased capacity limits for the affected databases, restoring full functionality and service stability to all impacted services.