Short answer: what to use on a Mac

WinMTR does not run on macOS, and neither of its forks covered below, WinMTR Redux and WinMTR-refresh, ships a Mac build. The report your provider wants is an MTR report, and any MTR program makes one.

Your situation Use Admin password
You have Homebrew, or don’t mind installing it mtr in Terminal Yes, it runs with sudo
You want a Terminal tool without sudo Trippy (trip --unprivileged) No
No Terminal; the problem comes and goes over hours Netutilus MTR (Pro) No
You only need a quick look at the path traceroute and ping, built into macOS No

Why your ISP asked for a WinMTR report

A single traceroute is a snapshot: one moment, three probes per hop. MTR repeats the trace and keeps probing every hop, so it shows the loss and delay at each router over time. That is how a support desk sees where packets go missing.

Cloudflare’s support guide lists MTR for “connection timeouts/drops” and “site unreachable from specific networks”. It tells Mac users to install MTR through Homebrew and Windows users to use WinMTR, so either program is accepted. WinMTR’s own README suggests its text or HTML export for documenting a problem or filing a complaint with your ISP.

What the desk needs is the hop table (loss %, probes sent, and the reply times for every hop), run against the host they named, for long enough, while the problem is happening.

WinMTR facts

Facts checked on 2026-10-20, from the official WinMTR site and the projects’ GitHub pages.

WinMTR (original) WinMTR Redux WinMTR-refresh
What it is The original, started in 2000 as a Windows clone of mtr Fork with IPv6 support Rebuild with IPv6 support and Unicode
Platforms Windows XP and newer Windows Windows 11 and Windows 10 x64; Windows 11 on ARM best effort
Latest version v0.92, 31 Jan 2011 v1.00, 12 Jan 2014 v0.99, 11 Nov 2025 (x64 and Arm64 builds)
Last commit on the main branch — 13 Jan 2014 8 Jun 2026
Licence Free, open source (GPL v2) GPL v2 GPL v2
Mac build No No No

Sources: WinMTR official site, WinMTR-refresh README and releases, WinMTR Redux releases.

The Mac options, checked the same day:

mtr (Homebrew) Trippy Netutilus MTR
Version 0.96 0.13.0 in Netutilus 1.20.2
Runs on macOS, Linux Linux, BSD, macOS, Windows macOS 14.6 or later
Licence Free, open source (GPL v2) Free, open source (Apache-2.0) Free app; MTR is part of Pro
Needs sudo Yes No, with --unprivileged (macOS only) No
Probes ICMP, UDP or TCP ICMP, UDP or TCP ICMP only, IPv4 only
Export Text report, CSV, JSON, XML JSON, CSV, text and Markdown reports Hop table as CSV or copied text; timeline CSV, outage CSV and PNG report from History

Free on a Mac: mtr from Homebrew

This is the free path, and the one Cloudflare’s guide points Mac users to.

  1. Install Homebrew from brew.sh if you don’t have it.
  2. Install mtr:
brew install mtr
  1. Run a report against the host your provider named. Replace example.com with it:
sudo mtr -rw -c 100 example.com
  1. Wait about 100 seconds. Each cycle lasts one second, and report mode prints the table once all cycles are done.
  2. To keep the report as a file, redirect it:
sudo mtr -rw -c 100 example.com > mtr-report.txt

What the flags do, from the mtr manual:

Flag Meaning
-r Report mode: run the set number of cycles, print statistics, exit
-w Wide report: do not cut host names
-c 100 Number of cycles (pings per hop)
-b Show host names and IP addresses
-n Numbers only, no DNS lookups
-T TCP SYN probes instead of ICMP echo
-P 443 Target port for a TCP trace

The report has one row per hop with the columns Loss%, Snt, Last, Avg, Best, Wrst and StDev. WinMTR shows loss %, sent and received counts and best, average and worst times, so the two read the same way.

If mtr won’t start

  • It asks for sudo. mtr hands the probing to a helper, mtr-packet, which needs extra privileges to send its own packets. Homebrew’s install notes say it plainly: “mtr requires root privileges so you will need to run sudo mtr.” Without sudo, mtr on macOS stops with a “Failure to open” error.
  • The shell can’t find it. Homebrew installs mtr into sbin, not bin. On Apple silicon that is /opt/homebrew/sbin. The standard Homebrew setup line adds both folders to your PATH; on this Mac, brew shellenv prints:
export PATH="/opt/homebrew/bin:/opt/homebrew/sbin${PATH+:$PATH}";

If your shell still can’t find it, call mtr by its full path:

sudo "$(brew --prefix)/sbin/mtr" -rw -c 100 example.com

Trippy, if you’d rather not use sudo

Trippy is a network diagnostic tool inspired by mtr, also free and in Homebrew. On macOS it has an unprivileged mode, so it runs without sudo, and it can write the same kind of report:

brew install trippy
trip example.com --unprivileged -m pretty -C 100

-m pretty prints a text table after the rounds set by -C; -m csv, -m json and -m markdown work too.

No Homebrew and no admin rights

macOS still has traceroute and ping. They are not MTR: traceroute shows the path once, and ping tests only the far end. Together they are enough to see roughly where a problem is. On macOS 27.0.1:

$ traceroute -n -w 2 -m 20 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 20 hops max, 40 byte packets
 1  192.168.1.1  3.457 ms  4.029 ms  3.079 ms
 2  10.20.0.1  15.841 ms  3.669 ms  8.202 ms
 3  172.16.10.10  14.932 ms  3.772 ms  3.594 ms
 4  172.16.10.9  7.728 ms  5.032 ms  6.507 ms
 5  * * *
 6  1.1.1.1  16.142 ms  16.455 ms  30.218 ms

$ ping -c 20 -i 0.5 1.1.1.1
...
--- 1.1.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.220/18.628/48.587/8.922 ms

Hop 5 not answering is normal here: the destination still replies with no loss, so that router just ignores the probes. Netutilus does both of these in a window for free: Traceroute and Ping.

Where WinMTR and command-line mtr are better

  • Free and open source. WinMTR and mtr are GPL v2 and cost nothing. Netutilus MTR is part of a paid Pro upgrade.
  • TCP and UDP probes. mtr -T sends TCP SYN probes and mtr -u UDP. Some networks treat ICMP differently from real traffic, so a TCP trace to the port your service uses can tell a different story. Cloudflare’s guide shows mtr -P with a TCP port and -T. Netutilus MTR sends ICMP only.
  • IPv6. mtr has -6, and both WinMTR forks added IPv6. Netutilus MTR traces IPv4 only.
  • Report files in the expected format. WinMTR saves text or HTML, and mtr prints a plain-text report and can write CSV, JSON or XML. Netutilus copies the hop table as text and saves CSV and PNG files, but writes no text or HTML report file.
  • Servers and scripts. mtr and Trippy also run on Linux, so you can trace from a server at the other end of a connection. Netutilus is a Mac app.

For a one-off report that a host asks for today, Homebrew mtr is the shortest path if you are comfortable in Terminal.

Native MTR on a Mac: Netutilus

Netutilus is a native Mac app with an MTR tool. It probes every hop continuously with no Homebrew, no Terminal and no sudo. It is built for the case where one report is not enough: the problem happens a few times a day, and you need to show when.

  • Hop table. Loss%, Sent, Last, Avg, Best, Worst and Stdev for every hop, updated live. The probe interval is 1, 1.5, 2 or 5 seconds. Copy puts the table on the clipboard as plain text in those columns, and Export saves it as CSV.
  • History. Every run is recorded, and the History tab keeps the last 10 runs for up to 60 days. It draws each run as a heatmap, hops down the side and time across, and sums the run up in one sentence, for example where loss starts and whether it reaches the destination.
  • Outage log. Every stretch of two or more lost probes in a row to the destination, with its exact start and end, even in a run that lasted days.
  • Exports from History. Export offers Export Timeline (CSV)…, Export Outages (CSV)… (when the run has outages), Export Report (PNG)… and Copy, which puts a plain-text hop table and the outage list on the clipboard.

To record a run for your provider:

  1. Open MTR in Netutilus.
  2. Type the host your provider named and press Return.
  3. Leave it running while the problem happens. You can switch to other tools in the meantime.
  4. Open the History tab and pick the run.
  5. Click Export and choose Export Report (PNG)… for the picture, and Export Outages (CSV)… for the exact times. Use Copy for text you can paste into the ticket.

Netutilus is free to download. MTR and its history are part of Netutilus Pro; Ping and Traceroute are free. The app needs macOS 14.6 or later. More on the tool: MTR for Mac.

What to send your provider

  1. The right target. Trace to the server or address the support desk named, not to a random website.
  2. The right moment. Run it while the problem is happening. A clean report from a good hour proves nothing.
  3. Enough probes. At least 100 cycles (-c 100). For problems that come and go, record for hours and send the outage times.
  4. The text, not a photo of it. Paste the mtr report or the copied text into the ticket. Attach the PNG and CSV if you have them.
  5. The time window. Date, time and time zone of the problem, and whether the Mac was on Wi-Fi or Ethernet.
  6. Read it first. Only loss that continues to the last hop is real. Loss at one router in the middle that does not carry on to the destination is usually that router answering probes at the lowest priority, not a fault. Loss from hop 1 onwards points at your own Wi-Fi or router. Loss that starts at hop 2 is usually the line between your router and the provider, which is the provider’s to fix. Check first that hop 2 is not a second router of your own. More in packet loss.

If the loss starts inside your home network, fix that first; the provider will ask anyway. The internet is slow or keeps dropping walks through it.

Commands tested on macOS 27.0.1 on 2026-10-20.

Note: Netutilus is made by Poteam, who publish this site.