> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Run MTR and Traceroute on Linux and Windows

> How to run MTR and traceroute on Linux and Windows: install the tool, run mtr -rwc 100 or tracert to your server, and use TCP mode when ICMP is blocked.

To run MTR on Linux, install it (`sudo apt install mtr-tiny` on Ubuntu/Debian, `sudo dnf install mtr` on AlmaLinux/Rocky) and run `mtr -rwc 100 203.0.113.10` for a 100-cycle report. For a single trace use `traceroute 203.0.113.10`. On Windows, use the built-in `tracert 203.0.113.10` or `pathping 203.0.113.10`, or WinMTR for an MTR-style report.

| Difficulty | Time | Works on | Needs |
| - | - | - | - |
| Beginner | 5 minutes | Ubuntu 22.04/24.04, Debian 12/13, AlmaLinux/Rocky 9/10, Windows Server 2019/2022/2025, Windows 10/11, macOS | The destination IP or hostname |

## Before you start

* A **hop** is one router on the way between two computers. Traceroute lists each hop; MTR keeps probing every hop and adds loss and latency statistics.
* Commands below use `sudo` for a non-root user. If you are logged in as root, leave it out.
* To find what the numbers mean and where a problem sits, see [network latency troubleshooting](https://help.freakhosting.com/portals/other/how-to-diagnose-network-latency-issues.md).

## How to install MTR and traceroute

> [tab] Ubuntu / Debian
>
> ```bash theme={null}
> sudo apt update
> sudo apt install mtr-tiny traceroute
> ```
>
> `mtr-tiny` is MTR without the graphical interface, which is what you want on a server.

> [tab] AlmaLinux / Rocky
>
> ```bash theme={null}
> sudo dnf install mtr traceroute
> ```

> [tab] Windows
>
> `tracert` and `pathping` are built in. For an MTR-style report, download WinMTR from [winmtr.net](https://winmtr.net/); it runs without installing.

## How to run an MTR report

**1. Run the report**

```bash theme={null}
mtr -rwc 100 203.0.113.10
```

This sends 100 cycles (about 100 seconds at the default one-second interval), then prints the report and exits.

**2. Save it to a file**

```bash theme={null}
mtr -rwc 100 203.0.113.10 > mtr-report.txt
```

**3. Check the output**

```text theme={null}
Start: 2026-11-04T13:27:03+0000
HOST: web01                   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 203.0.113.1            0.0%   100    0.4   0.5   0.3   1.9   0.2
  2.|-- 198.51.100.1           0.0%   100    1.1   1.3   0.9   6.0   0.6
  3.|-- 203.0.113.10           0.0%   100    9.8  10.1   9.5  14.2   0.7
```

The last line is the destination. Loss on the last line is what affects real traffic.

### Useful MTR options

| Option | What it does |
| - | - |
| `-r` | Report mode: run, print statistics, exit |
| `-w` | Wide report, doesn't cut hostnames |
| `-c 100` | Number of cycles to send |
| `-n` | Show IP addresses only, no name lookups |
| `-b` | Show both hostnames and IP addresses |
| `-z` | Show the AS (network operator) number of each hop |
| `-4` / `-6` | Force IPv4 or IPv6 |
| `-T -P 443` | Use TCP SYN to port 443 instead of ICMP |
| `-u` | Use UDP instead of ICMP |

Use TCP mode when a firewall on the path drops ICMP, or to test the same port your service uses:

```bash theme={null}
mtr -rwc 100 -T -P 443 203.0.113.10
```

## How to run traceroute on Linux

```bash theme={null}
traceroute 203.0.113.10
```

By default `traceroute` sends 3 UDP probes per hop and stops after 30 hops. Useful variants:

```bash theme={null}
traceroute -n 203.0.113.10              # no name lookups, faster
sudo traceroute -I 203.0.113.10         # ICMP echo, like Windows tracert
sudo traceroute -T -p 443 203.0.113.10  # TCP SYN to port 443
traceroute -6 2001:db8::10              # IPv6
```

`-I` and `-T` need root privileges; without `sudo` you get "You do not have enough privileges to use this traceroute method".

## How to run tracert and pathping on Windows

Open **PowerShell** or **Command Prompt** and run:

```powershell theme={null}
tracert -d 203.0.113.10
```

`-d` skips name lookups. [`tracert`](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/tracert) stops after 30 hops and waits 4 seconds per reply by default.

For per-hop loss statistics, use [`pathping`](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/pathping). It first lists the route, then sends 100 queries to each hop, so it takes a few minutes:

```powershell theme={null}
pathping -n 203.0.113.10
```

In PowerShell you can also run `Test-NetConnection 203.0.113.10 -TraceRoute`.

### WinMTR

**1. Start WinMTR**

Open `WinMTR.exe` and type the server IP in **Host**.

**2. Run the test**

Click **Start** and let it run for at least 100 packets (about 2 minutes), ideally while the problem is happening.

**3. Copy the results**

Click **Stop**, then **Copy Text to clipboard** and paste the result into your ticket.

## Frequently asked questions

### Why does traceroute stop or show `* * *` before the destination?

A firewall on the path or on the server drops the probes. Try a different method: `sudo traceroute -T -p 443` on Linux or `mtr -T -P 443`. Single hops with `*` in the middle are normal when the later hops answer.

### Should I run MTR from my computer or from the server?

Both. The route back from the server is often different from the route to it. Run one report each way during the problem and compare.

### Is MTR the same as WinMTR?

WinMTR is a separate Windows program that shows the same kind of per-hop statistics. Results are comparable, but use the same packet count for both.

### How long should MTR run?

At least 100 cycles. Short runs (10 cycles) hide occasional loss.

## Related guides

> [card] [VPS and dedicated server guides](https://help.freakhosting.com/portals/other/vps-and-dedicated-server-guides.md)
>
> Every guide in this section.

> [card] [Diagnose network latency](https://help.freakhosting.com/portals/other/how-to-diagnose-network-latency-issues.md)
>
> Read the results and find the cause.

> [card] [Test speed with iperf3](https://help.freakhosting.com/portals/other/how-to-test-network-speed-with-iperf3.md)
>
> Measure throughput between two hosts.

> [card] [Enable ICMP on Windows](https://help.freakhosting.com/portals/other/how-to-enable-icmp-on-windows.md)
>
> Let your Windows server answer ping.

> [card] [Check if a port is open](https://help.freakhosting.com/portals/other/how-to-check-if-a-port-is-open-from-outside.md)
>
> Test a service from outside.

***

> [!NOTE]
>
> **Checked against the [Ubuntu mtr man page](https://manpages.ubuntu.com/manpages/noble/man8/mtr.8.html) and Microsoft Learn ([tracert](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/tracert), [pathping](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/pathping), [Test-NetConnection](https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection))** on 4 November 2026; Linux commands tested on Ubuntu 24.04 LTS (mtr 0.95, traceroute 2.1.5). Commands can differ on other distributions or releases.

> [!NOTE]
>
> ### Need Extra Help?
>
> If you encounter any issues, our support team is ready to assist:
>
> * **Live Chat:** Quick assistance via our website.
> * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
> * **Discord:** [Join our Community](https://discord.gg/freakhosting)
> * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)

> [!TIP]
>
> ### Save on Your Hosting
>
> Ready to upgrade your hosting? Use code **KB20** at checkout for **20% off** your first order!

***

**Last Updated:** November 2026


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.