- Level
- confirmed
- Worst impact
- Degraded
- Components
- Messaging, Apps/Integrations/APIs, Canvases
- Down Index
- 47of 100
What to do
Check whether you use Slack Messaging, Apps/Integrations/APIs, Canvases. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 16h 21m it lasted.
Anything that failed between 2026-05-27 23:00 UTC and 2026-05-28 15:22 UTC may need a replay.Subscribe to Slack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=slack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Slack 21
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- update
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ba0dc43479
Is Slack still down?
No, this incident was resolved 2026-05-28 15:22 UTC. For Slack's live state, see https://down.guide/slack.
How long did it last?
16h 21m, from 2026-05-27 23:00 UTC to 2026-05-28 15:22 UTC, by the times Slack posted.
What was affected?
Slack named Messaging, Apps/Integrations/APIs, Canvases.
What caused it?
Slack hasn't published a root cause. If it does, it shows here.
Where does this come from?
Slack's official status page, https://slack-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.