- Level
- confirmed
- Worst impact
- Degraded
- Components
- Messaging
- Down Index
- 40of 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 29m it lasted.
Anything that failed between 2026-06-17 00:38 UTC and 2026-06-17 01:07 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 2
- update
Some users may be experiencing issues performing certain actions in Slack, channel creation, invitation, and join operations may result in a degraded experience. Thank you for your patience while we continue to investigate the situation.
provider
- update
This issue is now resolved for all users. We apologize for any disruptions to your day.
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-973e74b034
Is Slack still down?
No, this incident was resolved 2026-06-17 01:07 UTC. For Slack's live state, see https://down.guide/slack.
How long did it last?
29m, from 2026-06-17 00:38 UTC to 2026-06-17 01:07 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.