Slack: Partial Degradation Impacting Usergroups
Timeline of updates
- update
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.
- update
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.
- resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
eae0177f69c69d54…
Impact, status and times are the vendor’s own, as last archived. View on slack-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Slack, started 2026-06-01 02:08 UTC, resolved after 57 min, 3 update(s).
- Title
- Partial Degradation Impacting Usergroups
- Vendor
- Slack
- Date
- URL
- https://rewindex.com/company/slack/incidents/1558
Slack profileRecent Slack incidentsAll outages on June 1, 2026Slack in June 2026MarkdownJSON