Slack experienced a minor incident on December 8, 2025 affecting Messaging, lasting 9d 17h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 08, 2025, 11:23 PM UTC
We are aware of an issue currently impacting threads. Our teams are investigating, and we will provide more information as soon as it’s available. We’re very sorry for any inconvenience this is causing.
- resolved Dec 09, 2025, 06:55 AM UTC
Our work on this issue is still ongoing. Current status and actions being taken: We have no additional news to share at this time, but we’re focused on getting things back to normal as quickly as possible.We'll be back with another update as soon as we have news to share.
- resolved Dec 09, 2025, 04:55 PM UTC
We've identified the cause of the issue and implemented a fix. We're currently monitoring internal health metrics & user reports, but will provide an update once we've determined this issue is fully resolved. We appreciate your patience as we sort this out.
- investigating Dec 09, 2025, 05:34 PM UTC
We've resolved the issue with threads not loading for some users. We apologize for any disruptions to you day.
- identified Dec 18, 2025, 04:44 PM UTC
From 7:12 AM to 4:50 PM PST on December 8, 2025, some users encountered a "Something's fishy!" error when loading threads or experienced delays or a blank screen when loading specific channels in Slack. We identified the cause as a recent configuration change that triggered unexpected rate limiting on backend components responsible for fetching message data for threads. We reverted the problematic change, resolving the issue for all users.