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.
update
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.
update
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.
Free Plan Customers Are Experiencing Message Failures
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.
update
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.
update
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.
update
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.
update
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.
update
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.
September 2026
Some customers experiencing blurry image previews and download issues
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.
update
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.
update
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.
update
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.
update
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 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.
Known workarounds: None identified yet.
We appreciate your patience as we sort this out.
update
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.
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.
update
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.
update
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.
update
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.
update
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.
August 2026
Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
update
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.
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.
update
We have identified the cause of this issue as a recent change and have started the process of rolling back the problematic change.
update
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.
July 2026
Feature Degradation Affecting the Receipt of Emails in Slack
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.
update
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.
update
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.
Issue sending messages to channels via certain Workflows
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.
update
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.
update
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.
update
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.
update
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.
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.
update
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.
update
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.
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.
update
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.
update
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.
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.
June 2026
Incident: Trouble with Gmail add-on Integration
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Trouble adding multiple users to channels
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: 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 t...
Incident: Some users unable to sign in
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 ac...
Incident: Administrators may experience errors in member management.
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 b...
Incident: Trouble connecting or loading Slack
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Connectivity Issues Affecting Some Users in Europe
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 windowWe apologize for any inconvenience this may have caused.
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.
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 @-mentionDelayed reacjiMismatch in Channel member count and channel membershipSlow loading of messages, user avatars, and unfurlsWe are working with urgency to improve platform stability and reduce impact. We’ll provide an update in the ...
Incident: Severe Latency Impacting All Slack Services
Source not attested
Last archived state: investigating
View archived record details
investigating
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.
Incident: Trouble uploading files and emojis 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: 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 percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced slowness when uploading files and emojis in Slack. Attaching or sending files may have taken...
