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 distance. Latency that spikes at one hop and drops at the next is that router answering slowly, not forwarding slowly.
- A trace that stops short is usually a firewall dropping probes, not a broken path. Confirm with a TCP probe to the real service port.
- 100.64.0.0/10 is carrier NAT — the ISP's space, not yours, and not the same thing as your LAN.
- 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.
Plate —Other tools
More on the bench
- 01Switch Config AuditorPaste a running-config, get the findings.
- 02Drive Health ReaderPaste smartctl output, get a straight answer.
- 03Subnet CalculatorCIDR in, everything else out.
- 04PoE Budget PlannerWill the switch actually carry the load?
- 05Camera Storage CalculatorHow many terabytes for how many days.
- 06Transfer Time CalculatorHow long the migration window really needs to be.
Free diagnosticsSame-day dispatchNo outsourcingDone or free
Want a second opinionHappy to look at it
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.