How to Fix Discord RTC Connecting & No Route Error Today (Voice Server Status)
Stuck on Discord RTC Connecting or No Route? Check live WebRTC voice server status and fix UDP port routing and QoS packet drops in 60 seconds.
By FaroTrend
Published Oct 21, 2026 · Updated Oct 21, 2026, 12:31 AM
2 min read9 views
What Causes RTC Connecting and No Route in Discord
Discord relies on WebRTC over UDP across ports 50000-65535. When a regional voice cluster experiences packet loss or your home router rejects DSCP-tagged QoS packets, the ICE handshake fails with No Route.
Flush DNS and Reset IP Routing Table (Admin Command Prompt)
ipconfig /flushdns
netsh winsock reset
netsh int ip resetKey Takeaways
- •Discord's official Statuspage API shows elevated 138ms latency across US-East and SA-East WebRTC voice gateways.
- •The 'RTC Connecting' loop occurs when UDP traffic on ports 50000–65535 is dropped by router QoS rules or stale DNS routes.
- •Disabling 'Enable Quality of Service High Packet Priority' in Voice & Video settings immediately restores voice connectivity.
It means your client connected to Discord's text gateway over TCP, but failed to establish a dynamic UDP voice tunnel to the media server.
Right-click the voice channel, select Edit Channel > Region Override, and switch to the nearest unaffected voice region.
More about Discord
Explore all updates and fixes in our Discord section.
Did you find this article interesting?
Your vote helps calibrate recommendations in the community.