Discover how to diagnose network problems by analyzing outbound and return paths to improve connection stability and performance → Learn more now
12 November 202614 min read32 Views0 helpful
Introduction
Network issues can be really frustrating and are definitely not part of everyday life. But when they occur, it's important to quickly and effectively find the cause to resolve the problem. You can analyze detailed information about network problems very well with the WinMTR (Windows) or MTR (Linux/Mac OS) app.
WinMTR/MTR is a network diagnostic tool that combines the functions of Ping and Traceroute. It allows you to analyze both the outbound path (Client → Server) and the return path (Server → Client) precisely by tracking the route of data packets in both directions. Important information such as latency and packet loss is recorded, which is crucial for accurately identifying and resolving network issues.
Outbound path (Client → Server): A report for the outbound path is helpful when problems like connection drops, slow connections, or difficulties establishing a connection occur. This analysis helps identify possible issues on the way from the client to the server, such as network congestion, packet loss, or faulty routes.
Return path (Server → Client): A report for the return path only makes sense if a stable and functioning connection on the outbound path has been confirmed. The return path report is especially relevant when the outbound path shows no problems but issues like slow server responses, delayed loading times, or incomplete data transfers still occur.
In short: If you notice network problems, you should first analyze the outbound path (Client → Server). If the outbound report shows no anomalies and the problems persist, check the return path (Server → Client) to find possible asymmetric issues. Asymmetric network problems occur when data packets flow smoothly in one direction but experience delays or packet loss in the opposite direction.
Installation
Now that it's clear when reports for inbound and outbound paths are useful, let's continue with the installation on both client and server sides.
Client
For the outbound path, the app must be installed on the client (your computer). The following steps show you how to install the app for your operating system.
If you use a Windows computer, the network analysis runs via the WinMTR app. To install WinMTR on your computer, first download the app from the ZAP-Hosting website. After downloading, extract the file. You will then get the executable file WinMTR.exe.
On a Linux computer, the network analysis runs via the MTR app. To install MTR, open the terminal and execute the appropriate installation command for your system:
On a Mac OS computer, network analysis also runs via MTR. However, MTR is not pre-installed and not available in the Apple Store. You must first install Homebrew as a package manager.
Install Homebrew
Open the terminal and run the following command to install Homebrew:
Connect to your server via Remote Desktop Connection. To install WinMTR, first download the app from the ZAP-Hosting website. After downloading, extract the file. You will then get the executable file WinMTR.exe.
It is a network diagnostic tool that combines the functions of Ping and Traceroute. It analyzes both the outbound path (client to server) and the return path (server to client), recording latency and packet loss to detect network issues.
Start with the outbound path (client to server). If this shows no anomalies and problems persist, then check the return path (server to client) to find possible asymmetric issues.
On Windows, use the WinMTR app (download from the ZAP-Hosting website). On Linux, use MTR, installable via commands like 'apt install mtr -y' (Debian/Ubuntu). On Mac, MTR is not pre-installed and must be installed via Homebrew.
Feedback
Was this article helpful?
Your feedback helps us prioritize and improve content.
0 of 0 Users found this article helpful.
Personal support
Need more help than the guide provides?
Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.
Zappy knows this guide and answers you right in the chat.
You decide which services we may enable for analytics, personalization, and external content.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
AnalyticsMarketingPersonalizationExternal media
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.3
Navigation
VPS
Reporting Issues
Even though ZAP-Hosting constantly monitors the network, it is important to quickly contact our support in case of network problems. To help us diagnose the problem accurately and resolve it quickly, please send us the results of your WinMTR/MTR reports for both outbound and return paths. This way, we can precisely identify possible problem areas and assist you promptly.
Server hosting from €2.49 / month, online instantly, DDoS protection included.
The following shows how to create a report with WinMTR/MTR – both for the outbound path (Client → Server) and the return path (Server → Client).
Warning
Create report during active issues
The report should be created while the problem is active and noticeable. Only then does the report provide useful information that helps with troubleshooting.
Outbound path (Client → Server)
To analyze the path from your computer to the server, open the WinMTR/MTR app on your computer and follow the steps below.
Start the WinMTR app by double-clicking the file WinMTR.exe. Enter the IP address or hostname of the server in the Host field. Then start the report. Let the app run for at least one minute to collect enough data. When you have enough data, stop the analysis and save the result via Export TEXT.
Open the terminal and start MTR with the following command:
Code
mtr <your server ip address>
Let the app run for at least one minute to collect enough data. Then stop the analysis and save the result.
Return path (Server → Client)
To analyze the path from the server to your computer, connect to your server and follow the steps below.
Start MTR on your server in the SSH terminal with the following command:
Code
mtr <your client ip address>
Let the app run for at least one minute to collect enough data. Then stop the analysis and save the result.
Info
Don't know your IP address or how to find it? There are various methods to determine your IP address. The quickest way is via online services like WhatIsMyIPAddress.
Enter your connection's IP address in the Host field. Then start the report. Again, let the app run for at least one minute to collect enough data. Then stop the analysis and save the result via .
Evaluating the Report
When evaluating, there are some important points to watch out for. Below we explain these in more detail and show why they are important for the analysis. If you pay attention to these aspects, you can better identify and narrow down the cause of the problem.
Packet Loss
If you see packet loss in the results, this indicates possible network problems. A small, temporary packet loss of 1-2% is usually uncritical; higher values indicate more serious issues. Packet loss can cause delays or connection drops. If the loss is evenly distributed across all hops, the problem is likely in your own network or on the server side. If the loss occurs only at a specific hop or area, the problem is likely at that node or the connection to the next. Important: Small losses at the first hops belonging to your local network are not necessarily critical, as these devices often prioritize ICMP requests (like Ping) lower and sometimes discard them.
Latency (Ping Times)
Latency values (Avg, Best, Worst) give you insight into the speed and stability of the connection. If you see that latency at a specific hop is consistently high, this can indicate network congestion or a slow router. A sudden increase in latency between two hops points to a possible bottleneck. Normally, latency increases gradually on the way to the destination. However, watch out for sudden, sharp spikes, which often signal a problem. Comparing outbound and return paths also helps detect asymmetric issues – i.e., when traffic in one direction has problems.
With a detailed analysis of these factors, you can well determine where the network problem lies – whether in your own network, with the internet provider, or somewhere on the way to the server.
Diagnostic Examples
To better understand this, we show you some diagnostic examples. We have compiled various scenarios that illustrate different situations and possible causes. This way, you learn to interpret the data better and diagnose network problems more effectively.
Info
The following diagnostic examples are based on fictional WinMTR/MTR reports. The IP addresses, hostnames, and routes are completely made up and have no relation to real networks or hosts.
Example: Packet Loss on Client Side
Export TEXT
Info
Don't know your IP address or how to find it? There are various methods to determine your IP address. The quickest way is via online services like WhatIsMyIPAddress.
Description
Here, packet loss occurs on the client side, visible on both outbound and return paths.
The evaluation shows packet loss on the client side. Both paths show losses at the first hops (Hop 1 and 2), indicating a problem in the local network or router of the client.
Example: Packet Loss on Server Side
Description
Here, packet loss occurs on the server side, visible on both outbound and return paths.
The evaluation shows high latency on the client side. Both paths show increased latency at the first hops (Hop 1 and 2), indicating a problem at the client.
Example: Latency Issues on Server Side
Description
Here, there are high latency times on the server side, visible on both outbound and return paths.
The evaluation shows high latency on the server side. Both paths show increased latency at the last hops (Hop 7 and 8), indicating a problem at the server.
Example: Routing Problem (ISP Routing)
Description
Here, the route from Client X to the server works without problems, while Client Y has routing problems with packet loss to the server. This indicates an issue with the internet service provider (ISP).
The evaluation shows a routing problem at the ISP. While the route from Client X is stable, Client Y has significant issues with packet loss and high latency.
Example: Packet Loss Only on Outbound Path (Client → Server)
Description
Here, packet loss occurs only on the outbound path (from client to server), while the return path (from server to client) is loss-free. This can indicate a problem in a network segment towards the server, e.g., due to faulty routers, congestion, or poor connection.
The evaluation shows packet loss only on the outbound path. The losses are visible at hops 4, 5, and 6, indicating a problem on the way from client to server, e.g., congestion or faulty network devices. The return path has no losses; the connection in the other direction is stable.
Example: Packet Loss Only on Return Path (Server → Client)
Description
Here, packet loss occurs only on the return path (from server to client), while the outbound path (from client to server) is loss-free. This can indicate a problem in a network segment on the return path.
The evaluation shows packet loss only on the return path. The losses are visible at hops 4, 5, and 6 of the return path, indicating a problem on the way from server to client.