How to Fix Discord "No Route" / RTC Connecting Voice Chat Error

By FixMyError · Updated October 13, 2026 · 8 min read

What Discord's No Route error means

When you click a voice channel and Discord shows "RTC Connecting" forever — or flashes a "No Route" message — it means the voice handshake never completed. Discord is trying to reach its voice servers with real-time audio traffic, but it cannot find a working network route. The rest of Discord keeps working normally: text channels load, messages send, friends are online. Only voice is broken.

That split behavior is the key diagnostic clue. Because chat works, your account and Discord's core servers are fine. The problem is specific to voice traffic, which travels over UDP on specific ports that routers, firewalls, VPNs, and DNS resolvers handle differently than normal web traffic. In the vast majority of cases the fix lives on your device or your local network — a setting or piece of software is silently dropping Discord's voice packets.

Common causes

• QoS High Packet Priority enabled: Discord tags your voice packets as high priority, and many routers and ISPs reject that tag — this is the single most common trigger of No Route.
• VPN or proxy blocking UDP: Discord voice runs over UDP. Many VPNs route only TCP cleanly and break or reroute voice packets.
• Firewall or antivirus blocking Discord: Windows Firewall or a security suite can start blocking Discord's voice traffic after an update changes the executable.
• Stale DNS or a bad network route: your machine may be trying to reach a voice server through an outdated or broken route.
• Wrong voice server region or a Discord outage: a struggling region can break one server while others work, and genuine Discord voice outages make every local fix fail.

How to fix Discord No Route — step by step

Work through these fixes in order. Most No Route cases are fixed by step 1 or 2.

1. Turn off Quality of Service High Packet Priority. Open Discord and click the gear icon next to your username to open User Settings. Go to Voice & Video and scroll down to the Quality of Service section. Toggle off Enable Quality of Service High Packet Priority, then quit Discord completely — right-click the Discord icon in the system tray and choose Quit Discord — and reopen it. Rejoin the voice channel and check whether the error is gone.
2. Restart your router and your device. Power-cycle the network path. Unplug your router and modem from the wall, wait 30 to 60 seconds, plug them back in, and wait until all the status lights return to normal. Restart your computer or phone at the same time. Then open Discord and try the voice channel again — this alone clears a surprising number of No Route errors.
3. Flush your DNS cache. Your machine may be holding a stale route to Discord's voice servers. On Windows, press the Windows key, type cmd, right-click Command Prompt, choose Run as administrator, type ipconfig /flushdns and press Enter. On a Mac, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Close and reopen Discord afterward.
4. Check your VPN and firewall rules. Temporarily turn off your VPN and rejoin the voice channel — Discord voice runs over UDP, which many VPNs block or reroute poorly. If you must keep the VPN on, enable its split tunneling feature and exclude Discord, or switch the VPN protocol to UDP. Also make sure Windows is not blocking Discord: open Firewall & network protection, click Allow an app through firewall, click Change settings, find discord.exe, and check both the Private and Public boxes.
5. Switch to a reliable public DNS. Bad DNS can send Discord's voice traffic down a dead route. On Windows, go to Settings, then Network & Internet, select your connection, and edit the DNS assignment to Manual. Set the preferred DNS to 8.8.8.8 and the alternate to 8.8.4.4 (Google), or 1.1.1.1 and 1.0.0.1 (Cloudflare). Save, restart your network connection, then reopen Discord and try the voice channel.
6. Change the voice channel's server region. If you manage the server, right-click the server name, choose Server Settings, go to Overview, and scroll to the Region Override section. Change it from Automatic to the region closest to you and click Save changes. A mismatched or struggling region is a common reason one particular server refuses to connect while others work fine.
7. Update Discord and check its server status. Let Discord check for updates when it launches — an outdated client can fail newer voice handshakes. On mobile, update Discord through the app store and make sure your phone's operating system is current. Finally, rule out a Discord-side outage by visiting discordstatus.com. If the voice servers are having problems, no local fix will help — you just have to wait it out.

Did this fix it? Quick checklist

• The voice channel shows "Voice Connected" instead of RTC Connecting
• You can hear other people and your microphone indicator lights up when you talk
• The fix survives a full Discord restart
• Voice also works on a different device or network

If No Route only appears on one network — for example a school or office Wi-Fi — that network may be blocking voice traffic outright, and no setting on your device will fix it. Try your phone's mobile data to confirm; if voice works there, the school network's firewall is the cause and only their network admin can change it. Gamers who run Discord alongside a game on a strict NAT setup should also check their router's UPnP setting, since some routers need it to let voice ports open reliably. And if the error returned right after a Discord update, the update may have replaced the executable your firewall knew — re-check the firewall allow-list for discord.exe before trying anything else.