Slack down full#

If you'd like to receive a full Root Cause Analysis (RCA) report, please reach out to to request one. We continued to closely monitor the situation until we had full confidence the issue was resolved and no further impact would reoccur. By 9:14 AM PST, everyone should have been able to connect to Slack again after reloading their app or browser tab. This allowed the system to recover while steadily restoring full access to all users. With traffic distributed across the additional databases, we gradually lifted the rate limits to allow more people to connect to Slack. We reinstated the rate limits and redirected some traffic to the database replicas to relieve the demand on our primary databases. Most of my company have spotty connection. I guess it was down so they could do this crappy update. However, we moved too quickly and the increased activity affected the system again. Slack was down to me, and now that it is back, it is begging me to subscribe to use paid features, with the nag screens blocking my view of important stuff.

Once the system had stabilized, we began lifting these rate limits to enable more connections to Slack. This meant that some people could not access Slack at all, but also that Slack would continue working for those who were already connected. We introduced tighter rate limits on connection requests to reduce the load on the system. Due to this increased activity, the affected databases failed to serve incoming requests to connect to Slack. Other online platforms including GitHub and Amazon Web Services also appear to be experiencing outages. You can check the status of Slack on the platform's website, here. Statistics show that the outages began around 8:30 a.m. Collected using a 10 sample of all teams. A live outage map showed that the issues predominantly occurred in northern America. Comparison of memory usage at p10, p50, p90, and p99 for a single team running the full client (left) and minimal client (right). On Februfrom 6:00 AM PST to 9:14 AM PST, customers may not have been able to access Slack.Ī configuration change inadvertently lead to a sudden increase in activity on our database infrastructure. This helps to reduce the overall footprint of the app and release resources back to the operating system to improve performance for the teams you are actively using.

Slack down