Fix Discord No Route or RTC Connecting voice errors
What to do first
Troubleshoot Discord No Route or RTC Connecting voice errors by following the official decision path while preserving user data.
This is a general troubleshooting guide, not an announcement of a current outage.
Affected products and symptoms
- Product
- Discord
- Versions and conditions
- Discord desktop and browser apps
- Error codes and identifiers
- No Route · RTC Connecting · ICE Checking
Symptoms
- No Route, RTC Connecting, or ICE Checking never completes
- Voice alone fails on a particular network
Causes and conditions
Besides a Discord outage, the router, ISP, VPN, or firewall can interfere with the route to voice servers.
Before you start
- Before changes, record and preserve Discord Status, error state, ISP, VPN state, region, and time.
- Change one item at a time and record the original symptom after each stage.
Precautions
- Do not bulk-delete unrelated settings or data.
- Exclude personal data and credentials; share only the necessary parts of Discord Status, error state, ISP, VPN state, region, and time.
Step-by-step instructions
Check discordstatus.com for Voice or regional incidents. If timing matches, preserve local settings and wait for recovery.
Compare Waiting for Voice Server and similar states with Discord Status and time. Local DNS changes cannot fix an official outage.
Quit Discord, then restart the computer, router, and modem. On shared or managed networks, ask the administrator before restarting equipment.
At home, wait for modem link before starting router and PC. Users should not restart school or company network equipment.
Retry with an optional VPN or proxy disconnected, and test an approved alternate network if available. A network-dependent result isolates the route.
An alternate network is a diagnostic comparison. If mobile works, investigate UDP or VPN restrictions on the original network.
Update Discord and check OS or security-software allow rules. If unresolved, send Discord Support the error state, ISP, region, and timestamp.
Record error name, channel, server region, and time; the state identifies the connection stage.
Check the result
- rejoin the same voice channel and confirm several minutes of stable two-way voice and reconnection
- Check adjacent basic functions for side effects from the change.
If the problem continues
- contact Discord Support if multiple networks fail, or the network administrator/ISP if only one does
- When continuing with a workaround, preserve original files or account data separately.
Scope of this guide
Troubleshooting guide — Troubleshoot Discord No Route or RTC Connecting voice errors by following the official decision path while preserving user data.
Frequently asked questions
Why does text work while voice fails?
Voice uses a separate real-time path that can be affected independently by VPNs and firewalls.
Should I change DNS first?
First check Status, restart, and compare VPN/network behavior. Do not alter managed DNS without approval.
Official sources and dates
Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.
Related troubleshooting guides
- Fix a Discord microphone that is not detected
- Fix Acrobat “A running instance has caused an error”
- Fix Firefox “already running” or profile-in-use errors
- Identify the source of Chrome “Managed by your organization”
- Fix OneDrive “Can’t open file” or “Make sure OneDrive is running”
- Fix OneDrive error 0x8007016a