If your Discord voice calls keep dropping, audio cuts out, or messages fail to send, you may have an unstable network connection. Discord includes a built-in connection stability test that records detailed logs. These logs show packet loss, latency spikes, and jitter values that help pinpoint the cause of poor performance. This article explains how to run the test and interpret the log data to identify connection problems.
Key Takeaways: Running a Discord Connection Stability Test
- User Settings > Voice & Video > Run Connection Test: Starts a 4-second test that measures packet loss, jitter, and latency.
- Ctrl + Shift + I (Windows) or Cmd + Option + I (Mac): Opens Discord Developer Tools to view network logs.
- Network tab in Developer Tools: Captures WebSocket and RTC connection events that show disconnections and reconnections.
How Discord Connection Stability Testing Works
Discord uses a Real-Time Communication protocol to transmit voice and video data between users. The connection stability test checks three key metrics: packet loss, jitter, and latency. Packet loss is the percentage of data packets that never reach the destination. Jitter measures the variation in packet arrival time. Latency is the delay between sending and receiving data. High values in any of these metrics cause choppy audio, dropped calls, and slow message delivery.
The test runs for exactly 4 seconds. During that time, Discord sends test packets to its servers and records the results. The log data is stored in the Developer Tools console and network tabs. You must enable Developer Mode in Discord before the test captures all details.
Prerequisites for the Test
Before running the test, ensure you have the following:
- A stable internet connection with at least 1 Mbps download speed
- Discord desktop app version 1.0.9000 or later
- Developer Mode enabled in User Settings > Advanced > Developer Mode
- Administrator permissions on your computer to access network logs
Steps to Run the Connection Stability Test and Capture Logs
Follow these steps to run the test and save the log data for analysis.
- Open Discord and Navigate to Voice & Video Settings
Launch the Discord desktop app. Click the gear icon in the bottom-left corner to open User Settings. Select Voice & Video from the left sidebar. - Enable Developer Mode if Not Already Active
In User Settings, go to Advanced in the left sidebar. Toggle Developer Mode to the ON position. This enables detailed logging in the Developer Tools. - Open Developer Tools
Press Ctrl + Shift + I on Windows or Cmd + Option + I on Mac. The Developer Tools panel opens on the right side of the Discord window. Click the Console tab to view log messages. - Run the Connection Stability Test
Return to Voice & Video settings. Scroll down to the Voice Settings section. Click the Run Connection Test button. The test runs for 4 seconds. Watch the Console tab for real-time log entries showing packet loss and jitter values. - View Network Logs
In Developer Tools, click the Network tab. You see a list of all network requests Discord makes during the test. Look for entries labeled “voice” or “rtc” in the Name column. Click any entry to see detailed timing and status information. - Save the Log Data
In the Console tab, right-click anywhere in the log area and select Save as… Choose a location on your computer and save the file as a .log file. In the Network tab, click the Export HAR button (looks like a download arrow) to save all network data as a .har file.
Interpreting the Test Results
After saving the logs, open the .log file in any text editor. Look for lines containing the following keywords:
- packetLoss: A value above 5% indicates significant packet loss that affects voice quality.
- jitter: Values above 30 ms cause audio distortion and echo.
- latency: Values above 150 ms introduce noticeable delay in conversations.
- disconnect: Multiple disconnect entries in a short period indicate an unstable network.
The .har file contains request and response headers for each WebSocket connection. Look for HTTP status codes 403 or 503, which indicate server-side issues. Repeated requests to the region endpoint suggest Discord is switching server regions due to instability.
Common Issues After Running the Test
Test Shows 0% Packet Loss but Voice Still Drops
The connection test measures only the link between your computer and Discord servers. It does not test the full path from your computer to other users. Voice drops after the test may be caused by your router, ISP throttling, or interference from other devices on your network. Run a continuous ping to a stable server like 8.8.8.8 to check for intermittent drops.
Log File Contains No Data
If the Console tab shows no entries during the test, Developer Mode may not be enabled. Return to User Settings > Advanced and confirm Developer Mode is ON. Also ensure you clicked the Console tab before running the test. If the issue persists, restart Discord and try again.
Network Tab Shows No RTC Entries
The Network tab only captures requests made while it is open. Close and reopen Developer Tools, then run the test again. If still no entries appear, your Discord version may be outdated. Update to the latest version by clicking the Download button on the Discord website.
Discord Connection Test: Built-in Test vs Third-Party Tools
| Item | Discord Built-in Test | Third-Party Tools |
|---|---|---|
| Duration | 4 seconds | Continuous or user-defined |
| Metrics measured | Packet loss, jitter, latency | Packet loss, jitter, latency, throughput, DNS resolution |
| Log export format | .log and .har files | Varies by tool (CSV, JSON, PNG) |
| Network path tested | Computer to Discord server | Computer to any target server |
| Requires Developer Mode | Yes | No |
The built-in test is quick and directly tied to Discord’s infrastructure. Third-party tools like PingPlotter or WinMTR provide longer tests and show the entire network path, including router hops. Use the built-in test for a fast check. Use third-party tools when you need detailed routing information or when the built-in test shows no issues but problems persist.
After running the test and analyzing logs, you now have concrete data to share with your ISP or network administrator. The packet loss and jitter values from the .log file give them a clear target to investigate. For ongoing monitoring, run the test weekly and save the logs in a dated folder. If you see a trend of increasing packet loss over time, your router hardware may need replacement or your ISP may be degrading service during peak hours.