Downrightnow
// Incident Post-MortemDRN-1104AD54

Slack outage on December 18, 2025

Minor severityResolved45 minProductivity
Started · UTC
Dec 18, 04:44 PM
212d ago
Resolved · UTC
Dec 18, 05:29 PM
212d ago
Duration
45 min
End-to-end
Peak confidence
25.00
0 snapshots
// User impact

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.

// What happened

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.

Deterministic readout · awaiting AI summary pass

// Timeline
  1. Incident detected

    Minor confidence crossed the incident threshold for Incident: Issues loading or viewing threads.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

25.00

The incident reached 25.00 peak confidence across available stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Thu, Dec 18, 2025, 05:29 PM UTC.