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