Slack experienced a minor incident on December 24, 2025 affecting Messaging, lasting 5d 17h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 24, 2025, 12:33 AM 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 regret any inconvenience this is causing.
- resolved Dec 24, 2025, 02:04 AM UTC
This issue is now resolved for all users. Current status and recent actions taken: Threads should now load normally for all impacted users. To restore normal thread performance, we redirected traffic away from the affected database shard and then scaled up its capacity.Scope: A small number of users may have had trouble with threads.Previous impact on end users: Threads may have failed to load or resulted in a "Something's fishy!" error message.Required resolution steps: No additional steps are necessary.We apologize for any inconvenience this may have caused to your day
- resolved Dec 29, 2025, 05:49 PM UTC
Between 1:05 PM and 5:26 PM PST on December 23, 2025, some users may have encountered a "Something's fishy!" error when attempting to load message threads. We traced this to a backend job that consumed an excessive amount of system resources, leading to a portion of a database becoming unresponsive. To mitigate, we optimized the resource allocation for these background tasks and restarted the affected database segments, resolving the issue for affected users.