Discord RTC Connecting and No Route: Fixes That Work in 2026

You click a voice channel, the status line changes to "RTC Connecting", and nothing else happens. A few seconds later it flips to "No Route" and your friends carry on without you. Text works, the server loads, only voice is dead.

Discord's help center article on voice connection errors puts these errors in one group and says they usually mean something on your side is interfering with the connection: a firewall, a VPN or the network itself. That's good news, because you can test each cause in a few minutes. This guide lists the checks in the order that finds the cause fastest.

TL;DR

• RTC Connecting, No Route, ICE Checking and a plain "Connecting" are the same family of error. Discord's help center says they point to your side of the connection.
• Test your phone's hotspot first. If voice works there, the problem is your home network or PC. If it fails there too, look at your account or at Discord's status page.
• Discord only works on VPNs that support UDP. A VPN that is on, but tunnelling over TCP, is a common reason voice fails.
• "Waiting for Voice Server" is different: that one is on Discord's side, and no setting on your PC fixes it.

What RTC Connecting and No Route mean

Discord voice is a live stream of small packets between your app and one of Discord's voice servers. Before any audio flows, your app has to find a working path to that server. RTC Connecting is the app trying to open that real-time connection. No Route is the app giving up because it couldn't find a path. ICE Checking is the step in between, where the app tests candidate paths.

None of this is about your microphone, your headset or your audio settings. It's about whether packets can travel from your device to Discord and back.

Discord splits the voice errors into two groups. These four are blamed on your side:

• ICE Checking
• No Route
• RTC Connecting
• Connecting

The only error Discord puts on its own side is "Waiting for Voice Server". If you're stuck there, check discordstatus.com and wait, because Discord says that state means broad service issues.

Start here: a 60-second test that narrows it down

Before you change any setting, answer one question: does voice work on a different network?

1. Turn on your phone's hotspot and connect your computer to it.
2. Join a voice channel.

If it works, the cause is your normal network, your router, a firewall, a VPN or your provider. Go through the fixes below in order. If it still fails on the hotspot, the cause is probably your PC (firewall, antivirus, VPN software) or your account, and the network steps will waste your time.

The fixes, in order of how often they work

Discord's own checklist is short. Follow it in this order.

1. Check Discord's status page

Open discordstatus.com. If voice is degraded there, stop. Nothing you change will help.

2. Restart the modem, the router and the computer

Discord lists this first and says it works more often than you'd expect. Unplug the modem and router for 30 seconds, plug them back in, wait until the lights settle, then restart the computer. A restart clears stale connection state that causes half-open routes.

3. Check for a provider outage

If other apps feel slow or drop, ask your internet provider about outages in your area. Voice is the first thing to break when a connection is unstable.

4. Allow Discord through your firewall and antivirus

Security software sometimes blocks the UDP traffic voice needs. Add Discord to the allowed apps list in Windows Defender Firewall or macOS's firewall settings, and add it to the exclusions of any third-party antivirus. If you want a quick answer, disable the antivirus for a few minutes and reconnect. Turn it back on and keep the exclusion if that fixed it.

5. Check your VPN

This is the step most guides skip, and it's where Discord's own page is specific: "Discord only works on VPNs that have UDP". More on this in the next section.

6. Ask your network admin

If you're on a work, school or dorm network, Discord may be blocked or limited. Discord's help center says exactly that. Ask the administrator whether Discord's voice traffic is allowed. You can't fix a policy block from your side without breaking the network's rules.

7. Change the voice region

If you manage the server, change the region temporarily: Voice Channel Settings > Overview > Region Override. You can also change the region inside a private voice call. A different region means a different voice server, which sometimes avoids a bad route.

8. Flush your DNS cache

On Windows, open Command Prompt as administrator and run:

ipconfig /flushdns

Then restart Discord. This clears stale DNS entries and costs nothing to try. It's a low-odds fix, so do it after the checks above.

9. Contact Discord with a console log

If nothing works, Discord's support team asks for a screenshot of your console logs. Install Discord's PTB or Canary client, join the failing voice channel, press Ctrl+Shift+I on Windows or Option+Command+I on Mac, open the Console tab, and screenshot the full page with the error messages visible. Send it through dis.gd/support.

Where a VPN fits: cause, and sometimes cure

VPNs show up on both sides of this error.

When a VPN is the cause

Voice runs on UDP, a fast protocol that doesn't wait for every packet to be acknowledged. That suits real-time audio. If your VPN sends all traffic through a TCP tunnel, the voice packets get wrapped inside a protocol that retransmits and waits, and the real-time connection stalls or fails.

Discord's help center makes this explicit with its line about UDP. Two practical rules follow:

• Protocol matters more than brand. WireGuard runs over UDP. OpenVPN can run over UDP or over TCP, and the TCP option exists for networks that block everything else. For Discord voice, pick the UDP option.
• Server distance matters. A server on the other side of the world adds delay and a longer route to a voice server, and can make "Connecting" last longer.

To test whether your VPN is the culprit, join a voice channel with the VPN off. If it works, turn the VPN on and switch protocol and server one at a time. What is a VPN protocol explains how to tell them apart.

When a VPN is the cure

Sometimes the route from your provider to Discord is poor. Providers send traffic through different peering points, and a bad one can drop UDP packets or add seconds of delay. A VPN sends your traffic out through a different path, which can fix the route even though nothing is wrong with your setup.

You can check this with a simple A/B test. Join the same voice channel with and without the VPN and compare your ping in Discord's voice connection panel. If the VPN lowers it or fixes the connection, your provider's route was the problem. If you see no difference, the VPN is neither the cause nor the cure, and the error is elsewhere. For a refresher on reading latency, see what is ping.

A VPN can't fix a school or office network that blocks Discord on purpose, and it can't fix a Discord outage. If a network blocks Discord's voice traffic, it often blocks VPN traffic too. Atomic VPN runs WireGuard by default, which means UDP, so it fits the requirement Discord states. If you want a longer walkthrough of a first connection, see how to set up a VPN.

Symptoms and likely causes

The order to remember

Hotspot first, then restart, then firewall, then VPN protocol, then region. If you've done all of that and "Waiting for Voice Server" is what you're seeing, it's Discord's side and the only fix is time.