Friday March 27, 2026

Resolved

This issue is now resolved for all users.

• Current status and recent actions taken: We identified a paused job that may have been contributing to the high utilization. This was unpaused, which restored resource availability.
• Scope: This only affected a small subset of users.
• Previous impact to end users: Some users may have experienced issues while sending messages and loading message history in Slack between 20:14 PDT and 22:14 PDT.

We apologize for any disruptions to your day.

10:39 PM PST

Investigating

Our work on this issue is still ongoing.

• Current status and actions being taken: We are reviewing additional logs and diagnostic information to determine the best path to resolution.

We'll provide another update in 60 minutes until the impact is resolved for all users.

10:19 PM PST

Update

We continue to investigate the issue.

• Current status and actions being taken: We have identified high resource utilization as a potential trigger. We continue to investigate and determine the best path to resolution.
• Estimated time to resolution: We don't have the exact resolution time at the moment and will update you once we have additional information.
• Scope: This is only impacting a small subset of users.
• Current impact to end users: Some users may experience issues while sending messages and loading message history in Slack.
• Known workarounds: Users can mitigate the issue by retrying the message sending or loading of message history.

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

9:42 PM PST

Investigating

We're investigating a new incident.

• Current impact to end users: Some users may experience issues while sending messages and loading message history in Slack. 

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

9:12 PM PST