Slack experienced a minor incident on March 29, 2026 affecting Messaging, lasting 2h 38m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 29, 2026, 10:38 PM UTC
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.
- identified Mar 29, 2026, 11:30 PM UTC
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.
- monitoring Mar 30, 2026, 12:29 AM UTC
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.
- monitoring Mar 30, 2026, 01:17 AM UTC
Following a period of monitoring, our engineering team called this incident resolved as of 01:10 UTC, March 30. We apologize for any inconvenience this issue has caused to users.