Monday August 25, 2025

Summary

Beginning at 2:03 PM PDT on August 25, 2025 until 2:27 PM PDT, some users may have experienced trouble loading threads in Slack, resulting in a "Something's fishy!" message.

A backend capacity change unexpectedly caused a subset of databases to enter a bad state preventing traffic related to loading thread content from being served properly. The affected databases would accept new entries, but were temporarily unable to read thread content, resulting in errors.

We reversed the changes that caused the bad state, restoring all functionality to affected users.

6:00 PM PST

Resolved

This issue is now resolved for all users.

• Current status and recent actions taken: We identified the cause of the issue and implemented a fix to restore thread functionality.
• Scope: This affected a portion of users globally.
• Previous impact to end users: Some users may have had trouble loading threads in their Slack clients. This resulted in a "Something's fishy!" error message.
• Required resolution steps: No required steps, if users are experiencing any trouble, they may consider hard-refreshing their app via Cmd/Ctrl + Shift + R.

We apologize for any disruptions to your day.

2:53 PM PST

Investigating

We're investigating a new incident.

• Current impact to end users: Some users may experience trouble loading threads and receive a "Something's fishy!" error message instead. We're investigating the issue.

We'll provide an update within 30 minutes including further details on current actions being taken.

2:28 PM PST