- Level
- confirmed
- Worst impact
- Degraded
- Components
- Workspace/Org Administration
- Down Index
- 47of 100
What to do
Check whether you use Slack Workspace/Org Administration. 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 1d 6h it lasted.
Anything that failed between 2026-06-09 15:24 UTC and 2026-06-10 21:43 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 8
- update
Some users may experience issues when attempting to add multiple users to channels. Multiple matches error may appear along with a failure to identify team members. This may cause subsequent workflows not to trigger. We're investigating and will let you know as soon as we know more.
provider
- update
Our work on this issue is still ongoing. Current status and actions being taken: We have identified the trigger for this issue and a fix is in the process of deploying. The progress is being monitored and we’ll provide an update as soon as the fix is completely deployed and verified. We'll be back with another update once we have news to share.
provider
- update
This issue is now resolved for all users. Current status and recent actions taken: We identified the trigger for this issue and a fix was deployed. After a period of monitoring, we have concluded that there is no further impact to users. Previous impact to end users: Some users may have experienced issues when attempting to add multiple users to channels and received an error indicating a failure to identify team members. This could have caused subsequent workflows not to trigger. Required resolution steps: No further action is necessary. Thanks for sticking with us as we resolved this. We apologize for any disruptions to your day.
provider
- update
We've received reports that a subset of users may continue to experience issues when attempting to add multiple users to channels using email addresses. These users may encounter a "Multiple matches" error, preventing the intended user from being identified and added to the channel. We’re actively investigating these reports to determine whether additional remediation is required. We'll provide further updates as more information becomes available.
provider
- update
We’re working to reproduce the issue. This will help us identify the underlying cause and provide a resolution. We'll provide further update as soon as more information becomes available.
provider
- update
We’ve identified the cause of the issue and we’re validating a fix to ensure it fully resolves the issue before we deploy it. We'll provide further update as soon as more information becomes available.
provider
- update
We've deployed a fix for the issue and are monitoring to confirm that the issue has been resolved. We'll provide another update as soon as more information becomes available.
provider
- update
We've resolved an issue that could cause incorrect email address tokens to appear when users pasted multiple email addresses into the member invite flow. In some cases, pasted email addresses were incorrectly matched to existing members with similar email addresses, requiring users to manually correct the entries before proceeding. We identified the cause of the issue and deployed a fix to ensure email addresses are now matched correctly when pasted into the invite flow. The issue is resolved for all affected users. If you're still experiencing any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and appreciate your patience.
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-8011b3214b
Is Slack still down?
No, this incident was resolved 2026-06-10 21:43 UTC. For Slack's live state, see https://down.guide/slack.
How long did it last?
1d 6h, from 2026-06-09 15:24 UTC to 2026-06-10 21:43 UTC, by the times Slack posted.
What was affected?
Slack named Workspace/Org Administration.
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.