Slack Real-Time Connection Disruption

What to do

• Check whether you use Slack Messaging. 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-10-22 18:50 UTC and 2026-10-22 18:50 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

1. updateOct 22, 2026, 6:50 PM UTC

   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.

   provider

Corrections

None so far.

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