- Level
- confirmed
- Worst impact
- Degraded
- Components
- Messaging
- Down Index
- 32of 100
What to do
Check whether you use Slack Messaging. 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 0m it lasted.
Anything that failed between 2026-06-16 01:19 UTC and 2026-06-16 01:19 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 1
- update
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.
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-0f82274317
Is Slack still down?
No, this incident was resolved 2026-06-16 01:19 UTC. For Slack's live state, see https://down.guide/slack.
How long did it last?
0m, from 2026-06-16 01:19 UTC to 2026-06-16 01:19 UTC, by the times Slack posted.
What was affected?
Slack named Messaging.
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.