Sunday August 24, 2025

Summary

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.

6:15 PM PST

Resolved

This issue is now resolved for all users.

• Current status and recent actions taken: Manual mitigation efforts have restored the scheduled migrations. Additional capacity was also added to accommodate increased read/write throughput. The migrations are now expected to proceed as expected.
• Scope: Users of standalone workspaces with scheduled migrations.
• Previous impact to end users: Some of the scheduled migration windows may have overrun, and users may have experienced issues while connecting to or loading Slack.

We apologize for any disruptions to your day.

8:54 AM PST

Cause Identified

We’re still actively investigating this issue

Current status and actions being taken: We identified the cause of the issue and have initiated manual remediation efforts to restore functionality.

Estimated time to resolution: No estimated time.

Scope: Users of standalone workspaces that have a scheduled migration window.

Current impact to end users: The scheduled migration windows may overrun, and users may experience issues connecting to or loading Slack.

We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
We appreciate your patience as we sort this out.

8:32 AM PST

Investigating

We are investigating an issue where some users of standalone workspaces may be experiencing issues connecting to or loading Slack. We apologize for the disruption. We are working to resolve this as our highest priority, and we'll provide another update in 30 minutes.

8:00 AM PST