Is Slack down?

Product match: components.

Read the provider’s incident report

1. 2026-10-22T11:50:50-07:00 ·

   Some Slack customers experienced disrupted real-time connections, delayed message delivery, and errors loading conversation history on October 22, 2026, starting at 16:08 UTC. A large number of active connections closed at once and then reconnected, which briefly strained the services customers rely on to send and read messages. By 16:26 UTC, connections had reconnected and service had returned to normal. We apologize for how this incident affected you and your business. We will undertake a full

Product match: components.

Read the provider’s incident report

1. 2026-10-13T17:23:07-07:00 ·

   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.

Product match: components.

Read the provider’s incident report

1. 2026-10-09T08:35:31-07:00 ·

   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. 2026-10-09T09:20:04-07:00 ·

   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. 2026-10-09T16:58:33-07:00 ·

   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.

4. 2026-10-12T10:03:31-07:00 ·

   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 inconvenience and thank you for your patience.

Product match: components.

Read the provider’s incident report

1. 2026-10-01T05:39:35-07:00 ·

   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.

2. 2026-10-01T05:56:59-07:00 ·

   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. 2026-10-01T06:58:40-07:00 ·

   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. 

4. 2026-10-01T07:31:24-07:00 ·

   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. 2026-10-01T11:52:01-07:00 ·

   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. 2026-10-01T11:59:35-07:00 ·

   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 futur

Product match: components.

Read the provider’s incident report

1. 2026-08-13T14:21:41-07:00 ·

   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. 2026-08-13T14:49:40-07:00 ·

   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. 2026-08-14T12:35:56-07:00 ·

   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.

4. 2026-08-14T13:20:26-07:00 ·

   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. 

5. 2026-08-14T14:39:25-07:00 ·

   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.

6. 2026-08-17T14:57:51-07:00 ·

   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.

7. 2026-08-20T15:54:59-07:00 ·

   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.

8. 2026-08-25T13:55:43-07:00 ·

   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.

9. 2026-08-27T11:58:04-07:00 ·

   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 channe

10. 2026-09-01T15:51:21-07:00 ·

    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.

11. 2026-09-04T10:00:57-07:00 ·

    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.

12. 2026-09-08T19:37:23-07:00 ·

    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.

Product match: components.

Read the provider’s incident report

1. 2026-09-12T04:04:17-07:00 ·

   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. 2026-09-12T04:29:49-07:00 ·

   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 des

3. 2026-09-12T05:52:08-07:00 ·

   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

4. 2026-09-12T07:10:13-07:00 ·

   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 gatheri

5. 2026-09-12T08:24:18-07:00 ·

   We have confirmed the technical trigger and are preparing a fixCurrent 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:

6. 2026-09-12T13:00:00-07:00 ·

   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.

Product match: components.

Read the provider’s incident report

1. 2026-09-09T17:34:21-07:00 ·

   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. 2026-09-09T17:58:36-07:00 ·

   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. 2026-09-09T18:29:53-07:00 ·

   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. 2026-09-09T18:37:07-07:00 ·

   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. 2026-09-09T20:14:18-07:00 ·

   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.

Product match: components.

Read the provider’s incident report

1. 2026-08-06T15:22:35-07:00 ·

   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. 

2. 2026-08-06T16:11:27-07:00 ·

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

3. 2026-08-06T18:07:04-07:00 ·

   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.

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T17:06:54.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T17:00:00.000Z to 2026-11-08T17:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Slack feature.

The latest status observation was 2026-11-08T16:59:22.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save Slack in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.