Slack: Slack Real-Time Connection Disruption
Affected components: Messaging
Timeline of updates
- resolved
Some Slack customers experienced disrupted real-time connections, delayed message delivery, and errors loading conversation history on October 22, 2026, starting at 16:08 UTC. A large number of active connections closed at once and then reconnected, which briefly strained the services customers rely on to send and read messages. By 16:26 UTC, connections had reconnected and service had returned to normal. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
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-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c066a41ddd3b3974…
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-10-22 18:50 UTC, resolved after 0 min, 1 update(s).
- Title
- Slack Real-Time Connection Disruption
- Vendor
- Slack
- Date
- URL
- https://rewindex.com/company/slack/incidents/1582
Slack profileRecent Slack incidentsAll outages on October 22, 2026Slack in October 2026MarkdownJSON