Slack Outage History

Started Oct 22, 2026, 06:50 PM UTC· resolved Oct 22, 2026, 06:50 PM UTC

1. resolved Oct 22, 2026, 06:50 PM UTC

   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.

Read the full incident report →

Started Oct 14, 2026, 12:23 AM UTC· resolved Oct 14, 2026, 12:28 AM UTC

1. resolved Oct 14, 2026, 12:23 AM UTC

   Some users may have experienced trouble logging into Slack. We identified the trigger and resolved the issue and restored access. We’re sorry for the disruption.

Read the full incident report →

Started Oct 09, 2026, 03:35 PM UTC· resolved Oct 12, 2026, 05:03 PM UTC

1. investigating Oct 09, 2026, 03:35 PM UTC

   Users may experience iOS closing unexpectedly when opening channels. We're actively looking in to this, and we'll share another update as soon as we have more information. We appreciate your patience in the meantime.

2. investigating Oct 09, 2026, 04:20 PM UTC

   We've developed a fix for the iOS app issue and are working to validate it before releasing it to customers. We'll share another update as soon as we have more information.

3. investigating Oct 09, 2026, 11:58 PM UTC

   An updated version of the Slack iOS app that fixes the crash was approved and began rolling out gradually. Customers who download the updated version from the app store can now open channels without the app closing unexpectedly. We'll provide an update once additional information becomes available.

4. resolved Oct 12, 2026, 05:03 PM UTC

   We've rolled out an updated version of the Slack iOS app to all impacted customers. Channels now open without the app closing unexpectedly. Users who are still experiencing this issue should update the Slack IOS app from the app store Store to resolve it. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Oct 01, 2026, 12:39 PM UTC· resolved Oct 01, 2026, 06:59 PM UTC

1. investigating Oct 01, 2026, 12:39 PM UTC

   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. investigating Oct 01, 2026, 12:56 PM UTC

   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. We apologize for the inconvenience and will provide another update as soon as we have more details to share.

3. investigating Oct 01, 2026, 01:58 PM UTC

   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. We apologize for the inconvenience and will provide another update as soon as we have more details to share.

4. investigating Oct 01, 2026, 02:31 PM UTC

   We’ve identified a potential fix for this issue and we’re working on getting this out to users as quickly as possible. We’ll be back once we have another update to share. Thank you for your continued patience as we work towards a solution.

5. monitoring Oct 01, 2026, 06:52 PM UTC

   Deployment of the fix is underway to restore access for impacted free plan workspaces, and we are actively monitoring the environment. More information will follow as we progress through this stage of remediation.

6. resolved Oct 01, 2026, 06:59 PM UTC

   A messaging integration briefly caused some free-plan workspaces to exceed their daily messaging limit, blocking them from sending messages. We took action to lift the sending block for all affected free-plan workspaces, and have confirmed messaging is now restored. 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.

Read the full incident report →

Started Sep 12, 2026, 11:04 AM UTC· resolved Sep 12, 2026, 08:00 PM UTC

1. investigating Sep 12, 2026, 11:04 AM UTC

   We're aware there's an issue where a subset of customers are experiencing blurry images which can't be downloaded, this is happening across all clients. We're actively working to understand the cause, scope, fix, or other details.

2. identified Sep 12, 2026, 11:29 AM UTC

   We've identified a likely technical trigger connected to a recent image-rendering service change. Current status and actions being taken: We have identified a likely technical trigger — a recent thumbnail-sharpening change to the image-rendering service. We're working to validate this, and are evaluating the rollback of the change as a possible fix.Estimated time to resolution: We are still confirming the technical trigger before a fix can be scoped.Scope: Affects a subset of customers across desktop, web, and mobile clientsCurrent impact to end users: Images uploaded before roughly 9:30 PM GMT on Sep 11 appear blurry in previews and fail to download. Newly uploaded images are unaffected.Known workarounds: None identified yet.We appreciate your patience as we sort this out.

3. investigating Sep 12, 2026, 12:52 PM UTC

   We have rolled back the code change that caused the issue in the production environment. Validation is in progress. Current status and actions being taken: We confirmed the technical trigger (a thumbnail-sharpening code change) and completed a rollback in the production environment after successfully testing the fix in the test environment. We are performing additional validations to confirm the fix was successful.Estimated time to resolution: We do not have and estimated time frame at the moment,.Scope: Affects a subset of customers across desktop, web, and mobile clients; Current impact to end users: Images uploaded before roughly 9:30 PM GMT on Sep 11 appear blurry in previews and fail to download. Newly uploaded images are unaffected. We appreciate your patience as we sort this out.

4. investigating Sep 12, 2026, 02:10 PM UTC

   The earlier rollback did not resolve the issue, and investigation has been redirected to a file-serving problem rather than the thumbnail-generation change. Current status and actions being taken: The rollback of the thumbnail-sharpening change did not fix the issue. We have revised the technical trigger assessment to a file-serving problem, where the system returns near-empty successful responses instead of full image data. We are investigating file storage and access-policy changes, and gathering file details from affected customers to pinpoint the cause.Estimated time to resolution: No confirmed estimate yet; the team is still narrowing down the cause following the pivot to file serving.Scope: Affects a subset of customers across desktop, web, and mobile clients.Current impact to end users: Images uploaded before 9:30 PM GMT on Sep 11 appear blurry in previews and fail to download. Newly uploaded images are unaffected. The earlier rollback did not change this — previously affected images remained blurry and undownloadable. We appreciate your patience as we sort this out.

5. investigating Sep 12, 2026, 03:24 PM UTC

   We have confirmed the technical trigger and are preparing a fix Current status and actions being taken: We confirmed the technical trigger — a code change that caused older file records to lose their stored file names, breaking retrieval of existing images. The team is preparing a targeted fix to restore file names correctly when reading older files. The affected files are expected to recover automatically once the fix is deployed.Estimated time to resolution: We don't have an estimate yet.Scope: Affects a subset of customers across desktop, web, and mobile clients.Current impact to end users: Images uploaded before roughly 9:30 PM GMT on Sep 11 appear blurry in previews and fail to download. Newly uploaded images are unaffected. Previously affected images remain blurry and undownloadable.We appreciate your patience as we sort this out.

6. monitoring Sep 12, 2026, 08:00 PM UTC

   Some customers experienced blurry images that couldn't be downloaded across all clients, affecting files uploaded before a recent file storage update. We deployed a fix restoring proper file access, and confirmed it resolved the issue for affected customers. 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.

Read the full incident report →

Started Sep 10, 2026, 12:34 AM UTC· resolved Sep 10, 2026, 03:14 AM UTC

1. investigating Sep 10, 2026, 12:34 AM UTC

   We’re aware of an issue affecting Workspace-level Apps & Workflows settings page. Users are seeing a blank page affecting these admin features. We’re actively investigating this issue and will provide an update in 30 minutes or sooner if more information becomes available.

2. investigating Sep 10, 2026, 12:58 AM UTC

   We've engaged our engineering team to assist in the investigation. We’re continuing to work on understanding the issue. We’ll provide an update in 30 minutes or sooner if more information becomes available.

3. identified Sep 10, 2026, 01:29 AM UTC

   We've identified the cause of this issue, and our engineers are testing a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. investigating Sep 10, 2026, 01:37 AM UTC

   The fix has been validated in our test environment and is now being deployed. We will provide an update once the deployment is complete, or sooner if additional information becomes available.

5. resolved Sep 10, 2026, 03:14 AM UTC

   This incident has been resolved. The engineering team has confirmed that the fix has been successfully deployed. We apologize for any disruptions this may have caused to your day.

Read the full incident report →

Started Aug 13, 2026, 09:21 PM UTC· resolved Sep 14, 2026, 10:31 PM UTC

1. investigating Aug 13, 2026, 09:21 PM UTC

   Users with custom data retention policies enabled might be unable to see or load older messages. We apologize for the trouble and we'll share more news as it becomes available.

2. investigating Aug 13, 2026, 09:49 PM UTC

   We're continuing to investigate an issue affecting a subset of channels with custom message retention settings. Our teams are working to identify the technical trigger and an appropriate fix. We'll provide an update as more news becomes available.

3. investigating Aug 14, 2026, 07:35 PM UTC

   We're continuing to investigate an issue affecting a subset of channels with custom message retention settings. Our Teams have restored functionality to the affected retention settings for known impacted customers. We are now working to identify and address any additional concerns regarding the message retention issues.

4. investigating Aug 14, 2026, 08:20 PM UTC

   After further investigation, the custom retention settings have not fully been restored yet. Our teams have identified the technical trigger and are currently developing a mitigation plan to mitigate the impact to the custom retention settings. All custom retention jobs have been put on hold as the team works to address this issue. We apologize for the confusion, and thank you for bearing with us while we work through this issue.

5. investigating Aug 14, 2026, 09:39 PM UTC

   We're continuing to investigate an issue affecting a subset of channels with custom message retention settings. Custom channel retention settings have been restored for affected customers. Custom retention jobs remain on hold for some customers as we work to fully resolve the underlying cause regarding the custom message retention issues.

6. investigating Aug 17, 2026, 09:57 PM UTC

   We're continuing our restoration efforts regarding this issue affecting a subset of channels with custom message retention settings. While we work to resolve this issue, data retention processing remains paused for affected customers. We will provide another update as additional information becomes available.

7. investigating Aug 20, 2026, 10:54 PM UTC

   We're continuing to work on restoring messages, message edits, and file shares for a limited number of workspaces that were affected by an issue with custom data retention settings. We've fixed what triggered the issue and are running data recovery using backup restoration methods. Custom retention settings have been restored for impacted channels, and we're gradually re-enabling retention jobs. We will provide another update as additional information becomes available.

8. investigating Aug 25, 2026, 08:55 PM UTC

   We’re continuing our work to restore the remaining message data affected by this issue. Our teams have made progress developing and validating the recovery process for messages, message edits, and shared files. We’re addressing additional technical dependencies and completing validation before proceeding with the next stages of restoration. We’ll continue to provide updates as we make progress.

9. investigating Aug 27, 2026, 06:58 PM UTC

   We’re continuing our work to restore the remaining message data affected by this issue. We’ve made further progress across the recovery processes for messages, message edits, and shared files. Validation of the message-edit recovery process has identified additional adjustments needed before restoration proceeds, while preparation and validation for message recovery continue. We’ve also completed additional development work supporting shared-file restoration, including handling for shared channels. Custom retention processing has been re-enabled for affected active workspaces. We’ll continue to provide updates as restoration and validation progress.

10. investigating Sep 01, 2026, 10:51 PM UTC

    We continue to restore batches of messages, message edits, and shared files. Each batch requires careful planning, monitoring, and validation to ensure the affected messages are accurately restored. Custom retention processing remains re-enabled for affected active workspaces. Thank you for bearing with us while we continue to work through this complex and nuanced issue. More updates will come as restoration and validation progress.

11. investigating Sep 04, 2026, 05:00 PM UTC

    We’ve made further progress restoring messages, message edits, and shared files affected by this issue. We identified and resolved a technical limit that was slowing recovery for some accounts, and recovery for Slack Connect workspaces is now underway. Message edit restoration is nearing completion for affected workspaces. We’re continuing to validate restored data as recovery progresses. We’ll provide another update as significant progress is made.

12. investigating Sep 09, 2026, 02:37 AM UTC

    We've made further progress restoring message data across affected teams and channels, with most batches now complete. We've deployed a tool to correct thread reply links affected during the restore process and are running it now. Slack Connect message restoration is resuming production runs, with results being closely monitored. We'll provide an update as soon as new information becomes available.

13. investigating Sep 11, 2026, 03:53 PM UTC

    We’ve completed message data restoration across affected teams and channels, and are now focused on restoring file shares which should be the last step towards resolution. We'll provide another update as soon as new information becomes available.

14. resolved Sep 14, 2026, 10:31 PM UTC

    We've completed restoring shared files for all remaining affected workspaces and restored and verified all affected data. If you still can't see previous content, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Thank you for your patience while we sorted out this issue.

Read the full incident report →

Started Aug 06, 2026, 10:22 PM UTC· resolved Aug 07, 2026, 01:08 AM UTC

1. investigating Aug 06, 2026, 10:22 PM UTC

   Since approximately 21:00 UTC on August 6, some admins have been unable to click or use the search bar on org dashboard pages. We are aware of this issue and are actively investigating the cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.

2. identified Aug 06, 2026, 11:11 PM UTC

   We have identified the cause of this issue as a recent change and have started the process of rolling back the problematic change.

3. resolved Aug 07, 2026, 01:07 AM UTC

   We've completed the rollback of the recent change that was the trigger of the issue. The Search bar and Admin dashboard is restored for all users. We apologize for the inconvenience caused to you and your business.

Read the full incident report →

Started Jul 28, 2026, 02:13 AM UTC· resolved Jul 28, 2026, 11:09 PM UTC

1. identified Jul 28, 2026, 02:13 AM UTC

   We're currently investigating an issue affecting users' ability to receive incoming emails into Slack, caused by some issues with our email ingestion pipeline. We're sorry for any inconvenience this is causing, our team is actively working on a fix and we'll share an update as soon as we have more information.

2. identified Jul 28, 2026, 03:25 AM UTC

   We identified the cause of the issue preventing users from receiving incoming emails. We are deploying a fix and will share a further update once deployment and verification are complete.

3. investigating Jul 28, 2026, 03:43 AM UTC

   The fix has been successfully deployed, and validation is now complete. The issue preventing users from receiving incoming emails into Slack is fully resolved, and normal service functionality has been restored. We apologize for any disruptions to your day.

Read the full incident report →

Started Jul 24, 2026, 08:22 AM UTC· resolved Jul 24, 2026, 10:47 AM UTC

1. investigating Jul 24, 2026, 08:22 AM UTC

   We’re aware of an issue affecting Workflows that include 'refer to a message link'. Users with these workflows are unable to send a message to a channel, and will receive an ‘Input Validation Error’ when trying to perform this step. We’re actively investigating this issue and will provide an update in 30 minutes or sooner if more information becomes available.

2. investigating Jul 24, 2026, 08:44 AM UTC

   We've engaged our Worklow team to assist in the investigation. Initial analysis appears to show a conflict between specific variables. We’re continuing to work to understand whether this is the trigger of the issue. We’ll provide an update in 30 minutes or sooner if more information becomes available.

3. investigating Jul 24, 2026, 09:08 AM UTC

   The Workflow team is currently analyzing whether a recent change may have resulted in the conflict between variables that has been observed. It is expected to take some time to validate whether this is the case. We’ll provide an update in 60 minutes or sooner if more information becomes available.

4. investigating Jul 24, 2026, 09:42 AM UTC

   We’ve performed a test of reverting a recent change and this appears to have resolved the issue. We are in the process of performing a production wide revert of this change. This is expected to take some time to complete and we will validate that it is successful. We’ll provide an update in 2 hours or sooner if more information becomes available.

5. resolved Jul 24, 2026, 10:47 AM UTC

   We’ve completed the revert of the recent change and have validated that this has brought customers out of impact and can now successfully send a message to a channel using Workflows that include 'refer to a message link'. We apologize for how this incident may have affected you and your business.

Read the full incident report →

Started Jul 24, 2026, 02:18 AM UTC· resolved Jul 24, 2026, 03:20 AM UTC

1. investigating Jul 24, 2026, 02:18 AM UTC

   Some users are reporting issues with receiving reminders in Slack. We're aware of the issue and are actively investigating. We'll provide an update as soon as more information becomes available. We apologize for any inconvenience this issue is causing you.

2. identified Jul 24, 2026, 02:53 AM UTC

   We believe we’ve identified the cause of the issue impacting reminders in Slack. We’ve developed a potential fix for the issue and have deployed a change. We are actively monitoring to confirm that reminders are being delivered as expected. We'll provide an update as more information becomes available.

3. resolved Jul 24, 2026, 03:20 AM UTC

   After a period of monitoring, we can see that reminders are now working as expected following the fix deployment. This issue has been resolved as of 03:00 UTC, July 24. We apologize for any inconvenience this issue has caused you.

Read the full incident report →

Started Jun 26, 2026, 09:12 AM UTC· resolved Jun 26, 2026, 10:09 AM UTC

1. investigating Jun 26, 2026, 09:12 AM UTC

   We're aware of an issue affecting users ability to reach our Slack Support team via the Chat functionality on the Slack Help page. Users will be unable to click on the ‘Chat’ option and will see a ‘Chat is temporarily unavailable. Please send us a message or check back later’ error message. We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

2. investigating Jun 26, 2026, 09:41 AM UTC

   Additional Slack engineers have been engaged and are investigating this issue. As a workaround, if users require support, they can use the ‘Send us a Message’ functionality on the Slack Help Center page here: https://slack.com/intl/en-gb/help/requests/new . A member of the Slack team will then be in touch. We're working to resolve this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

3. resolved Jun 26, 2026, 10:09 AM UTC

   We've resolved the issue and users can now use the Chat feature on the Slack Help Center. We performed a configuration change, which brought the feature back online and have validated that it's functioning as expected. We apologize for how this incident may have affected you and your business.

Read the full incident report →

Started Jun 17, 2026, 10:33 PM UTC· resolved Jun 18, 2026, 04:14 AM UTC

1. investigating Jun 17, 2026, 10:33 PM UTC

   Some workspace admins on standalone (non-Enterprise Grid) workspaces may be experiencing an issue where the SSO and authentication configuration page does not display current settings as expected. Admins may see a blank value for the "Require SSO authentication for" field on the admin SSO settings page, which does not accurately reflect the actual backend configuration — SSO settings remain intact and in effect. We are actively investigating this issue and will provide an update as soon as we have more information to share. We apologize for the inconvenience.

2. identified Jun 18, 2026, 01:49 AM UTC

   We have identified the trigger and developed a fix. We are currently deploying this fix and expect to resolve the issue shortly. We will provide another update once the deployment is complete. We apologize for the inconvenience.

3. monitoring Jun 18, 2026, 04:14 AM UTC

   We have successfully deployed the fix to production and the issue is resolved. The Admin SSO and Authentication Configuration page for standalone workspaces should now display the correct settings. If you continue to see outdated information, refresh the SSO Admin page to load the latest changes.

Read the full incident report →

Started Jun 17, 2026, 12:38 AM UTC· resolved Jun 17, 2026, 01:07 AM UTC

1. investigating Jun 17, 2026, 12:38 AM UTC

   Some users may be experiencing issues performing certain actions in Slack, channel creation, invitation, and join operations may result in a degraded experience. Thank you for your patience while we continue to investigate the situation.

2. resolved Jun 17, 2026, 01:07 AM UTC

   This issue is now resolved for all users. We apologize for any disruptions to your day.

Read the full incident report →

Started Jun 16, 2026, 03:50 PM UTC· resolved Jun 22, 2026, 08:39 PM UTC

1. investigating Jun 16, 2026, 03:50 PM UTC

   We are aware that some users on the Slack Android app are unable to submit workflow forms that contain a required file upload field. After a file is selected, the Submit button becomes disabled and the form cannot be completed. Users on Slack for iOS and Slack for web are not affected. We are actively investigating the issue and working to identify the root cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.

2. identified Jun 16, 2026, 04:48 PM UTC

   We have identified the cause of this issue and confirmed it affects a small subset of users on a single version of the Slack Android app. Users on other Android versions, iOS, and web are not affected. A fix is already available and will begin rolling out to Android users tomorrow. We will provide an update as soon as additional information becomes available.

3. investigating Jun 17, 2026, 07:38 PM UTC

   A fix for this issue has been delivered in a new version of the Slack Android app, and rollout has now begun. Android users will start seeing the updated app version become available in the Google Play Store as the rollout progresses. Once updated, users who were experiencing issues submitting workflow forms containing a required file upload field will be able to do so successfully. We will continue to monitor the rollout and provide another update as additional information becomes available.

4. investigating Jun 18, 2026, 10:30 PM UTC

   The rollout of the new version of the Slack Android app is ongoing and may take up to several days to fully complete. We continue to monitor the rollout and will provide another update when we have more information to share. Thank you for your patience with us while we work through this.

5. resolved Jun 21, 2026, 05:33 PM UTC

   We continue to monitor the rollout of the new version of Slack for Android. We'll provide another update when we have further information to share. Thank you for your continued patience.

6. resolved Jun 22, 2026, 08:39 PM UTC

   This issue has been resolved. Android users who were experiencing issues submitting workflow forms containing a required file upload field can now do so successfully. A fix was delivered via a new update to the Slack Android app. Users who are still experiencing this issue should update the Slack app from the Google Play Store to resolve it. No other action is required. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Jun 16, 2026, 01:19 AM UTC· resolved Jun 16, 2026, 01:19 AM UTC

1. resolved Jun 16, 2026, 01:19 AM UTC

   Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.

Read the full incident report →

Started Jun 11, 2026, 10:13 PM UTC· resolved Jun 11, 2026, 11:15 PM UTC

1. investigating Jun 11, 2026, 10:13 PM UTC

   We're aware of an issue affecting the Slack desktop app. Users may find that content in child windows, such as channels or documents opened in a separate window, displays at reduced height. We’ve identified the technical trigger and are deploying a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

2. monitoring Jun 11, 2026, 10:43 PM UTC

   We’ve deployed a fix and are now performing validations. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. resolved Jun 11, 2026, 11:15 PM UTC

   We've validated that the fix resolved the issue and child windows are now displaying content as expected. You may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. We're sorry for the disruption this caused to your day.

Read the full incident report →

Started Jun 10, 2026, 08:36 PM UTC· resolved Jun 11, 2026, 06:39 AM UTC

1. investigating Jun 10, 2026, 08:36 PM UTC

   We're aware of an issue impacting the Slack Gmail add-on integration. As a result, users are unable to interact with the add-on and may encounter a “Something went wrong when executing the add-on. For help, contact the add-on developer” error message when attempting to use it. We are investigating the cause of this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

2. investigating Jun 10, 2026, 09:05 PM UTC

   We’re still actively investigating the issue impacting the Slack Gmail add-on. We are working to identify the cause, and no workaround is currently available. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. investigating Jun 10, 2026, 09:37 PM UTC

   We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

4. investigating Jun 10, 2026, 10:49 PM UTC

   We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

5. identified Jun 10, 2026, 11:39 PM UTC

   We continue to investigate the issue impacting Slack Gmail add-ons. We've identified the cause and our teams are working on a fix to resolve the issue as soon as possible. We’ll provide an update once additional information becomes available.

6. investigating Jun 11, 2026, 12:18 AM UTC

   We’re actively working on the fix to resolve the issue. We estimate this will take approximately four hours or more to complete, and validate the fix, before it can be deployed. As such, the next status update will be once the fix has been completed and validated, or we have new information to share. We apologize for any inconvenience this issue is causing for users.

7. identified Jun 11, 2026, 06:04 AM UTC

   We’re continuing to investigate the issues with the Slack Gmail add-on and are actively working on a fix to resolve the issue. There’s no new information to share at this time, but we’ll provide an update as soon as we have more details on implementing the fix. We apologize for any inconvenience this issue is causing for users.

8. resolved Jun 11, 2026, 06:39 AM UTC

   We've resolved the issue that prevented customers from using the Slack Gmail add-on. The fix has been successfully deployed; health metrics have stabilized, and the Gmail add-on is now fully operational for all affected users. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 09, 2026, 03:24 PM UTC· resolved Jun 10, 2026, 09:43 PM UTC

1. investigating Jun 09, 2026, 03:24 PM UTC

   Some users may experience issues when attempting to add multiple users to channels. Multiple matches error may appear along with a failure to identify team members. This may cause subsequent workflows not to trigger. We're investigating and will let you know as soon as we know more.

2. identified Jun 09, 2026, 05:39 PM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We have identified the trigger for this issue and a fix is in the process of deploying. The progress is being monitored and we’ll provide an update as soon as the fix is completely deployed and verified.We'll be back with another update once we have news to share.

3. resolved Jun 09, 2026, 08:18 PM UTC

   This issue is now resolved for all users. Current status and recent actions taken: We identified the trigger for this issue and a fix was deployed. After a period of monitoring, we have concluded that there is no further impact to users.Previous impact to end users: Some users may have experienced issues when attempting to add multiple users to channels and received an error indicating a failure to identify team members. This could have caused subsequent workflows not to trigger. Required resolution steps: No further action is necessary.Thanks for sticking with us as we resolved this. We apologize for any disruptions to your day.

4. investigating Jun 10, 2026, 09:47 AM UTC

   We've received reports that a subset of users may continue to experience issues when attempting to add multiple users to channels using email addresses. These users may encounter a "Multiple matches" error, preventing the intended user from being identified and added to the channel. We’re actively investigating these reports to determine whether additional remediation is required. We'll provide further updates as more information becomes available.

5. investigating Jun 10, 2026, 10:35 AM UTC

   We’re working to reproduce the issue. This will help us ‌identify the underlying cause and provide a resolution. We'll provide further update as soon as more information becomes available.

6. identified Jun 10, 2026, 11:44 AM UTC

   We’ve identified the cause of the issue and we’re validating a fix to ensure it fully resolves the issue before we deploy it. We'll provide further update as soon as more information becomes available.

7. resolved Jun 10, 2026, 02:35 PM UTC

   We've deployed a fix for the issue and are monitoring to confirm that the issue has been resolved. We'll provide another update as soon as more information becomes available.

8. resolved Jun 10, 2026, 09:43 PM UTC

   We've resolved an issue that could cause incorrect email address tokens to appear when users pasted multiple email addresses into the member invite flow. In some cases, pasted email addresses were incorrectly matched to existing members with similar email addresses, requiring users to manually correct the entries before proceeding. We identified the cause of the issue and deployed a fix to ensure email addresses are now matched correctly when pasted into the invite flow. The issue is resolved for all affected users. If you're still experiencing any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and appreciate your patience.

Read the full incident report →

Started Jun 08, 2026, 07:00 PM UTC· resolved Jun 08, 2026, 07:35 PM UTC

1. investigating Jun 08, 2026, 07:00 PM UTC

   Some users in EMEA may be failing to receive 2FA codes via SMS when logging into Slack. We are investigating the trigger and working to resolve this incident as quickly as possible. We will provide another update in 30 minutes or sooner as we have more details to share.

2. resolved Jun 08, 2026, 07:35 PM UTC

   The issue affecting SMS-based two-factor authentication for users in EMEA has been resolved, and all services are now functioning as expected. We have adjusted configuration settings to restore normal service and will continue to monitor the situation to ensure stability. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Read the full incident report →

Started Jun 03, 2026, 04:33 PM UTC· resolved Jun 03, 2026, 05:35 PM UTC

1. investigating Jun 03, 2026, 04:33 PM UTC

   We're investigating a new incident. Current impact to end users: Some administrators may be experiencing errors managing members.We'll provide an update within 30 minutes including further details on current actions being taken.

2. investigating Jun 03, 2026, 04:49 PM UTC

   We're looking into an issue where some users may be unable to add new members, send invites, or run macros on their workspaces. We're on the case and will provide another update as soon as we have more details to share. We apologize for any disruption to your work. Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace. We'll provide an update within 30 minutes or sooner if additional information becomes available.

3. identified Jun 03, 2026, 05:12 PM UTC

   We have identified the cause of the issue preventing some workspace admins from adding new members via the Admin page as a recent change and are in the process of rolling back this change. Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace. Known workaround: Inviting members via the Slack client workspace menu (workspace name → Invite people to workspace) is currently working as expected. We'll provide an update within 30 minutes or sooner if additional information becomes available.

4. identified Jun 03, 2026, 05:35 PM UTC

   The Slack engineering team identified the cause as a recent update that introduced a code change which caused the invite modal to fail when accessed from the Admin page. We rolled back the change and have confirmed the fix is fully deployed and the issue is resolved. Some workspace Admins were unable to add new members to their workspaces via the Manage Members Admin page. In addition, some users attempting to invite people from this page may have encountered an error or been unable to run macros on their workspaces. Workspace Admins should now be able to add new members via the Manage Members admin page. A page refresh may be required. We apologize for the disruption to your work.

Read the full incident report →

Started Jun 03, 2026, 12:58 AM UTC· resolved Jun 03, 2026, 01:47 AM UTC

1. investigating Jun 03, 2026, 12:58 AM UTC

   We're investigating a new incident. Current impact to end users: Some users may be experiencing trouble loading or connecting to Slack. We're on the case.We'll provide an update within 30 minutes including further details on current actions being taken.

2. investigating Jun 03, 2026, 01:38 AM UTC

   Our work on this issue is still ongoing. Current status and actions being taken: we're investigating an issue where some Slack users are experiencing thread loading, client booting, and message delivery failures. We've identified several potential contributing factors and are working to confirm the root cause. Further updates will be shared as the investigation continues.We'll provide another update in 30 minutes until the impact is resolved for all users.

3. resolved Jun 03, 2026, 01:47 AM UTC

   This issue is now resolved for all users. Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored.We apologize for any disruptions to your day.

Read the full incident report →

Started Jun 02, 2026, 04:16 PM UTC· resolved Jun 02, 2026, 04:16 PM UTC

1. resolved Jun 02, 2026, 04:16 PM UTC

   Current status: The Slack engineering team investigated connectivity issues that affected some users between approximately 13:30 and 14:00 UTC on June 2, 2026. The issue has been resolved and no further impact has been reported. Scope: Some users, primarily in Europe, may have experienced difficulty loading or sending Slack messages during this window We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 01, 2026, 02:08 AM UTC· resolved Jun 01, 2026, 03:05 AM UTC

1. investigating Jun 01, 2026, 02:08 AM UTC

   We are currently investigating a partial degradation impacting usergroups. We’ll provide an update as soon as we have more information to share and are sorry for any inconvenience this issue is causing.

2. investigating Jun 01, 2026, 02:38 AM UTC

   We continue to investigate the issue and have identified a recent deployment as a likely trigger. Users may experience issues with user groups, including failed @mentions or groups appearing unavailable. We are actively working on restoring functionality and will provide another update as soon as possible.

3. resolved Jun 01, 2026, 03:05 AM UTC

   Our investigation has determined that the issue is isolated to a single customer environment and is not impacting the broader service. As a result, this incident will be removed from the status page and we will continue to work directly with the affected customer to address their issue.

Read the full incident report →

Started May 27, 2026, 11:02 PM UTC· resolved May 27, 2026, 11:29 PM UTC

1. investigating May 27, 2026, 11:02 PM UTC

   The Slack Engineering team is currently investigating severe latency impacting all Slack services. We'll provide an update as soon as we have more information to share and apologize for any inconvenience this is causing.

Read the full incident report →