Slack experienced a 2.7-hour incident where some users encountered elevated error rates and degradations when sending and receiving messages across the platform. The issue was caused by two database shards becoming overloaded, which led to query failures and messaging problems. The incident was resolved by deploying a fix to the affected shards and unpausing ProcessMessage jobs that had been temporarily halted.
We're investigating a new incident.
We apologize for the inconvenience and will continue sharing updates as they become available.
A fix has been deployed to the affected shards. ProcessMessage jobs had been paused, and these have now been unpaused on the affected shards. We are monitoring performance to assess whether the shards have returned to expected performance levels.
We’re continuing to investigate the issue. We have identified two affected shards that are becoming overloaded, causing elevated query failures and message-related degradations. We are in the process of testing a potential fix. We’ll provide the next update once new information becomes available.
We're investigating a new incident.Current impact to end users: Some users may experience elevated error rates and message-related degradations when sending and receiving messages across the Slack platformTeams are actively engaged to identify the root cause and remediate the service impact and will provide updates as information is available. We apologize for the inconvenience and will continue sharing updates as they become available.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with