- Level
- confirmed
- Worst impact
- Major outage
- Components
- API
- Down Index
- 39of 100
What to do
Check whether you use Discord API. 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 41m it lasted.
Anything that failed between 2026-08-07 22:21 UTC and 2026-08-07 23:02 UTC may need a replay.Subscribe to Discord's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=discord works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Discord 4
- identified
We're aware of an issue preventing users and bots from sending messages, we're working on fully restoring service
provider
- identified
This issue has expanded and is now affecting all Discord interactions. We're continuing to work towards mitigating the issue.
provider
- monitoring
We've recovered service and are continuing to monitor for recovery.
provider
- resolved
This issue has been fully resolved
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-a5642fd422
Is Discord still down?
No, this incident was resolved 2026-08-07 23:02 UTC. For Discord's live state, see https://down.guide/discord.
How long did it last?
41m, from 2026-08-07 22:21 UTC to 2026-08-07 23:02 UTC, by the times Discord posted.
What was affected?
Discord named API.
What caused it?
Discord hasn't published a root cause. If it does, it shows here.
Where does this come from?
Discord's official status page, https://discordstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.