Skip to main content

Perform an MTR diagnostic

What is MTR?​

MTR (My TraceRoute) is a network diagnostic tool that combines the features of ping and traceroute. It allows you to analyze in real-time the quality and performance of the connection between your computer and a remote server by monitoring each network "hop".

Why perform an MTR test?​

An MTR test is particularly useful for:

  • Identifying connection issues (latency, packet loss)
  • Precisely locating network congestion points
  • Analyzing routing performance and network stability
  • Verifying end-to-end service quality
  • Diagnosing intermittent connectivity problems

How to perform an MTR test?​

On Windows​

  1. Download WinMTR from the official website
  2. Install the software (no special configuration required)
  3. Launch WinMTR as administrator
  4. Enter the server's IP or domain name in the "Host" field
  5. Click "Start" and let it run for at least 15 minutes
  6. To save: "Export TEXT" or screenshot

On Linux​

Install MTR via your package manager:

# Debian/Ubuntu
sudo apt update && sudo apt install mtr

# CentOS/RHEL
sudo yum install mtr

# Fedora
sudo dnf install mtr

Run the command in text mode:

mtr -r -c 100 <server_IP> > mtr_report.txt

Or in interactive mode:

mtr <server_IP>

On macOS​

Install MTR via Homebrew:

brew install mtr

Launch MTR (requires root privileges):

sudo mtr <server_IP>

Best practices​

  • Test duration: Minimum 15 minutes, ideally 30 minutes for intermittent issues
  • Bidirectional tests:
    • Always perform tests in both directions (outbound and return)
    • From your machine to the remote server
    • From the remote server to your machine
    • Compare results to identify routing asymmetries
  • Test timing:
    • Perform the test during problematic periods
    • Run a reference test during a normal period
  • Documentation:
    • Note the exact date and time of the test
    • Document if the problem occurred during the test
    • Keep complete results (do not truncate)
  • Environment:
    • Avoid Wi-Fi if possible, prefer a wired connection
    • Close bandwidth-intensive applications
    • The test can run in the background while you work

Interpreting results​

Signs of potential problems:​

  • Packet loss > 1% on multiple hops
  • Latency that increases sharply between two hops
  • High standard deviation (StDev) indicating instability
  • Repeated timeouts (*) on certain hops
  • Significant asymmetry between outbound and return tests
  • Different routes between outbound and return

Normal results:​

  • Gradual slight increase in latency
  • Packet loss < 1%
  • Stable and low standard deviation
  • No sharp variation between hops

Important points to remember​

  • MTR is an essential tool for network diagnostics
  • Results allow precise localization of problems
  • A complete test includes periods with and without problems
  • Impact on your connection is minimal
  • If in doubt, don't hesitate to perform multiple tests

Support​

Contact our support team by attaching:

  • Complete MTR test results
  • Description of the problem encountered
  • Test dates and times