Skip to content
(347) 262-9435

Free diagnostic · No sign-up

Traceroute Reader

Paste traceroute, tracert, or mtr output and get the path interpreted: where sustained loss actually starts, which hops are only dropping probes cosmetically, whether a latency jump is distance or a fault, and where your network ends and the carrier's begins.

All three formats are recognised. Parsed in your browser; hop ownership lookup is opt-in and explained below.

Method & assumptions
  • Loss at a single hop is usually not loss. Routers deprioritise generating ICMP TTL-exceeded replies, so a busy core router drops your probes while forwarding real traffic fine. Only loss that persists to the destination is counted here.
  • Latency that steps up once and stays up is the length of a leg. Latency that spikes at one hop and drops again at the next tells you how quickly that router replies to probes, which is unrelated to how it forwards traffic.
  • A trace that stops short usually means a firewall is dropping probes somewhere along the way. Confirm with a TCP probe to the real service port before treating the path as broken.
  • 100.64.0.0/10 is carrier NAT: addressing the ISP runs internally. It looks private and behaves like someone else's network, because it is.
  • Parsing happens in your browser. Hop ownership lookup is the one exception: pressing that button sends the public hop addresses to RIPEstat via this site. Nothing else is transmitted, and the analysis works without it.

Want a second opinion

Happy to look at it
with you

Anyone about to open a carrier ticket, or about to be told the problem is on their end. If you would rather have someone else read it, send it over — no charge for the conversation.

Or call and speak to someone who does the work(347) 262-9435inquiries@jcitsystems.com
  • Free diagnostics
  • Same-day across most of the metro
  • Named technicians
  • No fix, no labour charge