- Level
- confirmed
- Worst impact
- Degraded
- Components
- Messaging
- Down Index
- 46of 100
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 6h 20m it lasted.
Anything that failed between 2026-10-01 12:39 UTC and 2026-10-01 18:59 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 6
- update
We're aware that some customers on our free plan are experiencing message-sending limit blocks in an unusual spike pattern, which is preventing them from sending messages. We're investigating why this message limit was triggered unexpectedly for some teams. If you're affected, you may be temporarily unable to send messages until this is resolved. We'll provide an update in 30 minutes or sooner if additional information becomes available.
provider
- update
We identified that a third-party app is stuck in a loop that has triggered billions of messages. This is causing free plan users to exceed messaging limits. We apologize for the inconvenience and will provide another update as soon as we have more details to share.
provider
- update
A feature toggle ramp-up caused an app integration to repeatedly post messages in a processing loop. This pushed free plan customers over the message volume threshold, triggering the sending block. We're working to restore access and are actively working on remediation options for impacted Workspaces. We apologize for the inconvenience and will provide another update as soon as we have more details to share.
provider
- update
We’ve identified a potential fix for this issue and we’re working on getting this out to users as quickly as possible. We’ll be back once we have another update to share. Thank you for your continued patience as we work towards a solution.
provider
- update
Deployment of the fix is underway to restore access for impacted free plan workspaces, and we are actively monitoring the environment. More information will follow as we progress through this stage of remediation.
provider
- update
A messaging integration briefly caused some free-plan workspaces to exceed their daily messaging limit, blocking them from sending messages. We took action to lift the sending block for all affected free-plan workspaces, and have confirmed messaging is now restored. 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
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-0f8d14f216
Is Slack still down?
No, this incident was resolved 2026-10-01 18:59 UTC. For Slack's live state, see https://down.guide/slack.
How long did it last?
6h 20m, from 2026-10-01 12:39 UTC to 2026-10-01 18:59 UTC, by the times Slack posted.
What was affected?
Slack named Messaging.
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.