Thursday May 29, 2025

Incident

Sarah Testing

incident done Update

<Summarize any notable changes from the previous update OR if there aren't changes from the previous update, specifically state that here.>


  • Current status and actions being taken: <What actions we're currently taking in our investigation or remediation efforts; are we trying to identify the cause, have identified the cause, preparing to ship a fix, etc.>
  • Estimated time to resolution: <Rough timeframe in which impact might be resolved, if we have an estimate.>
  • Scope: <Roughly what percentage of users are impacted; which categories of users, regions, devices, etc. are impacted; absolute number of errors and/or impacted users can be included ONLY IF sending email to ONE customer>
  • Current impact to end users: <Describe the symptoms impacted users may experience, which functionality or features are affected, relevant error messages, etc.>
  • Known workarounds: <Any steps users could take to continue using Slack or impacted features before the issue is fully resolved>


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

1:47 AM PST

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.

1:46 AM PST

Update

On <Month Day, Year of incident> from <X:XX AM/PM PST of start of user impact> to <X:XX AM/PM PST of end of user impact>, <describe the problems or symptoms users may have experienced during this timeframe, specifying who/which types of users, regions, devices, etc. where relevant>. 

<Briefly explain what caused the issue(s) in terms the majority of users can understand>

<Briefly explain how we fixed the issue(s) in terms the majority of users can understand OR if Slack didn't take any steps explain how we know impact is resolved for users>

<If needed, include any other details or context>


1:45 AM PST

Investigating

We've identified an issue impacting the ability for many users to send messages. We have already implemented a fix, and users may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) to see full recovery. We apologize for any interruption to your day.

1:44 AM PST

Features affected

Files

Huddles

Connectivity

Canvases

Status

Incident