Thursday October 29, 2026

Resolved

This issue is now resolved for all users.

• Current status and recent actions taken: <What actions we've taken leading to the resolution, any ongoing actions that may be relevant to customers, any elaboration or clarification on the "resolved" status if needed>
• Scope: <Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted>
• Previous impact to end users: <Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.>
• Required resolution steps: <Any steps users should take for the issue to be resolved on their end>

We apologize for any disruptions to your day.

2:48 AM PST

Update

We identified that a third-party app is stuck in a loop that has triggered billions of messages. This is causing free plan users to exceed messaging limits.

• Current status and actions being taken: A feature toggle ramp-up caused an app integration to repeatedly post messages in a processing loop. This pushed free plan customers over the message volume threshold, triggering the sending block. We're working to restore access and are actively working on remediation options for impacted Workspaces. 
• Estimated time to resolution: We don't have an estimated time yet. 
• Scope: Android users globally. 
• Current impact to end users: some customers on our free plan are experiencing message-sending limit blocks in an unusual spike pattern, which is preventing them from sending messages. We're investigating why this message limit was triggered unexpectedly for some teams. If you're affected, you may be temporarily unable to send messages until this is resolved. 
• Known workarounds: None at this time. 

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

2:45 AM PST

Update

We're aware that some customers on our free plan are experiencing message-sending limit blocks in an unusual spike pattern, which is preventing them from sending messages. We're investigating why this message limit was triggered unexpectedly for some teams. If you're affected, you may be temporarily unable to send messages until this is resolved. 

We'll provide an update in 30 minutes or sooner if additional information becomes available.

2:43 AM PST

Investigating

We're investigating a new incident.

• Current impact: Some users may be experiencing delays when loading Slack and when using Slack features. We're working to understand the full impact to users. Our team is actively investigating the issue and is focused on restoring full performance as quickly as possible. 

We’ll provide an update within 30 minutes, or as soon as new information become available with further details.

2:42 AM PST

Resolved

This issue is now resolved for all users.

• Current status and recent actions taken: test test test
• Scope: <Roughly what percentage of users were impacted; which categories of users, regions, devices, etc. were impacted>
• Previous impact to end users: <Describe the symptoms impacted users may have experienced, which functionality or features were affected, relevant error messages, etc.>
• Required resolution steps: <Any steps users should take for the issue to be resolved on their end>

We apologize for any disruptions to your day.

2:58 AM PST

Investigating

Some Slack customers experienced disrupted real-time connections, delayed message delivery, and errors loading conversation history on October 22, 2026, starting at 16:08 UTC. A large number of active connections closed at once and then reconnected, which briefly strained the services customers rely on to send and read messages. By 16:26 UTC, connections had reconnected and service had returned to normal. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

2:56 AM PST