Partial Degradation Impacting Usergroups

What to do

• Check whether your product depends on Slack. 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 57m it lasted.

  Anything that failed between 2026-06-01 02:08 UTC and 2026-06-01 03:05 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 3

1. updateJun 1, 2026, 2:08 AM UTC

   We are currently investigating a partial degradation impacting usergroups. We’ll provide an update as soon as we have more information to share and are sorry for any inconvenience this issue is causing.

   provider

2. updateJun 1, 2026, 2:38 AM UTC

   We continue to investigate the issue and have identified a recent deployment as a likely trigger. Users may experience issues with user groups, including failed @mentions or groups appearing unavailable. We are actively working on restoring functionality and will provide another update as soon as possible.

   provider

3. updateJun 1, 2026, 3:05 AM UTC

   Our investigation has determined that the issue is isolated to a single customer environment and is not impacting the broader service. As a result, this incident will be removed from the status page and we will continue to work directly with the affected customer to address their issue.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.