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.
April 2026
Incident: Users may experience delays due to increased load on bychan keyspace affecting system performance
majorSource not attested
Last archived state: investigating
View archived record details
investigating
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 channe...
Incident: Trouble Sending Messages
majorSource not attested
Last archived state: investigating
View archived record details
investigating
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...
Incident: Trouble with Slackbot and AI-powered features
majorSource not attested
Last archived state: investigating
View archived record details
investigating
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.
Incident: Slackbot button in the top navigation is disappearing
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: We've completed deploying the fix to address the issue affecting the Slackbot button in the top navigation bar. The Slackbot button is now working as expected. Scope: The issue was introduced for any users on build 121247.Previous impact to end users: The Slackbot button in the top navigation bar may not have been visible to users.Required resolution steps: Users who are stil...
March 2026
Incident: Issue with Sending and Receiving Messages
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Following a period of monitoring, our engineering team called this incident resolved as of 01:10 UTC, March 30. We apologize for any inconvenience this issue has caused to users.
Incident: Issues while sending messages and loading message history is impacting some users
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: We identified a paused job that may have been contributing to the high utilization. This was unpaused, which restored resource availability.Scope: This only affected a small subset of users.Previous impact to end users: Some users may have experienced issues while sending messages and loading message history in Slack between 20:14 PDT and 22:14 PDT.We apologize for any disruptions to yo...
Incident: Trouble connecting to Slack
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Intermittent errors when sending messages have been resolved. Additionally, some customers may see inaccurate notification badge counts which can be resolved with a hard reload to clear temporary local cache. Apologies for the trouble today and thank you for your patience.
Incident: Authorization Failure Errors Connecting to the Slack MCP Sever
majorSource not attested
Last archived state: investigating
View archived record details
investigating
We have resolved the issue that was causing users to experience authorization failures when connecting certain third-party integrations to Slack.We apologize for any inconvenience this may have caused and thank you for your patience.
This issue is now resolved for all users.Current status and recent actions taken: We identified the cause as a login routing component that had incorrect entries, which prevented users from being directed to their workspace correctly. A fix has been deployed to address this issue. Previous impact to end users: Users attempting to log in via SSO may have encountered errors requiring them to refresh their browser multiple times before successfully accessing...
Incident: Issues with App Mentions, Grid Migrations, and Notifications
majorSource not attested
Last archived state: investigating
View archived record details
investigating
This issue is now resolved for all users.Current status and recent actions taken: The issue is now resolved, and users should no longer be experiencing any trouble with when using app mentions, migrations, and push notifications. Enterprise Migrations should also be completing as expected.Scope: This issue wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Developers may have experienced issues in ...
