The issue with user statuses showing incorrectly has been resolved. We appreciate your patience as we worked to get things back in order.

We've resolved the issue some users were experiencing related to Slack apps/integrations displaying an error message when selecting dropdown options. Affected users may need to refresh their client (Cmd/Ctrl + Shift + R) to capture the fix. We apologize for the trouble, but appreciate you bearing with us as we worked to get things back in order.

Starting around 12:00 AM PDT on August 23, 2025 until around 12:13 AM PDT on August 25, 2025, a small subset of enterprise users may have experienced trouble connecting to or loading Slack.We determined this was caused by a routine enterprise migration system that encountered latency when processing backend jobs. This latency caused some migrations to run longer than scheduled, directly impacting affected users' ability to connect.After partnering with an upstream provider to investigate, we adjusted the problematic job processes to reduce latency, restoring full functionality to all affected users.

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.

From around 11:30 PM PDT on August 14, 2025, to around 4:00 AM PDT on August 15, 2025, some users in the Central Europe regions may have experienced trouble loading content in Slack, specifically the list of items like DMs or channels in their sidebar or content in conversations, such as messages.A backend caching system encountered stale configuration data, resulting in errors when attempting to fetch conversation & sidebar content.To quickly mitigate impact, we redirected traffic away from the problematic service area while we implemented a fix to the caching system. Once the fix was confirmed, traffic was restored, returning functionality for all affected users.