Is Slack down?

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.

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

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.

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: Known workarounds: 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.

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.

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.

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.

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.

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.

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.

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.

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'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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.