Why Discord Voice Reconnects Every Few Minutes on Carrier-Grade NAT

If you use Discord voice chat and your connection drops and reconnects every few minutes, you may be behind a Carrier-Grade NAT. This network setup is common with mobile hotspots, 4G/5G routers, and some residential ISPs. Carrier-Grade NAT shares a single public IP address among many users, which disrupts the direct peer-to-peer connection Discord relies on for stable voice calls. This article explains why Carrier-Grade NAT causes frequent reconnections and provides two reliable fixes you can apply today.

Why Carrier-Grade NAT Disrupts Discord Voice

Carrier-Grade NAT, also known as CGNAT or Large-Scale NAT, is a method ISPs use to conserve IPv4 addresses. Your router receives a private IP address from the ISP, and the ISP translates that private address to a shared public IP along with hundreds or thousands of other customers. This means your device does not have a unique public IP address.

Discord voice chat works best when two clients can establish a direct peer-to-peer connection using WebRTC. WebRTC negotiates a connection by exchanging IP addresses through a process called Interactive Connectivity Establishment. For a direct connection to succeed, both clients must be reachable at their public IP and port. Carrier-Grade NAT blocks incoming connection attempts because the ISP’s NAT gateway does not forward unsolicited traffic to your private IP. When WebRTC fails to establish a direct path, Discord falls back to a relay server. However, relay servers add latency and are more prone to timeout, especially under heavy load. The frequent reconnection you see is the client repeatedly trying to renegotiate a direct connection and failing, then switching back to the relay.

The problem is worse on mobile hotspots and 4G/5G routers because these networks almost always use Carrier-Grade NAT. Even on fiber or DSL connections, some ISPs apply CGNAT when you do not pay for a static public IP. The reconnection cycle typically lasts 30 seconds to 2 minutes, during which you cannot hear or speak to anyone in the channel.

Steps to Stop Discord Voice Reconnecting on Carrier-Grade NAT

You can solve this problem with two in-app settings changes. The first setting forces Discord to use its relay servers instead of attempting a direct connection. The second setting reduces packet loss that causes the relay connection to break. Apply both settings in the order shown below.

1. Open Discord User Settings
   Click the gear icon next to your username at the bottom left of the Discord window. This opens the User Settings menu.
2. Go to Voice & Video Settings
   In the left sidebar, scroll down to App Settings and click Voice & Video. This page contains all audio and network settings for voice chat.
3. Enable Use Proxy for Voice
   Scroll down to the Voice Settings section. Find the option labeled Use Proxy for Voice. Toggle the switch to the on position. This setting tells Discord to route all voice traffic through Discord’s relay servers instead of attempting a direct peer-to-peer connection. Because Carrier-Grade NAT blocks direct connections, using the proxy prevents the repeated renegotiation attempts.
4. Enable Quality of Service High Packet Priority
   In the same Voice Settings section, locate Enable Quality of Service High Packet Priority. Toggle this switch to on. This setting marks your voice packets with a higher priority in the network queue. On congested relay servers, this reduces packet loss and jitter, which are common causes of reconnections under Carrier-Grade NAT.
5. Test the Voice Connection
   Join any voice channel and speak for one minute. If the connection does not drop, the fix is working. If you still see reconnections, proceed to the next step.
6. Restart Discord Completely
   Close Discord from the system tray by right-clicking the Discord icon and selecting Quit Discord. Open Discord again and test the voice channel. A full restart ensures the new proxy setting takes effect.

Alternative Fix: Request a Public IP Address from Your ISP

If the in-app settings do not resolve the issue, the only permanent solution is to remove Carrier-Grade NAT from your connection. Contact your ISP and ask for a public IPv4 address. Many ISPs offer this as a free option or for a small monthly fee. Some ISPs also support public IPv6 addresses, which are not subject to CGNAT. Once you have a public IP, restart your router and modem. Discord voice will then be able to establish direct peer-to-peer connections without interruptions.

If Discord Voice Still Reconnects After the Main Fix

Discord Voice Reconnects on Mobile Data

Mobile networks, including 4G and 5G, almost always use Carrier-Grade NAT. The steps above apply to the Discord mobile app as well. Open the Discord app on your phone, tap your profile icon, select Voice & Video, and enable Use Proxy for Voice and Quality of Service High Packet Priority. If the problem persists, switch to a Wi-Fi network that uses a public IP, or contact your mobile carrier about a public IP option.

Reconnections Happen Only on Specific Servers

If reconnections occur only in certain Discord servers, the server may be using a voice region far from your location. Ask the server owner or admin to change the voice region to a region closer to you. Go to Server Settings > Overview > Server Region and select a region with lower ping. This reduces the distance your voice traffic must travel, which can stabilize the relay connection.

VPN or Third-Party Proxy Interference

A VPN or third-party proxy can add another NAT layer on top of Carrier-Grade NAT, making reconnections worse. Disable any VPN or proxy while using Discord voice. If you need a VPN for privacy, choose one that supports port forwarding, which can bypass some NAT restrictions. After disabling the VPN, restart Discord and test the voice channel again.

Discord Voice Connection Types: Direct vs Proxy vs Relay

Item	Direct Peer-to-Peer	Discord Proxy (Use Proxy for Voice)	Relay Server (Fallback)
Description	Clients connect directly without intermediate servers	Voice routed through Discord’s proxy servers	Voice routed through a third-party relay when proxy fails
Latency	Lowest	Moderate	Highest
Works on CGNAT	No	Yes	Yes, but unstable
Packet loss rate	Low	Low with High Packet Priority enabled	High under load
Recommended for	Users with a public IP	Users behind CGNAT	Emergency use only

Discord voice reconnections due to Carrier-Grade NAT can be fixed in minutes by enabling the proxy and high packet priority settings. If those settings do not work, requesting a public IP from your ISP is the definitive solution. Test your voice connection after each change to confirm the reconnections have stopped.