Monday November 10, 2025

Between 10:10 AM PST and 10:25 AM PST on November 10, 2025, some users may have temporarily been unable to connect to Slack or experienced a degree of latency when attempting to use features such as huddles, workflows, or message delivery.

We traced this back to a spike in traffic to core backend Slack functions. This traffic temporarily overwhelmed a subset of backend components, leading to brief increase in connection failures. The traffic spike subsided and connectivity was restored for all users by around 10:25 AM PST. To mitigate the risk of reoccurrence, we adjusted backend traffic routing rules to relieve affected systems and continued closely monitoring our health metrics. We determined the issue was fully resolved and necessary measures were in place by 12:30 PM PST.

We continue to implement additional measures to reduce the likelihood of this recurring in the future.

9:19 AM PST

This issue is now resolved for all users.

• Current status and recent actions taken: Our health metrics indicate that users are no longer impacted. We’ve also implemented additional steps to help reduce the likelihood of this issue recurring.
• Scope: A small number of users may have experienced issues connecting to or loading Slack, while other users may have remained connected, but experienced issues completing some actions.
• Previous impact to end users: Trouble connecting to or loading Slack, sending or receiving messages, and issues with some features like search or workflows.
• Required resolution steps: No steps to share.

We apologize for any disruptions to your day.

12:32 PM PST

Our work on this issue is still ongoing, though we have no new updates to share just yet.

• Current status and actions being taken: We’re continuing to work toward a full resolution and continue to see successful connection to Slack services.

We'll provide another update once this is resolved for all users.

12:00 PM PST

Our work on this issue is still ongoing and our health metrics continue to indicate improvement.

• Current status and actions being taken: Affected users may be able to connect and use Slack as normal, but we continue to closely monitor as we work to fully resolve this.

We'll provide another update in 30 minutes until impact is resolved for all users, we appreciate your patience as we sort this out.

11:39 AM PST

We've identified the cause and are seeing signs of improvement. Users may be able to connect to Slack again, but we're still working toward a full resolution.

• Current status and actions being taken: We're continuing to monitor our health metrics as we work to mitigate full impact and help reduce the likelihood of this recurring.
• Estimated time to resolution: No current time to share.
• Scope: A small number of users may have temporarily been unable to connect to Slack; other users may have remained connected but experienced performance delays.
• Current impact to end users: Some users may be able to connect to Slack once again. Previously, affected users encountered issues connecting to or loading Slack, or experienced delays in completing actions (e.g., sending messages, performing searches, or using workflows).
• Known workarounds: No known steps to share.

We'll continue to provide updates every 30 minutes until the impact is resolved for all users.

11:05 AM PST

We're investigating a new incident.

• Current impact to end users: Some users may have trouble connecting to or loading Slack.

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

10:26 AM PST