All's good under the hood, boss!

The underlying issue has been resolved and all users should be connected without issue.

We stopped a job that was causing pain to our databases. Now that they've recovered, all teams should be able to log into and use Slack normally. We apologize for any inconvenience!

All teams should be able to connect to Slack now. We apologize for the inconvenience!

We are working to resolve a connectivity disruption a small number of teams may be experiencing.

We've reverted a code change released at 9:23am PST that caused login requests to get very slow and have observed that teams are once again able to login. The change that was reverted introduced a dependency on our search infrastructure at login which was unnecessary and has now been removed.

First, we apologize again for the disruption this outage has caused. Here's a quick summary of what happened: Today, from 6:40am PST to about 10am PST Slack was down or slow for all customers. This was due to a slight decrease in database performance which exhausted all available capacity to answer requests and resulted in a large percentage of requests — signing in, sending messages, reacting, uploading files, and so on — failing.

Service was restored around 10am PST. None of your messages were lost but they remained queued for processing longer than usual. All messages sent during the incident have been processed now. We have taken several steps to address the issues and will be making these changes permanent in order to prevent similar incidents in the future. As always, we will continue to monitor the health of Slack and invite you to write to [email protected] if you have problems. Thank you again for your patience and apologies for the disruption ahead of the holidays.

Issue resolved; All users and teams should be able to connect to slack.

All service should be restored to affected teams. Once again, we apologize for any inconvenience this may have caused.