Traceroute / MTR

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.

Traceroute / MTR is designed to be straightforward: pick your input, choose the output settings, and generate a result you can copy or download. We focus on predictable defaults so you can get a usable output quickly, then fine-tune only when you need to.

If you’re using this tool for work, treat the result like any other export: verify a small sample first, then run the full job. Small checks (file size, encoding, preview, or a spot-check of values) prevent surprises later when you publish, upload, or share the output.

Quality and compatibility often pull in different directions. When you want maximum compatibility, choose widely supported options. When you want smaller size or faster delivery, pick modern formats and compression settings—but keep an original copy so you can re-export without compounding losses.

Privacy matters. Some tools run fully in your browser, while others may need server-side processing (for heavy conversions or specialized libraries). Where uploads are required, keep files non-sensitive and avoid including secrets in inputs. Always review the final output before sharing publicly.

Troubleshooting tips: if the output looks wrong, try changing one setting at a time, and confirm your input is what you think it is (color profile, transparency, encoding, delimiters, or line endings). Many issues come from an unexpected input variant rather than a broken converter.