English
日本語English简体中文暂无翻译，前往中文首页EspañolSin traducción: ir al inicio en español

If this page is not translated, the link opens that language’s home page.

Discord

Discord No Route: Compare the Device, Network and Voice Channel

For Discord voice calls that display No Route on Windows desktop or browser. Working websites or text chat do not prove the voice connection works.

Edited by Gemnao Editorial Team (Japanese)Last checked 2026-10-18
Saved articles →
No account needed. Saved only in this browser.

The short answer

Record the error/time and inspect incidents, then compare another channel or DM. If available, compare another device on the same Wi-Fi and the same PC on another network. Use those results to choose network, PC or channel checks; avoid indiscriminate DNS changes, router resets and firewall shutdowns.

Different symptom or still not fixed? Find the next check →

Key facts

Compare real calls
Text chat working is not a successful voice test
Change one condition
Same destination; separate device and network comparisons
Unperformed stays unknown
Use available comparisons without buying another device or connection

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
PC and phone fail on one Wi-Fi; another network worksPrioritize the original connection/router/VPN path.Step 2
Phone works on the same Wi-Fi; only the PC failsInspect PC VPN, app permissions and desktop/browser difference.Step 3
The same PC succeeds only with its VPN disconnectedAsk the VPN provider about UDP support and configuration.Step 2
One channel fails, but another channel or DM worksCompare its region with the administrator and preserve the original.Step 4
Several people fail together or another network also failsInspect incidents and other destinations; retain the comparison results.Step 1
Browser voice works, but the app alone shows No RouteInspect updates and voice settings before reinstalling.Step 3

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1｜Use incident checks and comparisons to narrow the scope

Web access is not equivalent to a working voice session.

Time: Compare one change at a time

  1. Record No Route and its time. Inspect Discord Status and your provider’s incident information. For a relevant outage, repeat the same call after recovery.
  2. Leave/rejoin once. If it continues, use the same PC/network to try another permitted channel or a DM with a willing person. For only one failing destination, continue to Step 4.
  3. If available, try that same destination on a phone using the same Wi-Fi. Confirm it has not switched to mobile data and record its actual network.
  4. Next, compare the same PC on another permitted connection such as your own hotspot. Keep the call brief, account for data limits and restore the original network afterward.
  5. Example record: PC/home Wi-Fi fails, phone/home Wi-Fi fails, PC/hotspot works. This prioritizes the home path but does not itself establish a faulty router or blocked UDP.

If another device/network is unavailable, record it as untested. Continue with available comparisons such as another channel or the same-PC browser.

Results that did not fix the problem help the next reader too.

Step 2｜For one failing network, inspect VPN and router conditions

Discord documents UDP support for voice through a VPN; compare VPN state separately from network changes.

Time: Compare one change at a time

  1. For a VPN you control, compare it disconnected when permitted. If that helps, consult the provider about UDP/configuration. Ask the administrator about a required work/school VPN.
  2. If home internet alone fails even without the VPN, check whether others are using it before restarting the modem/router according to its manufacturer.
  3. After connection recovery, restart the PC and test a short conversation with the same account/channel. Do not press the router’s factory-reset button.
  4. If unchanged, send the ISP/router provider the time and comparisons, such as multiple devices failing on one Wi-Fi but another connection working. Do not guess port numbers to open.

Another network working narrows the path; it does not identify the router as faulty. Respect shared users and managed network rules.

Results that did not fix the problem help the next reader too.

Step 3｜For PC-only failure, compare clients and targeted permissions

Inspect evidence before disabling protection broadly.

Time: Compare one change at a time

  1. Fully quit Discord through the notification area, restart to apply updates and, if needed, restart the PC before repeating the same call.
  2. End the app call, open https://discord.com/app on the same PC and join the same destination. Allow microphone access and verify actual conversation, not just the page loading.
  3. If app and browser both fail, inspect PC VPN use and security software block history. Match event time and the actual Discord executable before drawing a conclusion.
  4. For Windows app permissions, inspect Windows Security → Firewall & network protection → Allow an app through firewall, including Discord and the active network type. Have the administrator handle managed PCs.
  5. If the high-priority QoS setting is enabled under Voice & Video, record it, disable it and compare the same call. Skip an absent control and restore it if unhelpful.
  6. If only the browser keeps succeeding, use the RTC Connecting guide’s app checks. Before any later reinstall, confirm email/password and MFA access so you can sign back in.

Appearing in an allowlist does not prove every connection is permitted. Confirm only required changes with the administrator/provider instead of stopping the entire firewall or allowing all networks.

Results that did not fix the problem help the next reader too.

Step 4｜For a single channel, compare its voice region with the admin

A region change affects participants too; coordinate the comparison.

Time: Compare one change at a time

  1. Record that another channel/DM works and whether other participants also fail in the affected channel.
  2. With management permission, open the voice channel’s Edit Channel → Overview → Region Override. Record Automatic or the existing region.
  3. Temporarily select an available alternative and rejoin with the same people/network. If you lack permission, ask the administrator to perform the comparison.
  4. If unchanged, restore Automatic/the original region. If improved, share the successful region and results with the administrator before choosing the ongoing setting.

Results that did not fix the problem help the next reader too.

Step 5｜Organize evidence before DNS changes or a network reset

No Route alone does not establish a DNS problem.

Time: Compare one change at a time

  1. Separate a voice-only failure from websites also failing to resolve or load. If browsing fails too, consult the provider’s connection guidance.
  2. Do not apply DNS-cache clearing, DNS-server replacement or network reset as mandatory repairs for every voice-only No Route error.
  3. If an administrator/provider’s diagnosis calls for a change, record automatic configuration or original values first. Repeat the same call afterward and restore unhelpful changes as instructed.
  4. If No Route disappears but audio is missing, switch to the cannot-hear or microphone guide. A connected call and working audio are different results.

Results that did not fix the problem help the next reader too.

Avoid

  • Do not infer router damage, blocked UDP or DNS failure from the error label alone.
  • Do not factory-reset the router, guess firewall ports or leave protection disabled.

Important cautions

  • For support, record time, desktop/browser results, another same-Wi-Fi device, the same PC on another network, channel/DM differences, VPN and settings restored/retained.
  • For network-specific failures contact the network operator; for app-only failures contact Discord. Its official guide includes PTB/Canary log collection when needed: follow that procedure, keep logs private and submit only to official support.

FAQ

Does No Route mean my router is broken?

No. Compare another device on the same network and the same PC on another network before narrowing the investigation.

Why does text chat work while voice fails?

They are different connection checks. Inspect VPN UDP support and PC permissions according to the actual comparison results.

Will clearing DNS always fix it?

No Route does not itself prove DNS failure. Compare device, network and destination first; use provider guidance if evidence points to name-resolution trouble.

Do RTC Connecting and No Route have different causes?

Discord groups both as voice-connection errors. Use comparable device/network/destination results instead of diagnosing solely from the label; the RTC guide adds app-side checks.

Sources

English adaptation of the existing Japanese guide using corresponding steps and verified official documentation. Comparison examples are editorial guidance, not measured outcomes. Preserve access and original settings; distinguish an unavailable test from a successful result.

Discord: voice connection errors, VPN and regionsDiscord: voice and video troubleshootingDiscord Status: service incidentsDiscordJapanese version of this page