The short answer
Check whether Discord still responds and whether your call membership or connection state changed. For connection loss, inspect service incidents, then compare another channel and a DM with the same person. If every call fails, compare the browser on the same PC, then change only the network.
Different symptom or still not fixed? Find the next check →Key facts
- What stopped?
- App window, call connection or sound only
- Keep conditions comparable
- Same PC and participant; change location, client and network separately
- Test duration matters
- A short connection does not establish recovery from a later failure
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| Discord stays open, but the call disconnects or reconnects | Compare another channel and a DM for a similar duration. | Step 2 |
| The window closes or Discord restarts | Check the notification area and processes before calling it a crash. | Step 1 |
| You remain in the call, but voices break up | Confirm the connection remains active and investigate audio gaps. | Step 1 |
| DM works, but one server/channel disconnects | Ask whether other participants disconnect at the same time. | Step 2 |
| Only the desktop app fails; the same-PC browser stays connected | Restart/update the app and repeat the actual call. | Step 3 |
| Both clients fail, but another network works | Inspect the original network, VPN and restrictions. | Step 4 |
| Failure occurs only while gaming or streaming | Compare voice only, then the game, then streaming. | Step 5 |
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｜Separate connection loss, app closure and audio gaps
A vanished window does not by itself establish that Discord stopped running.
Time: Compare one change at a time
- Record the time and any RTC Connecting, No Route or other message. Ask the other participant whether you disappeared from the call or only stopped being audible.
- If the window closed, inspect the Discord icon in the notification area and Discord processes in Task Manager (Ctrl+Shift+Esc). Distinguish a background app from an exit or restart.
- For an actual app exit/restart, use the crashing guide. If membership and connection remain unchanged and only sound breaks up, use the voice-cutting-out guide.
- If Discord stays open and only the call connection drops, continue to Step 2. For reconnection stuck on RTC Connecting or No Route, consult the corresponding related guide too.
Results that did not fix the problem help the next reader too.
Step 2｜Change only the call location: channel, another channel, then DM
Keep the PC, network and willing participant the same. Compare for a meaningful duration.
Time: Compare one change at a time
- Check Discord Status for a relevant voice incident. Wait for recovery when one is reported; no announcement does not rule out a newly developing incident.
- If calls usually fail after about three minutes, a roughly five-minute conversation is one comparison example. Record the failure time. For failures after longer use, compare over a similarly relevant period instead.
- Try another permitted voice channel, then a DM call with the same person. Keep client and network settings unchanged during these comparisons.
- If only one channel fails, ask whether other participants disconnected simultaneously. Have its administrator check channel settings, permission changes and any move/disconnect actions.
- If every location including DMs fails, continue to Step 3. One failing channel alone does not establish faulty hardware or a problem across the whole network.
Results that did not fix the problem help the next reader too.
Step 3｜Compare desktop and browser on the same PC and network
Opening chat is insufficient: compare whether an actual voice call stays connected.
Time: Compare one change at a time
- Leave the desktop call, open https://discord.com/app in a browser, sign in to the same account and allow microphone access for the site.
- Join the same location with the same person and compare for the duration used in Step 2. Do not join from both clients simultaneously.
- If only the browser stays connected, fully quit the desktop app from the notification area, restart it to apply updates and repeat that call.
- If only the app still fails, inspect the high-priority QoS packet setting under Voice & Video → Voice. If enabled, record the value, disable it and reconnect for comparison; restore it if unhelpful.
- If both fail, continue to Step 4. If only the browser fails, update it and compare another supported browser. Missing microphone permission that prevents the call means this comparison is incomplete.
Results that did not fix the problem help the next reader too.
Step 4｜Compare another network, then inspect the original connection
A speed-test number alone does not show whether voice calls remain connected.
Time: Compare one change at a time
- Pause downloads or cloud synchronization one at a time and compare the same call’s disconnect frequency.
- For Wi-Fi, compare Ethernet. If available, separately compare another internet connection, such as your own phone hotspot, on the same PC and client; account for mobile data limits.
- Ethernet alone working points toward Wi-Fi conditions; another internet connection alone working prioritizes the original connection/router/restrictions. Record these as separate comparisons.
- If using a VPN you control, compare with it disconnected when permitted. Discord documents UDP support as a requirement for voice through a VPN. Ask the administrator about work/school network restrictions.
- If failure remains specific to the original network, restart its router using the manufacturer’s procedure and inspect Discord-specific security software permissions. If another network also fails, continue to Step 5.
A router restart interrupts other users. Do not press its factory-reset button, bypass managed network rules or leave the entire firewall disabled.
Results that did not fix the problem help the next reader too.
Step 5｜For gaming or streaming failures, compare load and the actual symptom
High CPU use alone does not establish the cause, and broken audio can be mistaken for disconnection.
Time: Compare one change at a time
- With the same participant and network, compare voice only with game/streaming stopped, then add the game, then start streaming. Record connection state at each failure.
- Open Task Manager with Ctrl+Shift+Esc. Inspect CPU, memory and GPU under Performance when the symptom occurs; use Processes to identify recording or unnecessary apps adding load.
- Stop one optional task such as recording and repeat the same conditions. Check whether disconnects also decrease; if not, do not attribute the problem to load alone.
- If connected but Push to Talk stops responding, inspect its binding and the game/app permission difference. For an app exit use the crashing guide; for voice gaps use the audio-cutting-out guide.
Results that did not fix the problem help the next reader too.
Avoid
- Do not treat browser chat loading or a brief successful call as proof that voice connectivity is healthy.
- Do not reset the router, disable all protection or change client, network and channel together.
Important cautions
- For help, record failure time and time to recurrence, whether the app remained open, location/client/network comparisons, VPN use, gaming/streaming and exact messages.
- For one channel, contact its administrator; for one network, contact its operator/router support; for failures across tested conditions, contact Discord support. Mark unavailable comparisons as untested.
FAQ
Why do calls disconnect when my speed test is fast?
Throughput does not establish freedom from brief outages or connection restrictions. Compare Ethernet and another network separately on the same PC and observe actual call failures.
Does working browser chat prove the network is fine?
No. Compare a voice call with the same participant for a relevant duration. Chat access and sustained voice are different observations.
Should I reinstall when only one server fails?
First compare another channel and a DM. Ask the administrator about settings, permissions and disconnect actions when failure is confined to a location.
Is losing only voices while gaming necessarily a network issue?
No. If call membership remains, inspect input, sensitivity, Push to Talk and PC load using the voice-cutting-out guide rather than treating it as confirmed connection loss.
Sources
English adaptation of the existing Japanese guide using the same steps and official sources. Comparison sequences and example outcomes are editorial guidance, not measured results. Record original settings, change one condition at a time and distinguish an incomplete comparison from a successful result.
Discord: voice and video troubleshootingDiscord Status: service incidentsDiscord: voice connection errors, VPN and network checksDiscordJapanese version of this page