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.
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.
update
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.
update
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.
May 2026
Trouble with Slack - General Slack functionality issues
This issue is now resolved for all users.
Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue.
Scope: This issue affected Slack users globally.
Previous impact to end users: Slack users experienced difficulties accessing Slack features, including Messaging, Workflows, Apps, Integrations, APIs, Canvas, and Connections, beginning at 22:21 UTC on May 27, 2026. Following an infrastructure change, a cascading scheduling failure caused widespread service impact across all regions and clients. Slack services largely returned to normal operational levels at 05:45 UTC on May 27, with residual impact that remained during the deployment. A brief issue with Canvas surfaced at 10:00 UTC on May 28 that lasted until approximately 12:30 UTC.
Required resolution steps: No steps required.
We apologize for any disruptions to your day. We'll undertake a full investigation of the incident, establishing the technical trigger, the mechanism of failure, and preventative measures to avoid further disruptions.
update
Slack users continue to experience permissions-related issues such as: unable to manage channels, add Canvas to tabs, update statuses, convert public to private channels while we work on a complete restoration.
We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
Remediation efforts via configuration adjustments and deployment will take several hours to complete to fully resolve channel management and status issues. Slack users may continue to experience intermittent impact.
We'll be back with another update in 30 minutes when we have news to share.
update
Remediation efforts via configuration adjustments and deployment are in progress. Users may still run into issues updating their status and managing channels.
We’ll provide another update in 30 minutes or as soon as we have more information, and again we are sorry for the inconvenience this is causing.
update
Recovery activities continue, and restoration efforts are progressing well. Slack users should now be able to edit Canvases as the errors have dropped.
We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
Our work on this issue is still ongoing.
Current status and actions being taken: Remediation efforts are underway via configuration adjustments and deployment. We're still working to resolve the issues with Canvas.
We'll be back with another update once we have news to share.
update
We continue to investigate the issue, and are gathering the resources necessary to restore services.
We’ll provide another update in 30 minutes or as soon as we have more information, and again we're sorry for the inconvenience this is causing.
update
Users continue to experience issues with their ability to manage channels, Canvas edits not saving, and user statuses not clearing or updating correctly. Investigations are underway.
We're working with urgency to improve platform stability and reduce impact. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
We continue to investigate the issue and are working with urgency to improve stability and reduce impact.
We’ll provide another in 30 minutes or sooner, including further details on current actions being taken. We're sorry for the inconvenience this is causing.
update
We're investigating a new impact to Slack.
Current impact to end users: Slack users are experiencing issues with managing channels, statuses aren't clearing or updating correctly, and edits on Canvas aren't being saved.
We'll provide an update within 30 minutes including further details on current actions being taken.
update
Slack services have largely returned to normal operational levels. Messaging, Workflows, Apps, Integrations, APIs, and Connections have all been restored.
We'll continue with the final restoration activities and we'll provide updates as significant developments occur.
update
Slack services continue to progress through the final stages of recovery activities to restore functionality across all services.
We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
Recovery activities continue, and restoration efforts are progressing well. Platform stability is improving, and no further customer impact is expected.
We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.
update
We’re glad to inform you that the Workflow Builder job backlogs were cleared and workflow execution has returned to normal. We continue progressing through the final stages of recovery activities across affected service areas as overall platform stability improves.
We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
Cleanup and recovery efforts continue. Workflow builder job backlogs are being drained. Event subscriptions have been re-enabled. No further impact is expected. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
Workflow builder jobs that were triggered during the disruption period have been replayed and will complete over the next several hours. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
Messaging latency has now cleared. Newly triggered workflows should start and complete as normal. Workflows that executed during the impact period ending at approximately 7pm PDT may not have completed. Customers may notice delayed workflow execution for jobs that triggered during the disruption period. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
We are continuing to work on implementing fixes to fully resolve the issue. Messaging should now be recovered. Users may continue to experience issues with workflow steps completing. Empty pills instead of @-mention; delayed reacji; mismatch in Channel member count and channel membership; and slow loading of messages, user avatars, and unfurls should now all be working properly. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
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 @-mention
Delayed reacji
Mismatch in Channel member count and channel membership
Slow loading of messages, user avatars, and unfurls
We are working with urgency to improve platform stability and reduce impact. We’ll provide an update in the next 30 minutes or sooner, if additional information becomes available.
update
We continue to investigate the issue, and are implementing fixes to restore services. We're starting to see some improvements from the fixes implemented so far. We’ll provide another update as soon as we have more information, and again we are sorry for the inconvenience this is causing.
update
We're investigating a new incident.
Current impact to end users: We’re aware of an issue affecting workflows, message edits, channel renames, apps, and channel creations.
We'll provide an update within 30 minutes including further details on current actions being taken.
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 longer than expected — or failed to complete in a timely manner.
Required resolution steps: No additional steps are required.
We apologize for any disruptions to your day.
update
We've identified the trigger, causing slow file and emoji uploads in Slack, and have deployed a fix. At this time, we are monitoring the environment to confirm full resolution.
Current status and actions being taken: We've identified a frontend error as the cause of the issue and have deployed a fix. We're actively monitoring our health metrics to confirm the fix has resolved the issue for all users.
Estimated time to resolution: No ETA at this time.
Scope: Users globally may be experiencing this issue.
Current impact to end users: Some users may experience slowness when uploading files and emojis in Slack. Attaching or sending files may be taking longer than expected — or failing to complete in a timely manner.
Known workarounds: No workarounds at this time.
We'll provide another update as soon as we have more information to share.
Some Slack users experienced issues where Huddle AI summaries weren't being generated. Users also appeared to be showing as in a huddle after it had ended.
We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support.
We apologize for the inconvenience and any impact this may have had.
The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally.
If you are still experiencing any trouble, please perform a hard reload of Slack by pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.
update
Our work on this issue is still ongoing.
Current status and actions being taken: We've identified a potential cause related to an internal infrastructure component responsible for processing background tasks. Several nodes running this component were experiencing resource exhaustion and CrashLoopBackOff errors, causing connectivity failures to our message queue brokers. A revert of a recent configuration change is currently rolling out and we're seeing signs of improvement — 503 errors are trending down and some impacted pods are stabilizing.
We'll continue monitoring the progress. We'll be back with another update once we have news to share. Thank you for your patience.
update
Our work on this issue is still ongoing.
Current status and actions being taken: We're investigating reports of slow loading times, errors when updating workflows, editing messages, creating or renaming channels, reactions, and issues with file uploads and third-party integrations. Some users may encounter failures when posting images or using add-ins.
We'll be back with another update once we have news to share.
update
We're investigating a new incident.
Current impact to end users: We’re aware of an issue affecting file uploads, message edits, channel renames, and channel creations.
We'll provide an update within 30 minutes including further details on current actions being taken.
EKM customers were previously experiencing issues with channel loading and message delivery
Users who rely on Enterprise Key Management (EKM) may have experienced elevated latency and errors across messaging, channel loading, workflows, and file operations starting around 5:55 AM PDT on May 11, 2026. Impact was mitigated and the incident was brought under control at 9:16 AM PDT on May 11, 2026.
We've deployed fixes addressing the root cause of the elevated encryption key request load. If you continue to experience trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and thank you for your patience.
update
Our work on this issue is still ongoing.
Current status and actions being taken: Customer impact effectively stopped around 8:00AM PT and has remained stable. Our monitoring has shown no further instability and we have considered this incident under control. We are continuing to monitor closely and we'll update again when there's another meaningful update to share.
We apologize for the disruption.
update
Our work on this issue is still ongoing.
Current status and actions being taken: Our monitoring has shown no further instability and we have considered this incident now under control. We are continuing to monitor closely.
We'll provide another update should we find any further information of note. We apologize for the disruption.
update
Current status and actions being taken: We have identified contributing factors to the issue impacting EKM customers and have taken mitigating actions, including reducing the rate of KMS requests by approximately 50% and increasing cache capacity. We are continuing to monitor closely and are actively investigating the underlying cause in partnership with our third-party provider.
Estimated time to resolution: The incident has been stable for over an hour with no new customer-facing impact detected.
Scope: Customers using Enterprise Key Management (EKM)
Current impact to end users: Customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds.
Known workarounds: No known workarounds at this time.
We'll provide another update by 9:50 AM PT. We apologize for the disruption.
update
Current status and actions being taken: We're continuing to investigate elevated error rates affecting a subset of users. We've identified additional load contributing to the issue and have taken steps to reduce it. We've also engaged our third-party vendor to assist in providing additional troubleshooting.
Estimated time to resolution: Under investigation. No ETA available at this time.
Scope: Customers using Enterprise Key Management (EKM)
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds.
Known workarounds: No known workarounds at this time.
We'll provide another update in 30 minutes or as new information becomes available. We apologize for the disruption.
update
Current status and actions being taken: We're continuing to investigate elevated error rates affecting a subset of users. We've identified additional load contributing to the issue and have taken steps to reduce it.
Estimated time to resolution: Under investigation. No ETA available at this time.
Scope: Customers using Enterprise Key Management (EKM)
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds.
Known workarounds: No known workarounds at this time.
We'll provide another update in 30 minutes or as new information becomes available. We apologize for the disruption.
update
Current status and actions being taken: We’re investigating a recurrence of a previous incident causing elevated errors and high latency for EKM customers. As a precaution, EKM backfills have been paused to reduce load. Teams are evaluating pod scaling and assessing a high-volume load test workload contributing to EKGen traffic. A bridge is active with EKM and EKGen engineers engaged, and third-party infrastructure teams have been re-engaged as a potential contributing factor.
Estimated time to resolution: Under investigation. No ETA available at this time.
Scope: Customers using Enterprise Key Management (EKM).
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications, Workflow, DMs, and activity feeds.
Known workarounds: No known workarounds at this time.
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
update
This issue is now resolved for all users.
Current status and recent actions taken: Our upstream provider has successfully implemented a fix. Following a period of stable monitoring, all services have been restored. Customers should no longer experience issues accessing Slack.
Scope: This issue didn’t affect any specific region, but a percentage of Enterprise Key Management customers may have experienced an impact globally.
Previous impact to end users: Customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading channels. Additionally, they may have experienced delays with all messaging activity, including notifications and activity feeds.
Required resolution steps: No additional steps are necessary.
We apologize for any disruptions to your day.
update
We’re investigating this issue:
Current status and actions being taken: Our upstream provider has implemented a fix and is continuing their investigation. In the meantime, we continue to observe improved health metrics. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved
Estimated time to resolution: No ETA at this time.
Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.
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’re investigating this issue:
Current status and actions being taken: We continue to monitor the issue as our upstream provider continues their work toward a resolution. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved.
Estimated time to resolution: No ETA at this time.
Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.
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’re investigating this issue:
Current status and actions being taken: We're seeing consistent improvement in our health metrics while our upstream provider has begun implementing a fix on their side. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved.
Estimated time to resolution: No ETA at this time.
Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.
Known workarounds: No known workarounds at this time.
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
update
We’re investigating this issue:
Current status and actions being taken: We’ve deployed a fix that has improved our cache hit ratio and are observing recovery in our health metrics. In parallel, we're monitoring for updates from our upstream provider. Affected customers may already be seeing improvements, and we’ll continue to monitor the situation closely until it is fully resolved.
Estimated time to resolution: No ETA at this time.
Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management customers may experience impact globally.
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading channels. Additionally, they may experience delays with all messaging activity, including notifications and activity feeds.
Known workarounds: No known workarounds at this time.
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
update
We’re investigating this issue:
Current status and actions being taken: We believe an issue with an upstream provider may be impacting some Slack services. We’re partnering with them to help with our investigation and are waiting on additional details from their analysis. In parallel, we’re actively reviewing the cache configuration to alleviate the impact.
Estimated time to resolution: No ETA at this time.
Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management (EKM) customers may experience impact globally.
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels.
Known workarounds: No known workarounds at this time.
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
update
We’re investigating this issue:
Current status and actions being taken: We’re seeing renewed, elevated error rates and latency affecting customers using Enterprise Key Management (EKM). Affected customers may experience issues sending messages and loading some channels. Our team is actively investigating this issue.
Estimated time to resolution: No ETA at this time.
Scope: This is not affecting any specific region, but a percentage of Enterprise Key Management (EKM) customers may experience impact globally.
Current impact to end users: Customers using Enterprise Key Management (EKM) may experience issues sending messages and loading some channels.
Known workarounds: No known workarounds at this time.
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
update
Between approximately 10:55 AM and 11:10 AM PDT, customers using Enterprise Key Management (EKM) may have experienced issues sending messages and loading some channels. Error rates have returned to normal levels and customers should now see expected performance. We are continuing to investigate the underlying cause and monitoring closely. We apologize for the disruption.
Scheduled Grid Migrations are experiencing extended downtime
This issue is now resolved.
Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing.
Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack.
Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window.
Known workarounds: No workarounds needed at this time.
We apologize for how this incident affected you and your business.
update
Users who are undergoing scheduled Grid Migrations are experiencing extended downtime. Downtime is expected during a Grid Migration however it's taking longer than usual. During the downtime users are unable to access Slack until the migration completes. We've identified an issue with Job Queues, which may be the cause and are investigating this further. The next update will be provided once additional information becomes available.
This issue is now resolved for all users.
Current status and recent actions taken: A fix has been deployed that resolved the underlying cause of this issue. Our health metrics have returned to normal levels and workflows are running as expected.
Scope: Users in the EU region — primarily teams based in Central Europe — experienced elevated workflow failure rates.
Previous impact to end users: Users may have experienced workflows failing to run, with the first step remaining stuck in an initialized state. Some users in the EU region may also have experienced general slowness when using Slack.
Required resolution steps: No steps are required. Workflows should be running normally. If you continue to experience any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).
We apologize for any disruptions this may have caused to your day.
update
A fix has been deployed to address the elevated latency in EU backend services. The team is monitoring the environment to ensure service stability and full recovery. We'll provide another update as soon as possible.
update
The investigation identified elevated latency in EU backend services as the cause of workflows not completing. A subset of workflow trigger attempts is impacted, primarily, EU users. Pod restarts have stopped, and error rates are improving. A fix is being prepared and will be deployed shortly. We'll provide another update as soon as possible.
update
Some users are experiencing issues with workflows. Triggered workflows may fail to complete, with the first step not executing. We'll provide another update as soon as possible.
At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack.
We identified that infrastructure changes to our Search cluster caused a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity and restoring affected search shards. We also blocked certain Search traffic to contain secondary impact while the cluster was being recovered.
As of 00:45 UTC, May 1, 2026, Slack Search functionality is fully operational.
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.
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.
August 2026
Incident: Trouble Using Search Bar For Some Admins
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
July 2026
Incident: Feature Degradation Affecting the Receipt of Emails in Slack
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Issue sending messages to channels via certain Workflows
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Receiving reminders in Slack issue
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
June 2026
Incident: Chat functionality unavailable on Slack Help page
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Trouble submitting workflow forms with file attachments on Android.
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Trouble loading SSO configuration settings for some workspace admins
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Trouble performing some actions
minorSource not attested
Last archived state: resolved
View archived record details
resolved
This issue is now resolved for all users.We apologize for any disruptions to your day.
Incident: Slack Messaging issue
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
Incident: Child windows displaying content at half height
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
