Slack outage on December 29, 2025
Slack users likely saw failed connections, degraded availability, or session instability for this Productivity service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.
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.
Deterministic readout · awaiting AI summary pass
Incident detected
Minor confidence crossed the incident threshold for Incident: Issue loading threads in Slack.
Marked resolved
The incident was closed after 45 min of observed impact.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
25.00The incident reached 25.00 peak confidence across available stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
0 affectedThe incident row exists, but the bounded snapshot window does not include affected status samples.
Recovery signal
ResolvedRecovery was recorded at Mon, Dec 29, 2025, 06:34 PM UTC.