Slack had 72 outages in the last 2 years totaling 1105h 11m of downtime — averaging 3 incidents per month.
There were 72 Slack outages since November 20, 2025 totaling 1105h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
Some workspace admins on standalone (non-Enterprise Grid) workspaces may be experiencing an issue where the SSO and authentication configuration page does not display current settings as expected. Admins may see a blank value for the "Require SSO authentication for" field on the admin SSO settings page, which does not accurately reflect the actual backend configuration — SSO settings remain intact and in effect. We are actively investigating this issue and will provide an update as soon as we have more information to share. We apologize for the inconvenience.
We have identified the trigger and developed a fix. We are currently deploying this fix and expect to resolve the issue shortly. We will provide another update once the deployment is complete. We apologize for the inconvenience.
We have successfully deployed the fix to production and the issue is resolved. The Admin SSO and Authentication Configuration page for standalone workspaces should now display the correct settings. If you continue to see outdated information, refresh the SSO Admin page to load the latest changes.
Some users are having trouble loading Slack. Performing certain actions, channel creation, invitation, and join operations may result in a degraded experience. Thank you for your patience while we continue to investigate the situation.
This issue is now resolved for all users. We apologize for any disruptions to your day.
We are aware that some users on the Slack Android app are unable to submit workflow forms that contain a required file upload field. After a file is selected, the Submit button becomes disabled and the form cannot be completed. Users on Slack for iOS and Slack for web are not affected. We are actively investigating the issue and working to identify the root cause. We'll provide an update in 60 minutes or sooner if additional information becomes available.
We have identified the cause of this issue and confirmed it affects a small subset of users on a single version of the Slack Android app. Users on other Android versions, iOS, and web are not affected. A fix is already available and will begin rolling out to Android users tomorrow. We will provide an update as soon as additional information becomes available.
A fix for this issue has been delivered in a new version of the Slack Android app, and rollout has now begun. Android users will start seeing the updated app version become available in the Google Play Store as the rollout progresses. Once updated, users who were experiencing issues submitting workflow forms containing a required file upload field will be able to do so successfully. We will continue to monitor the rollout and provide another update as additional information becomes available.
The rollout of the new version of the Slack Android app is ongoing and may take up to several days to fully complete. We continue to monitor the rollout and will provide another update when we have more information to share. Thank you for your patience with us while we work through this.
On June 19, 2026 at 13:12 UTC, we completed a rollback of the configuration change, which resolved the notification delivery failure. Push notifications are now functioning normally for Android users. 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.
This issue has been resolved. Android users who were experiencing issues submitting workflow forms containing a required file upload field can now do so successfully. A fix was delivered via a new update to the Slack Android app. Users who are still experiencing this issue should update the Slack app from the Google Play Store to resolve it. No other action is required. We apologize for the inconvenience and thank you for your patience.
Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.
We're aware of an issue affecting the Slack desktop app. Users may find that content in child windows, such as channels or documents opened in a separate window, displays at reduced height. We’ve identified the technical trigger and are deploying a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.
We’ve deployed a fix and are now performing validations. We'll provide an update in 30 minutes or sooner if additional information becomes available.
We've validated that the fix resolved the issue and child windows are now displaying content as expected. You may need to reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. We're sorry for the disruption this caused to your day.
Some users in EMEA may be failing to receive 2FA codes via SMS when logging into Slack. We are investigating the trigger and working to resolve this incident as quickly as possible. We will provide another update in 30 minutes or sooner as we have more details to share.
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 action to avoid a repeat in the future.
We're investigating a new incident. Current impact to end users: Some administrators may be experiencing errors managing members.We'll provide an update within 30 minutes including further details on current actions being taken.
We're looking into an issue where some users may be unable to add new members, send invites, or run macros on their workspaces. We're on the case and will provide another update as soon as we have more details to share. We apologize for any disruption to your work. Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace. We'll provide an update within 30 minutes or sooner if additional information becomes available.
We have identified the cause of the issue preventing some workspace admins from adding new members via the Admin page as a recent change and are in the process of rolling back this change. Current impact to end users: Some users may encounter errors when attempting to add or manage members, send invites, or run macros on their workspace. Known workaround: Inviting members via the Slack client workspace menu (workspace name → Invite people to workspace) is currently working as expected. We'll provide an update within 30 minutes or sooner if additional information becomes available.
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 been unable to run macros on their workspaces. Workspace Admins should now be able to add new members via the Manage Members admin page. A page refresh may be required. We apologize for the disruption to your work.
We're investigating a new incident. Current impact to end users: Some users may be experiencing trouble loading or connecting to Slack. We're on the case.We'll provide an update within 30 minutes including further details on current actions being taken.
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.
This issue is now resolved for all users. Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored.We apologize for any disruptions to your day.
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 window We apologize for any inconvenience this may have caused.
We are currently investigating a partial degradation impacting usergroups. We’ll provide an update as soon as we have more information to share and are sorry for any inconvenience this issue is causing.
We continue to investigate the issue and have identified a recent deployment as a likely trigger. Users may experience issues with user groups, including failed @mentions or groups appearing unavailable. We are actively working on restoring functionality and will provide another update as soon as possible.
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.
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.