In 60 seconds
- Check Discord Status first when messages, login, and voice fail across devices.
- Compare the web app and mobile app, then Wi-Fi and mobile data, one change at a time.
- If only voice fails, note the RTC error and inspect VPN, firewall, or managed-network restrictions.
Start with the scope of the problem
A service incident and a local connection problem can look almost identical. Before clearing data or reinstalling Discord, check the official status page for active incidents and component-level problems affecting the API, messaging, media, or voice.
If Discord works in a browser but not in the desktop app, the issue is more likely local to the application. If it works on mobile data but not Wi-Fi, focus on the router, DNS, firewall, or network policy instead of the account.
Treat voice-only errors separately
Voice uses a different network path from ordinary messages. An RTC Connecting loop or voice connection error can be caused by a VPN, restrictive workplace or school network, firewall rules, or a router that is not handling the connection correctly.
Record the exact error, test one alternative network, and follow Discord's official voice troubleshooting. Avoid deleting app data until you have ruled out a wider incident and simpler network causes.
Quick checklist
Open Discord Status and check current incidents
Try the web app and one other device
Switch once between Wi-Fi and mobile data
For voice-only issues, record the RTC error before changing settings
What is confirmed — and what needs caution
- Discord publishes component status and incident history.
- Voice failures can have different causes from message or login failures.
- Crowdsourced outage reports alone do not prove a global incident.
- Repeated reinstalls can erase local settings without fixing a network problem.
Primary sources
01Issueureum summarizes public source material in its own words. Product names belong to their respective owners. Check the linked official source for current details.