- Level
- confirmed
- Worst impact
- Degraded
- Components
- API, Push Notifications
- Down Index
- 17of 100
What to do
Check whether you use Discord API, Push Notifications. 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 32m it lasted.
Anything that failed between 2026-03-25 15:18 UTC and 2026-03-25 15:51 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 3
- investigating
We are investigating degraded performance affecting some Discord features, including streaming and messaging, due to a networking issue beginning at approximately 7:53 AM PT; our team is actively engaged with our cloud provider to resolve the issue.
provider
- monitoring
We have identified the source of the issues and are monitoring recovery.
provider
- resolved
This incident has 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-4dac96660c
Is Discord still down?
No, this incident was resolved 2026-03-25 15:51 UTC. For Discord's live state, see https://down.guide/discord.
How long did it last?
32m, from 2026-03-25 15:18 UTC to 2026-03-25 15:51 UTC, by the times Discord posted.
What was affected?
Discord named API, Push Notifications.
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.