Slack

Affected: Login/SSO

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-10-14 00:23 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.

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Connectivity

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-09 15:35 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. update 2026-10-09 16:20 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. update 2026-10-09 23:58 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...

4. update 2026-10-12 17:03 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-10-01 12:39 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,...

2. update 2026-10-01 12:56 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. update 2026-10-01 13:58 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...

4. update 2026-10-01 14:31 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. update 2026-10-01 18:52 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. update 2026-10-01 18:59 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Files

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-09-12 11:04 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. update 2026-09-12 11:29 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...

3. update 2026-09-12 12:52 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...

4. update 2026-09-12 14:10 UTC

   T he 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...

5. update 2026-09-12 15:24 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...

6. update 2026-09-12 20:00 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Apps/Integrations/APIs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. update 2026-09-10 00:34 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. update 2026-09-10 00:58 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. update 2026-09-10 01:29 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. update 2026-09-10 01:37 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. update 2026-09-10 03:14 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.

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging, Workspace/Org Administration

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-08-13 21:21 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. update 2026-08-13 21:49 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. update 2026-08-14 19:35 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...

4. update 2026-08-14 20:20 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...

5. update 2026-08-14 21:39 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...

6. update 2026-08-17 21:57 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...

7. update 2026-08-20 22:54 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...

8. update 2026-08-25 20:55 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...

9. update 2026-08-27 18:58 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...

10. update 2026-09-01 22:51 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....

11. update 2026-09-04 17:00 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...

12. update 2026-09-09 02:37 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...

13. update 2026-09-11 15:53 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. update 2026-09-14 22:31 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Search

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. update 2026-08-06 22:22 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...

2. update 2026-08-06 23:11 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. update 2026-08-07 01:07 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.

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Apps/Integrations/APIs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. update 2026-07-28 02:13 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...

2. update 2026-07-28 03:25 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. update 2026-07-28 03:43 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.

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Workflows

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-07-24 08:22 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...

2. update 2026-07-24 08:44 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...

3. update 2026-07-24 09:08 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...

4. update 2026-07-24 09:42 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...

5. update 2026-07-24 10:47 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. update 2026-07-24 02:18 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. update 2026-07-24 02:53 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...

3. update 2026-07-24 03:20 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.

Excerpts are shortened. Read the full incident on Slack's status page.

Failure mode: The text does not say enough to tell. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. update 2026-06-26 09:12 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’...

2. update 2026-06-26 09:41 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...

3. update 2026-06-26 10:09 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Login/SSO

1. update 2026-06-17 22:33 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...

2. update 2026-06-18 01:49 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. update 2026-06-18 04:14 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging

1. update 2026-06-17 00:38 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. update 2026-06-17 01:07 UTC

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

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Workflows

1. update 2026-06-16 15:50 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...

2. update 2026-06-16 16:48 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...

3. update 2026-06-17 19:38 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...

4. update 2026-06-18 22:30 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...

5. update 2026-06-21 17:33 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. update 2026-06-22 20:39 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging

1. update 2026-06-16 01:19 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.

Excerpts are shortened. Read the full incident on Slack's status page.

1. update 2026-06-11 22:13 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...

2. update 2026-06-11 22:43 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. update 2026-06-11 23:15 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Apps/Integrations/APIs

1. update 2026-06-10 20:36 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....

2. update 2026-06-10 21:05 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. update 2026-06-10 21:37 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...

4. update 2026-06-10 22:49 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...

5. update 2026-06-10 23:39 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. update 2026-06-11 00:18 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...

7. update 2026-06-11 06:04 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...

8. update 2026-06-11 06:39 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Workspace/Org Administration

1. update 2026-06-09 15:24 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...

2. update 2026-06-09 17:39 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...

3. update 2026-06-09 20:18 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...

4. update 2026-06-10 09:47 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...

5. update 2026-06-10 10:35 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. update 2026-06-10 11:44 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. update 2026-06-10 14:35 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. update 2026-06-10 21:43 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Login/SSO

1. update 2026-06-08 19:00 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. update 2026-06-08 19:35 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Workspace/Org Administration

1. update 2026-06-03 16:33 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. update 2026-06-03 16:49 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...

3. update 2026-06-03 17:12 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...

4. update 2026-06-03 17:35 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Connectivity, Messaging

1. update 2026-06-03 00:58 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. update 2026-06-03 01:38 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...

3. update 2026-06-03 01:47 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Connectivity, Messaging

1. update 2026-06-02 16:16 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...

Excerpts are shortened. Read the full incident on Slack's status page.

1. update 2026-06-01 02:08 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. update 2026-06-01 02:38 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...

3. update 2026-06-01 03:05 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...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging, Apps/Integrations/APIs, Canvases

1. update 2026-05-27 23:00 UTC

   We're investigating a new incident. Current impact to end users: We’re aware of an issue affecting workflows, message edits, channel renames, apps, and channel creations. We'll provide an update within 30 minutes including further details on current actions being taken.

2. update 2026-05-27 23:31 UTC

   We continue to investigate the issue, and are‌ implementing fixes to restore services. We're starting to see some improvements from the fixes implemented so far. We’ll provide another update as soon as we have more information, and again we are sorry for the inconvenience this...

3. update 2026-05-28 01:03 UTC

   Teams continue to implement configuration adjustments and deployment fixes to resolve the issue. All features except for Workflows and Messaging should be recovered. Some lingering impact remains. Users may notice: Empty pills instead of @-mention Delayed reacji Mismatch in...

4. update 2026-05-28 01:41 UTC

   We are continuing to work on implementing fixes to fully resolve the issue. Messaging should now be recovered. Users may continue to experience issues with workflow steps completing. Empty pills instead of @-mention; delayed reacji; mismatch in Channel member count and channel...

5. update 2026-05-28 02:17 UTC

   Messaging latency has now cleared. Newly triggered workflows should start and complete as normal. Workflows that executed during the impact period ending at approximately 7pm PDT may not have completed. Customers may notice delayed workflow execution for jobs that triggered...

6. update 2026-05-28 02:46 UTC

   Workflow builder jobs that were triggered during the disruption period have been replayed and will complete over the next several hours. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

7. update 2026-05-28 03:22 UTC

   Cleanup and recovery efforts continue. Workflow builder job backlogs are being drained. Event subscriptions have been re-enabled. No further impact is expected. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

8. update 2026-05-28 03:55 UTC

   We’re glad to inform you that the Workflow Builder job backlogs were cleared and workflow execution has returned to normal. We continue progressing through the final stages of recovery activities across affected service areas as overall platform stability improves. We’ll provide...

9. update 2026-05-28 04:30 UTC

   Recovery activities continue, and restoration efforts are progressing well. Platform stability is improving, and no further customer impact is expected. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

10. update 2026-05-28 05:13 UTC

    Slack services continue to progress through the final stages of ‌recovery activities to restore functionality across all services. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

11. update 2026-05-28 05:47 UTC

    Slack services have largely returned to normal operational levels. Messaging, Workflows, Apps, Integrations, APIs, and Connections have all been restored. We'll continue with the final restoration activities and we'll provide updates as significant developments occur.

12. update 2026-05-28 10:04 UTC

    We're investigating a new impact to Slack. Current impact to end users: Slack users are experiencing issues with managing channels, statuses aren't clearing or updating correctly, and edits on Canvas aren't being saved. We'll provide an update within 30 minutes including further...

13. update 2026-05-28 10:45 UTC

    We continue to investigate the issue and are working with urgency to improve stability and reduce impact. We’ll provide another in 30 minutes or sooner, including further details on current actions being taken. We're sorry for the inconvenience this is causing.

14. update 2026-05-28 11:17 UTC

    Users continue to experience issues with their ability to manage channels, Canvas edits not saving, and user statuses not clearing or updating correctly. Investigations are underway. We're working with urgency to improve platform stability and reduce impact. We’ll provide an...

15. update 2026-05-28 11:46 UTC

    We continue to investigate the issue, and are‌ gathering the resources necessary to restore services. We’ll provide another update in 30 minutes or as soon as we have more information, and again we're sorry for the inconvenience this is causing.

16. update 2026-05-28 12:01 UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Remediation efforts are underway via configuration adjustments and deployment. We're still working to resolve the issues with Canvas. We'll be back with another update once we have news to share.

17. update 2026-05-28 12:25 UTC

    Recovery activities continue, and restoration efforts are progressing well. Slack users should now be able to edit Canvases as the errors have dropped. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.

18. update 2026-05-28 12:55 UTC

    Remediation efforts via configuration adjustments and deployment are in progress. Users may still run into issues updating their status and managing channels. We’ll provide another update in 30 minutes or as soon as we have more information, and again we are sorry for the...

19. update 2026-05-28 13:35 UTC

    Remediation efforts via configuration adjustments and deployment will take several hours to complete to fully resolve channel management and status issues. Slack users may continue to experience intermittent impact. We'll be back with another update in 30 minutes when we have...

20. update 2026-05-28 14:09 UTC

    Slack users continue to experience permissions-related issues such as: unable to manage channels, add Canvas to tabs, update statuses, convert public to private channels while we work on a complete restoration. We’ll provide an update in the next 30 minutes or sooner, if...

21. update 2026-05-28 15:22 UTC

    This issue is now resolved for all users. Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours....

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Files

1. update 2026-05-19 20:51 UTC

   We've identified the trigger, causing slow file and emoji uploads in Slack, and have deployed a fix. At this time, we are monitoring the environment to confirm full resolution. Current status and actions being taken: We've identified a frontend error as the cause of the issue...

2. update 2026-05-19 22:27 UTC

   This issue is now resolved for all users. Current status and recent actions taken: The fix has successfully deployed, and our health metrics have stabilized. The issue is now fully resolved for all affected users. Scope: This wasn't affecting any specific region, but a...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Huddles

1. update 2026-05-18 14:53 UTC

   Some Slack users experienced issues where Huddle AI summaries ‌weren't being generated. Users also appeared to be showing as in a huddle after it had ended. We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging, Files, Apps/Integrations/APIs, Workflows

1. update 2026-05-14 14:37 UTC

   We're investigating a new incident. Current impact to end users: We’re aware of an issue affecting file uploads, message edits, channel renames, and channel creations. We'll provide an update within 30 minutes including further details on current actions being taken.

2. update 2026-05-14 14:50 UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We're investigating reports of slow loading times, errors when updating workflows, editing messages, creating or renaming channels, reactions, and issues with file uploads and third-party...

3. update 2026-05-14 15:19 UTC

   Our work on this issue is still ongoing. Current status and actions being taken: We've identified a potential cause related to an internal infrastructure component responsible for processing background tasks. Several nodes running this component were experiencing resource...

4. update 2026-05-14 15:34 UTC

   The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally. If you are still experiencing any trouble, please perform a hard reload of Slack by...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Messaging, Files, Notifications, Apps/Integrations/APIs

1. update 2026-05-08 18:31 UTC

   Between approximately 10:55 AM and 11:10 AM PDT, customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading some channels. Error rates have returned to normal levels and customers should now see expected performance. We are...

2. update 2026-05-08 18:44 UTC

   We’re investigating this issue: Current status and actions being taken: We’re seeing renewed, elevated error rates and latency affecting customers using Enterprise Key Management (EKM). Affected customers may experience issues sending messages and loading some channels. Our team...

3. update 2026-05-08 19:20 UTC

   We’re investigating this issue: Current status and actions being taken: We believe an issue with an upstream provider may be impacting some Slack services. We’re partnering with them to help with our investigation and are waiting on additional details from their analysis. In...

4. update 2026-05-08 19:54 UTC

   We’re investigating this issue: Current status and actions being taken: We’ve deployed a fix that has improved our cache hit ratio and are observing recovery in our health metrics. In parallel, we're monitoring for updates from our upstream provider. Affected customers may...

5. update 2026-05-08 20:27 UTC

   We’re investigating this issue: Current status and actions being taken: We're seeing consistent improvement in our health metrics while our upstream provider has begun implementing a fix on their side. Affected customers may already be seeing improvements, and we’ll continue to...

6. update 2026-05-08 20:57 UTC

   We’re investigating this issue: Current status and actions being taken: We continue to monitor the issue as our upstream provider continues their work toward a resolution. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely...

7. update 2026-05-08 21:58 UTC

   We’re investigating this issue: Current status and actions being taken: Our upstream provider has implemented a fix and is continuing their investigation. In the meantime, we continue to observe improved health metrics. Affected customers may already be seeing improvements, and...

8. update 2026-05-08 23:27 UTC

   This issue is now resolved for all users. Current status and recent actions taken: Our upstream provider has successfully implemented a fix. Following a period of stable monitoring, all services have been restored. Customers should no longer experience issues accessing Slack....

9. update 2026-05-11 14:22 UTC

   Current status and actions being taken: We’re investigating a recurrence of a previous incident causing elevated errors and high latency for EKM customers. As a precaution, EKM backfills have been paused to reduce load. Teams are evaluating pod scaling and assessing a...

10. update 2026-05-11 15:11 UTC

    Current status and actions being taken: We're continuing to investigate elevated error rates affecting a subset of users. We've identified additional load contributing to the issue and have taken steps to reduce it. Estimated time to resolution: Under investigation. No ETA...

11. update 2026-05-11 16:05 UTC

    Current status and actions being taken: We're continuing to investigate elevated error rates affecting a subset of users. We've identified additional load contributing to the issue and have taken steps to reduce it. We've also engaged our third-party vendor to assist in...

12. update 2026-05-11 16:38 UTC

    Current status and actions being taken: We have identified contributing factors to the issue impacting EKM customers and have taken mitigating actions, including reducing the rate of KMS requests by approximately 50% and increasing cache capacity. We are continuing to monitor...

13. update 2026-05-11 17:12 UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Our monitoring has shown no further instability and we have considered this incident now under control. We are continuing to monitor closely. We'll provide another update should we find any further...

14. update 2026-05-11 19:02 UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Customer impact effectively stopped around 8:00AM PT and has remained stable. Our monitoring has shown no further instability and we have considered this incident under control. We are continuing to...

15. update 2026-05-11 21:48 UTC

    Users who rely on Enterprise Key Management (EKM) may have experienced elevated latency and errors across messaging, channel loading, workflows, and file operations starting around 5:55 AM PDT on May 11, 2026. Impact was mitigated and the incident was brought under control at...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Connectivity

1. update 2026-05-08 12:13 UTC

   Users who are undergoing scheduled Grid Migrations are experiencing extended downtime. Downtime is expected during a Grid Migration however it's taking longer than usual. During the downtime users are unable to access Slack until the migration completes. We've identified an...

2. update 2026-05-08 17:44 UTC

   This issue is now resolved. Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing. Scope: A...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Workflows

1. update 2026-05-04 10:00 UTC

   Some users are experiencing issues with workflows. Triggered workflows may fail to complete, with the first step not executing. We'll provide another update as soon as possible.

2. update 2026-05-04 11:43 UTC

   The investigation identified elevated latency in EU backend services as the cause of workflows not completing. A subset of workflow trigger attempts is impacted, primarily, EU users. Pod restarts have stopped, and error rates are improving. A fix is being prepared and will be...

3. update 2026-05-04 13:08 UTC

   A fix has been deployed to address the elevated latency in EU backend services. The team is monitoring the environment to ensure service stability and full recovery. We'll provide another update as soon as possible.

4. update 2026-05-04 17:37 UTC

   This issue is now resolved for all users. Current status and recent actions taken: A fix has been deployed that resolved the underlying cause of this issue. Our health metrics have returned to normal levels and workflows are running as expected. Scope : Users in the EU region —...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Search

1. update 2026-05-01 01:50 UTC

   At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack. We identified that infrastructure changes to our Search cluster caused...

Excerpts are shortened. Read the full incident on Slack's status page.

Affected: Notifications

1. update 2026-04-27 17:11 UTC

   Some users have reported issues with thread replies not generating a notification banner. We’re investigating the issue, and have identified a recent deployment as a possible trigger. We apologize for the inconvenience and will report back as more information becomes available.

2. update 2026-04-27 18:07 UTC

   We’re observing positive signals after rolling back the deployment in test environments. We will complete some final validations before rolling back the deployment in the production environment. Thank you for your patience as we work through this one. We’ll report back once...

3. update 2026-04-27 20:36 UTC

   We’ve successfully performed a rollback in the production environment, and all systems are now functioning as expected. Users should no longer experience any issues with thread replies not generating a notification banner. We apologize for any inconvenience and appreciate your...

Excerpts are shortened. Read the full incident on Slack's status page.