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 patience.
update
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 production rollback is completed or if there are substantial updates to share.
update
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.
Further investigation confirms that the issue impacting Thread loading has been self- resolved, and our team will continue to investigate to ensure that this doesn’t reoccur. We apologize for the trouble today and thank you for your patience.
update
We’re still investigating these issues with Threads not loading. No additional information to share just yet, but we’ll keep you posted as soon as we have an update.
update
Some users are having trouble loading Threads in Slack, this is affecting Windows and Chrome users. Users may receive an error asking them to ‘Try Again’.
We apologize for the inconvenience and will report back as more information becomes available.
Resolved
This issue is now resolved for all users.
Current status and recent actions taken: Custom statuses set to expire at a specific time are now clearing as expected. The issue self-resolved when the next scheduled expiration job successfully processed the affected users.
Scope: Some external users globally were affected. Users on desktop were impacted; the issue was not reproducible internally or across test workspaces.
Previous impact to end users: Some users may have experienced custom statuses that did not automatically clear at their scheduled expiration time.
Required resolution steps: No steps required.
We apologize for any disruptions to your day.
update
We're aware of an issue affecting Slack. Some users who have set a custom status to expire at a specific time are finding that their status is not automatically clearing as expected. We're actively investigating and we'll provide an update as soon as we have more information available.
Users may experience delays due to increased load on bychan keyspace affecting system performance
This issue is now resolved for all users.
Current status and recent actions taken: We've completed rolling back the change to address the issue impacting core Slack functionality, including launching Slack, sending messages, loading threads, and other related actions.
Scope: All Slack enterprise customers.
Previous impact to end users: Users experienced issues with channel-related operations, including delays or failures when loading channels or retrieving channel membership lists.
We apologize for any disruptions to your day.
This issue is now resolved for all users.
Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. Users should no longer experience any issues when sending messages.
Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.
Previous impact to end users: Some users may have experienced trouble sending messages.
Required resolution steps: No additional steps are required.
We apologize for any disruptions to your day.
update
We are actively working to resolve the current platform functionality issues.
Current status and actions being taken: We're still working toward resolving the issue and to reduce the likelihood of symptoms recurring. We'll continue to monitor internal metrics as we work through this.
Estimated time to resolution: No ETA at this time.
Scope: This issue isn't affecting any specific region, but a percentage of users may be affected globally.
Current impact to end users: Some users may experience trouble sending messages.
Known workarounds: No known workarounds at this time.
We'll provide the next update upon a significant change in status, or sooner if additional information becomes available.
update
We are actively working to resolve the current platform functionality issues.
Current status and actions being taken: We have processed the affected service PODs to expedite recovery, resulting in significant recovery across the platform. We're now monitoring all systems to ensure performance remains stable.
Estimated time to resolution: No ETA at this time.
Scope: This issue isn't affecting any specific region, but a percentage of users may be affected globally.
Current impact to end users: Some users may experience trouble sending messages.
Known workarounds: No known workarounds at this time.
We'll continue to provide updates every 60 minutes until the impact is resolved for all users.
update
We are actively working to resolve the current platform functionality issues.
Current status and actions being taken: We've identified a fix and are actively deploying it across the platform. Once the rollout is complete, we'll monitor system performance to ensure full stability.
Estimated time to resolution: No ETA at this time.
Scope: This issue isn't affecting any specific region, but a percentage of users may be affected globally.
Current impact to end users: Some users may experience trouble sending messages.
Known workarounds: No known workarounds at this time.
We appreciate your patience as we sort this out.
update
We're investigating a new incident.
Current impact to end users: Some users may experience trouble sending messages. We're investigating the issue and we regret any inconvenience this is causing.
We'll provide an update within 30 minutes including further details on current actions being taken.
Current status and recent actions taken: After monitoring system performance and infrastructure stability, we have confirmed that all Slack features are operating within expected levels. This incident is now resolved and users should no longer experience any issues with Slackbot, AI Features, or workflows.
We apologize for any disruptions to your day.
update
Current status and actions being taken: We've deployed an emergency fix to address the issues contributing to intermittent errors with Slackbot and Workflows. We're now seeing significant recovery across all affected services and are continuing to monitor the situation closely to ensure performance remains stable.
We'll provide another update in 60 minutes.
update
Current status and actions being taken: We’ve deployed a configuration fix, resulting in significant improvements to Slackbot success rates and health metrics. We're now monitoring the situation as we investigate a secondary cache issue that may be contributing to intermittent errors or degraded workflow performance.
We'll provide another update in 60 minutes.
update
Current status and actions being taken: Upon further review, we've identified issues with secondary caching and are currently working on a configuration fix. In parallel, we're continuing to investigate and assess several solutions to restore services.
We'll provide another update in 60 minutes.
update
Current status and actions being taken: The code fix hasn't successfully addressed the impact and we're resuming our investigations.
We'll provide another update in 60 minutes.
update
Current status and actions being taken: We've begun deploying the code fix to production. Once complete we'll begin monitoring the performance of Slackbot, as well as our other AI-powered features.
We'll provide another update in 60 minutes.
update
Current status and actions being taken: We believe we've identified an issue that's still causing impact to occur even after our upstream provider has resolved impact from their end. We expect a code fix to take at least an hour to complete and pass through various test environments.
We'll provide another update in 60 minutes.
update
Current status and actions being taken: We're continuing to engage with our third-party provider to find a solution. No further alleviative actions have been undertaken since our last update.
We'll provide another update in 60 minutes until the impact is resolved for all users.
update
Current status and actions being taken: We've taken steps to try to reduce the impact on Slackbot and its response capabilities. Customers may notice signs of improvement, however, the impact may still be intermittent until full resolution.
Other AI-powered features, including Search Answers, Meeting Notes, and Translation, are still experiencing issues due to the ongoing upstream problem. We're investigating similar alleviative actions for these features.
We'll provide another update in 60 minutes until the impact is resolved for all users.
update
Current status and actions being taken: We're continuing to engage with our third-party provider to find a solution. We're also exploring multiple avenues on our side to try to alleviate impact on Slackbot and AI-powered features until the upstream issue is resolved.
We'll provide another update in 60 minutes until the impact is resolved for all users.
update
Our work on this issue is still ongoing. Users may continue to experience intermittent trouble with Slackbot responses and other Slack AI-powered features such as Search Answers, Meeting Notes, and Translation.
Current status and actions being taken: We remain engaged with our third-party provider.
We'll provide another update in 60 minutes until the impact is resolved for all users.
update
Our work on this issue is still ongoing.
Current status and actions being taken: Users may continue to experience trouble with Slackbot responses and other Slack AI-powered features. We've identified the trigger as a third-party infrastructure issue and are working with the provider to resolve this issue.
We'll provide another update in 30 minutes until the impact is resolved for all users.
update
We're investigating a new incident.
Current impact to end users: Some users may be experiencing trouble with Slackbot responses. Other Slack functionality that leverages AI services may also be experiencing issues. We're on the case and we'll provide an update within 30 minutes including further details on current actions being taken.
Legacy Incident Archive
40 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Incident: Huddle AI summaries not being generated
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.
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 pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate ...
Incident: EKM customers were previously experiencing issues with channel loading and message delivery
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 9:16 AM PDT on May 11, 2026.We've deployed fixes addressing the root cause of the elevated encryption key request load. If you continue to experience trouble, please reload Slack using Command + Shif...
Incident: EKM customers experiencing issues with channel loading and message delivery
majorSource not attested
Last archived state: investigating
View archived record details
investigating
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 is actively investigating this issue.Estimated time to resolution: No ETA at this time.Scope: This isn't affecting any specific region, but a percentage of Enterprise Key Management customers m...
Incident: Scheduled Grid Migrations are experiencing extended downtime
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack. Current impact to end users: Affected users may have experienced an inability to access Slac...
Incident: Slow behaviour in Slack
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 — primarily teams based in Central Europe — experienced elevated workflow failure rates.Previous impact to end users: Users may have experienced workflows failing to run, with the first step remaini...
Incident: Slack Search Feature Disruption - Japan region
majorSource not attested
Last archived state: investigating
View archived record details
investigating
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 a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity an...
April 2026
Incident: Users May Not Receive Notifications on Slack Thread Replies
majorSource not attested
Last archived state: investigating
View archived record details
investigating
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 patience.
Incident: Slack Threads Not Loading
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Further investigation confirms that the issue impacting Thread loading has been self- resolved, and our team will continue to investigate to ensure that this doesn’t reoccur. We apologize for the trouble today and thank you for your patience.
Incident: Custom status not expiring
majorSource not attested
Last archived state: investigating
View archived record details
investigating
ResolvedThis issue is now resolved for all users.Current status and recent actions taken: Custom statuses set to expire at a specific time are now clearing as expected. The issue self-resolved when the next scheduled expiration job successfully processed the affected users. Scope: Some external users globally were affected. Users on desktop were impacted; the issue was not reproducible internally or across test workspaces.Previous impact to end users: Some users may ...
