Join our Discord and be part of our community!
Test Latency and Packet Loss (MTR)
This guide demonstrates how to perform a ping test using WinMTR. It is a free network diagnostic tool that combines the functionality of the traceroute and ping utilities into a single tool. We will also explain the significance of the results and how to interpret them. To perform the steps in this guide, you will need to extract a zip archive with WinRaR.
Understand Latency, Routing, and Packet Loss
Before diving into the tool, it is important to understand what latency and packet loss are, and why your connection to a game server might feel slow or unstable, even if the server itself is fine.
Latency (often called ping) is the time it takes for a data packet to travel from your computer to the server and back, measured in milliseconds (ms). The lower the latency, the faster your connection feels.
Latency depends on many factors:
- Distance: The farther you are from the server’s physical location, the longer it takes for data to travel.
- Routing: Data does not take a straight line between you and the server. It passes through multiple routers (called hops), each adding a bit of delay.
- Congestion: If one of these hops is overloaded or misconfigured, it can cause spikes in latency or even packet loss.
Packet loss happens when some of the data packets never make it to their destination. Even a small percentage of packet loss can cause lag, rubberbanding, or disconnects.
Note that not all network problems originate from the server. In most cases, routing issues occur somewhere between your ISP (Internet Service Provider) and the network carriers they use to reach our data centers.
These middle connections are outside of our direct control, meaning bad routing or high latency in one of those hops usually means your ISP chose a less direct or slower route for your connection to reach the server.
In short:
- High ping = long distance, poor routing, or network congestion.
- Packet loss = data is not reaching the server properly.
- Sudden spikes or jumps in latency often come from temporary congestion on an ISP or transit provider’s side.
That’s where a tool like WinMTR helps: it shows you exactly where along the route these issues occur.
Download WinMTR
- You can download WinMTR from its official GitHub page.
- The file to download is 1 winMRT-v100.zip.
Extract the ZIP File
- Next, you need to extract the downloaded ZIP archive.
- This can most often be done with the Windows Explorer, but can also be done with WinRaR.
- After you have installed WinRaR, right-click the ZIP file to reveal the context menu, and click Extract Here.
- A handful of files will be extracted. To access WinMTR, double click 1
WinMTR64.exe.
- You will see a simple interface where you can enter the host (IP address) you want to ping and traceroute.
Start MTR Test
- In the 1 Host field, input your server IP address or domain that you want to test.
- For example:
12.345.678.90orgoogle.com. - Press the 2 Start button.
- The program will start testing and save the data. Leave it running for 5–10 minutes for best results.
Interpret the Results
- After running the test for a few minutes (preferably 5–10 minutes), you will see various columns filled with data.
- Press the 1 Stop button
- 2 You can now see the test results.
- Here is a description of what each column signifies:
- Hostname: The router’s name or IP address at that hop.
- Number (Nr): The hop count.
- Loss %: The percentage of lost packets.
- Sent: The number of sent packets.
- Recv: The number of received packets.
- Best: The shortest time (in ms) data packets travel from your computer to the host.
- Avrg: The average time (in ms) data packets take to travel from your computer to the host.
- Worst: The longest time (in ms) data packets travel from your computer to the host.
- Last: The last round trip time for that hop.
- Press any of the 3 Export TEXT/HTML buttons to export the data.
- Send the exported data to the support team for further analysis.
Troubleshooting WinMTR
If you encounter issues while running the program, such as it showing a missing runtime or DLL error, please install Microsoft Visual C++ 2010 SP1 Redistributable from the following link:
- This runtime is required because WinMTR depends on Visual C++ libraries that may not be present on all systems.
- After the installation completes, relaunch WinMTR to verify that the issue is resolved.
Run a Traceroute
A traceroute maps the path your data takes from your computer to the destination server, showing every router (hop) along the way. It helps identify where delays or packet loss are occurring in the network path. Unlike WinMTR, a traceroute is a quick, one-time snapshot rather than a continuous test.
When to Use Traceroute
Our support team may ask you to run a traceroute when:
- You are experiencing high latency or connection issues.
- WinMTR is not available on your system.
- A quick network path snapshot is needed to diagnose routing problems.
Run Traceroute on Windows
- Press
Windows + R, typecmd, and press Enter to open the Command Prompt. - Type the following command, replacing the IP with your actual server IP address:
tracert YOUR_SERVER_IP- Example:
tracert 79.127.235.185 - The traceroute will begin. Each line represents one hop along the network path.
- Wait until you see Trace complete. before copying the results, this confirms all hops have been recorded.
- Select all the output, copy it, and paste it into your support ticket.
Run Traceroute on macOS/Linux
- Open the Terminal application.
- Type the following command:
traceroute YOUR_SERVER_IP- Example:
traceroute 79.127.235.185 - Wait for it to finish, then copy the full output into your support ticket.
Interpret the Results
Each row in the traceroute output represents a single hop:
- Hop number: The step count from your computer to the server.
- Hostname / IP: The router handling traffic at that hop.
- Round-trip times (ms): Three time measurements are shown per hop. High values at a specific hop indicate latency at that point in the path.
* * *(asterisks): The router at that hop did not respond. This is common and does not always indicate a problem. Many routers block traceroute probes by default. Only be concerned if asterisks appear at the final hop (the server itself).
If you require further assistance, you can open a support ticket here.
Feedback and suggestions can be submitted here or further discussed on our Discord server.