IT
Omnvert

Traceroute / MTR

Server-sideProcessed on our server, then deleted

Your file is uploaded to our server to be processed, so it does leave your device. Temporary files are removed as soon as processing finishes, and the uploaded original is deleted automatically within 120 minutes at the latest. Nothing is stored permanently.

About

Traceroute / MTR shows the path packets take to a host so you can see where latency or filtering begins. Classic traceroute lists hops with numeric IPs and round-trip times; MTR (when available) adds per-hop loss and rolling averages so you get a live-style report without needing a terminal. Configure max hops and probe count to keep tests concise while still revealing routing changes.

Use traceroute to answer questions like: does traffic stay inside the ISP or break out through a VPN/peer? Where does a CDN edge hand off to a transit provider? Which hop starts dropping packets during an incident? Because results are numeric, you can quickly spot private hops, CGNAT, or data-center networks. When MTR isn’t installed, the tool falls back to traceroute automatically and marks the response.

Loss in MTR should be interpreted carefully: loss on early hops that disappears later often indicates ICMP deprioritization, not actual packet loss to the destination. Combine this view with ping/HTTP tests to confirm whether the final hop is healthy. Adjust max hops (up to 30) to avoid extremely long traces while still surfacing middle-mile issues.

Outputs are copyable JSON plus raw text so you can paste them into tickets, postmortems or routing requests. Everything runs server-side with SSRF protections—private/reserved targets are blocked up front. That keeps traces safe while still providing the visibility needed for SRE, NetOps and support teams.

Common workflows: triaging a slowdown by seeing which hop adds >100ms; proving that a regional outage stops before your infrastructure; checking whether a VPN exit really uses the expected ASN; or documenting ISP peering paths for procurement and capacity planning.

How it works

  1. 1Open Traceroute / MTR and choose your file or enter the required input.
  2. 2Check the settings and start the process.
  3. 3The tool creates the result with temporary server-side processing.
  4. 4Download the output or copy the result when it is ready.

FAQ

›Traceroute vs MTR?
Traceroute lists hops once; MTR (when installed) aggregates multiple probes and shows loss/latency per hop in one table.
›What do asterisks mean?
Asterisks indicate no reply within the timeout for that probe—often due to ICMP rate limits or filters.
›Why is MTR unavailable?
Some systems don’t have mtr installed. The tool falls back to traceroute and marks the response header.
›Does loss on hop 1 always matter?
Not always. Many routers deprioritize ICMP to themselves but still forward traffic, so check the final hop and downstream loss.
›How many hops can I trace?
Up to 30, with a small probe count (1–5) to stay within timeouts and avoid stressing the path.
›Can I export results?
Yes. Copy JSON or raw text directly from the UI to share in tickets or monitoring notes.

Guides & tutorials

See all 2 guides →
Using Traceroute to Find Where a Connection Slows Down
Traceroute maps the routers between you and a host and times each one. The trick is reading it correctly: one slow middle hop usually means nothing, and a persistent jump at the end is the real problem.
Jul 09, 2026 • 9 min
How to Check Whether a Port Is Open, and What the Result Means
Open, closed, and filtered are three different answers, and telling them apart is the whole skill. Here is what the TCP handshake reveals and why a firewall makes a port look filtered rather than closed.
Jul 07, 2026 • 7 min