- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 24of 100
What to do
Check whether your product depends on Discord. 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 16m it lasted.
Anything that failed between 2026-03-12 20:50 UTC and 2026-03-12 21:06 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 2
- investigating
We are aware that bot traffic may be hitting 503 errors and are investigating the issue.
provider
- resolved
We believe the 503s have been 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-0f3a0be2a5
Is Discord still down?
No, this incident was resolved 2026-03-12 21:06 UTC. For Discord's live state, see https://down.guide/discord.
How long did it last?
16m, from 2026-03-12 20:50 UTC to 2026-03-12 21:06 UTC, by the times Discord posted.
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.