Why does RTC Connecting happen on only one specific server?

When the error affects only one Discord server while others work fine, that specific server's assigned voice node is experiencing downtime. Asking a server admin to change the channel's Region Override fixes it instantly.

Will using a VPN fix the RTC Connecting error?

If your local school, office, or home ISP is blocking UDP ports, connecting to a VPN with UDP or WireGuard support will bypass the network block and restore your voice connection.

Can Discord RTC Connecting be caused by server outages?

Yes. When Discord or Cloudflare suffers an outage, voice gateways in specific regions can stall. You can check our Voice Radar tool to confirm whether voice nodes in your area are operational.

What is the difference between RTC Connecting and No Route errors?

RTC Connecting means Discord is trying to reach a voice server but cannot negotiate the handshake. No Route means your computer reached the server, but your local firewall or router blocked the return UDP audio path.

Does running Discord as Administrator fix voice connection loops?

Yes, running Discord as Administrator gives the app full permission to open network sockets and bypass local Windows permission restrictions.

Back to Voice & Outage Radar

Voice & RTC5 min readVerified 2026 Solution

How to Fix Discord 'RTC Connecting' or 'Connecting' Loop Error

Quick Summary: The RTC Connecting error happens when Discord WebRTC voice packets get blocked by firewalls, DNS timeouts, router UDP restrictions, or VPN routing.

What Causes This Error

Discord uses WebRTC (Web Real-Time Communication) to send live microphone audio and video over UDP packets. Unlike ordinary website traffic that uses TCP, UDP packets do not request delivery receipts, which keeps your voice latency ultra-low. However, if your home Wi-Fi router, third-party antivirus firewall, or internet service provider blocks these UDP ports or throttles the connection, Discord gets stuck in an endless 'RTC Connecting' or 'Connecting' loop. In some cases, a temporary routing failure on Discord's regional voice server also causes the issue.

Quick 30-Second Pre-Flight Checklist

Before changing deep network settings, run through these three basic checks. They fix more than half of all voice dropouts:

1. Run as Administrator

Right-click Discord desktop shortcut and select Run as Administrator so audio capture hooks work.

2. Test Discord Web App

Open discord.com/app in Google Chrome incognito mode to see if the issue is desktop app cache.

3. Power Cycle Wi-Fi

Unplug your router for 30 seconds to wipe corrupted NAT tables and get clean IP routing from your ISP.

Step-by-Step Fixes

Follow in order

Switch the Voice Channel Region Override

If you are a server admin or moderator, right-click the voice channel, click 'Edit Channel', and open the Overview tab. Scroll down to 'Region Override' and change it from 'Automatic' to a nearby geographic location (such as switching from India to Singapore, or from US East to US Central). This forces Discord to disconnect from the stalled media node and assign your channel a completely fresh voice server gateway.

Turn Off High Packet Priority (QoS) in Discord

Discord has a feature called Quality of Service High Packet Priority that signals your router to prioritize Discord audio over other traffic. Unfortunately, many home Wi-Fi routers and ISP modems misinterpret these prioritized packets and drop them entirely. Open Discord User Settings (gear icon), click 'Voice & Video', scroll down to the Quality of Service section, and turn OFF the toggle labeled 'Enable Quality of Service High Packet Priority'. Restart Discord.

Flush DNS Cache and Reset Windows Winsock

Corrupted network cache often prevents Discord from resolving the correct IP addresses for voice gateways. On Windows, press Windows Key + S, type 'cmd', right-click Command Prompt, and select 'Run as Administrator'. Run the command `ipconfig /flushdns` and press Enter. Next, run `netsh winsock reset` and press Enter. Finally, restart your computer to apply the clean network sockets.

Change DNS Servers to Cloudflare (1.1.1.1) or Google (8.8.8.8)

Many local internet service providers use slow or outdated DNS servers that fail to resolve Discord's regional voice endpoints. Open Windows Settings > Network & Internet > change adapter options. Right-click your active connection, select Properties, click 'Internet Protocol Version 4 (TCP/IPv4)', and choose Properties. Select 'Use the following DNS server addresses' and enter 1.1.1.1 as Preferred and 1.0.0.1 as Alternate (or Google's 8.8.8.8 and 8.8.4.4).

Disable Third-Party Antivirus Firewall or Whitelist Discord

Security software like Norton, McAfee, Bitdefender, or Avast often flags Discord's UDP audio packets as suspicious network activity. Temporarily disable your third-party firewall to check if the voice connection establishes immediately. If it connects, add Discord (`%LocalAppData%/Discord/app-*/Discord.exe`) to your antivirus allowed applications list.

Turn Off VPN or Switch Protocol to WireGuard / UDP

If you use a VPN, Discord voice connections will fail if the VPN is tunneling traffic over TCP instead of UDP. Disconnect from your VPN and reconnect to the voice channel. If you must use a VPN for privacy, open your VPN application settings and change the connection protocol from OpenVPN TCP to WireGuard or OpenVPN UDP.

Command Prompt Network Diagnostic Commands

Open Command Prompt or PowerShell as Administrator on Windows. Run these commands to test connection health and wipe stale DNS records:

ipconfig /flushdnsClears corrupted local DNS cache preventing gateway lookups

Safe & Instant

netsh winsock resetRestores default Windows socket catalogs (requires PC restart)

Restart Required

ping -n 8 gateway.discord.ggMeasures packet loss and round-trip time to Discord core servers

Diagnostic Only

Frequently Asked Questions

RTC stands for Real-Time Communication. It refers to WebRTC, the open standard Discord uses to stream voice and video between users without needing third-party plugins.