To find out whether Discord is down, check Discord's own status page and read the row for the part that's failing you, such as API, Gateway, Voice or Client, rather than just the banner at the top. If every row shows Operational, the problem's probably on your side, and Discord's voice-error guide lists what to try next.
Nobody outside Discord can tell you whether it's down at the exact moment you're reading this, and I won't pretend to. What I can do is show you how to read the signals Discord publishes, so you can tell a real outage from a problem with your router, your VPN or your office network.
Where Discord reports outages
Discord runs a public status page. As of Nov 2026 it shows an overall banner, a row for each part of the service, system metrics such as API response time over a day, week or month, and a list of past incidents by date. There's also a Subscribe to Updates option if you'd like to hear about incidents without checking.
The rows are what matter. Discord lists these components:
- API, Media Proxy and Gateway, the plumbing that loads messages and keeps you connected
- Push Notifications and Search
- Voice, the part behind calls and voice channels
- Client, the app itself
- Third-party, Server Web Pages, Payments and the Marketing Site
So "Discord is down" can really mean "Voice is down" while text chat works fine, or "Push Notifications is down" while everything loads but nothing pings your phone. Look at the row that matches your symptom, not just the banner.
What the incident stages mean
When something goes wrong, Discord posts an incident and moves it through a fixed sequence. Knowing the stages tells you whether to wait or keep troubleshooting.
| Stage | What Discord means by it | What you should do |
|---|---|---|
| Investigating | Discord knows about a problem and is looking into it | Stop troubleshooting your own setup and wait |
| Identified | Discord has found the cause and is implementing a fix | Wait; the fix is in progress |
| Monitoring | A fix has been implemented and Discord is watching the results | Try again; most things should be coming back |
| Resolved | Discord considers the incident over | If you're still stuck, the cause is probably on your side |
The past-incident history is useful too. It keeps a day-by-day record, and most days simply say no incidents were reported. As of early November 2026 the history included voice call problems on 30 and 31 October 2026, both titled as issues establishing voice calls and both marked resolved. That's the pattern to look for: a dated entry that matches what you're seeing.
Check Discord's status in six steps
- Open Discord's status page and look at the overall banner.
- Find the row for the part that's failing you, for example Voice if calls won't connect, and see whether it shows Operational or an incident.
- Check Discord's Known Issues articles in its Help Center and the posts from Discord's support account on X, which cover outages and known bugs.
- If everything's clear, restart your modem, router and computer, and check your VPN and firewall.
- Try a different network, such as mobile data instead of your office Wi-Fi.
- If nothing works, contact Discord support with a screenshot of your console logs.
Discord's Known Issues articles sit in the Known Issues, Bugs and Troubleshooting section of its Help Center. Discord has used them for problems such as API errors involving messaging and partially dropping Xbox statuses, and it marks them resolved with a pointer back to the status page.
Reading your symptom: Discord's side or yours?
| What you see | Likely side | What to try |
|---|---|---|
| The status banner or several rows show an incident | Discord | Wait and follow the incident updates |
| Only the Voice row shows an incident | Discord, for calls only | Use text chat until Voice is resolved |
| Every row says Operational but voice is stuck on RTC Connecting | Probably yours | Router, VPN, firewall, network checks |
| "Waiting for Voice Server" | Discord | Check the status page; Discord says this one is on its side |
| Discord loads but no notifications arrive | Check the Push Notifications row | If it's Operational, the cause is probably your device |
| You can't log in or your account is locked | Not an outage | Contact Discord support, not the X account |
The voice errors that point at your own setup
Discord's voice-error guide splits connection errors into two groups. Four of them, ICE Checking, No Route, RTC Connecting and Connecting, are usually caused by something at your end, such as a firewall or a VPN. If you're stuck on the third one, I've written a full page on the RTC Connecting error.
Discord's own fixes for those four are worth knowing:
- Restart your modem, router and computer.
- Ask your internet provider whether there's an outage in your area.
- Make sure your firewall or antivirus allows Discord.
- Check your VPN. Discord says it only works on VPNs that use UDP.
- Talk to your network admin, because work and school networks may block Discord.
- If you're a server admin, change the voice region under Voice Channel Settings, then Overview, then Region Override. Discord says you can do this in private voice calls too.
That VPN line catches a lot of people. If your VPN doesn't carry UDP, voice can hang on one of these errors while Discord itself is fine, which looks exactly like an outage when it isn't.
There's one voice error Discord says is on its side: "Waiting for Voice Server". Discord says it shows in rare cases when it's having trouble with one of its servers, and points you to the status page.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
If the app crashes or won't open at all, that's a different problem. My guide to fixing Discord when it won't work covers that side in full.
What Discord's X support account can and can't do
Discord runs a support account on X that posts updates on known issues and bugs, ongoing outages, clarifying information and tips. It can help with basic troubleshooting and connection problems.
It can't help with 2FA removal or lost account access, disabled or banned accounts, hacked accounts, phone verification, refunds or cancellations, server ownership transfers or terms of service questions. Discord also says contacting it doesn't replace a support ticket. If your problem is your account rather than an outage, go straight to Discord's support routes.
My verdict
I'd start with the status page every time, and I'd read the component rows rather than the banner, because a Voice incident can sit under a mostly green page. Skip reinstalling, clearing caches or switching devices until you've ruled out a listed incident; you'll waste time fixing something that isn't broken. If you run a community or a brand server, subscribe to the status updates so you can tell members what's happening before they start messaging you.
Frequently asked questions
How do I know if Discord is down for everyone?
Check Discord's status page. If the banner or a component row such as Voice or API shows an incident, the problem is on Discord's side. If every row shows Operational, it's probably your connection or device.
Why does Discord say Waiting for Voice Server?
Discord says this error shows in rare cases when it's having trouble with one of its voice servers. Check the status page for a Voice incident.
Does Discord work with a VPN?
Discord says it only works on VPNs that use UDP. A VPN without UDP can stop voice from connecting even when Discord itself is fine.
What does Monitoring mean on Discord's status page?
It means a fix has been implemented and Discord is watching the results before marking the incident resolved.
Can Discord's X account help with a hacked account?
No. Discord says its X support account can't help with hacked, banned or disabled accounts, 2FA removal or lost access. Use a support ticket instead.
