Error messageNo Route and RTC Connecting mean Discord is not completing the voice connection. Working text chat does not establish that the voice path is allowed. Separate service, channel, client and network before changing microphones or resetting settings. Waiting for Voice Server calls for checking the service first.

Discord shows No Route or RTC Connecting

No Route

Separate a failure to reach voice servers from a microphone or audio-output problem.

Try this first

1 quick checks · ~3 min

  1. Check service and scopeDistinguish a service outage and the scope of failure.

Find your situation

See all the clues. Choose the one that matches what you observe.

Diagnostic signals

ObservationConfirmed voice incident
Wait for recovery: reinstalling cannot change service status.
ObservationText available, voice not connected
Web access does not rule out UDP restrictions or voice routing problems.

Step-by-step solutions

01

Check service and scope

Distinguish a service outage and the scope of failure.

  1. Record the literal state and check discordstatus.com. If a matching voice incident is reported, stop local tests until recovery. Normal status does not rule out a regional or newly starting failure.

  2. Try another permitted channel once. If it connects, follow the channel branch; if none connect, compare client and network. If connected but you cannot hear or be heard, use the related audio guide.

02

When other channels connect

  1. Compare in the same client and network so only the channel changes. If failure stays limited to one, ask its administrator to review that channel and whether others are affected. Do not reset the PC’s network based on that result.

  2. If you administer the channel, notify connected users and record Voice Channel Settings > Overview > Region Override. Temporarily try another region. Restore the value if unchanged; if improved, report the scope and region without assuming a permanent repair.

03

Compare browser and app

  1. Open official Discord in a supported browser and test the same channel, account and network. Allow microphone access only for Discord if prompted. Assess whether it connects, not merely whether the page loads or sound plays.

  2. If the browser connects but the app does not, the client or its local rules become more relevant: quit and reopen the app once and have its specific security allowance reviewed. Do not disable protection. If both fail, continue with the network comparison; if the app recovers, stop without deleting data.

04

Compare a permitted network

  1. If policy permits, test the same client and channel on another personal or authorized connection; mobile service may use paid data. If it works there, investigate the original network with its administrator or provider rather than reinstalling Discord. If it fails there too, keep both results for support.

  2. If using a VPN, check whether it supports UDP. Only temporarily disconnect a personal VPN when permitted and appropriate for that connection; restore it afterward. If the result changes, consult the VPN provider. A proxy or business network may impose restrictions: request authorization rather than bypassing them.

  3. If policy blocks voice, stop and consult IT. Without a known restriction, provide network, client, channels and failure time. Do not randomly change DNS, open arbitrary ports or turn off firewall or router security.

Next step

Still not working?

If service, channel, client and network comparisons do not isolate failure, send them privately to Discord with the literal state. Do not repeat restarts without a new hypothesis. Review personal details before sharing any logs requested by support.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems