Traceroute Hop Cards
Turn pasted Linux traceroute or Windows tracert text into hop cards with RTT bounds, unanswered probes and cautious latency-rise markers.
About this traceroute hop cards
Turn pasted Linux traceroute or Windows tracert text into hop cards with RTT bounds, unanswered probes and cautious latency-rise markers Performs protocol inspection, IP calculation, and network analysis client-side without sending probes or exposing network topology.
Protocol mechanics & network logic
Paste one English Linux traceroute or Windows tracert run. Analyze to show one card per numbered hop, preserving responder text and counting replies and stars. The legacy JSON parser remains below.
Worked network diagnostic scenario
Scenario: Review two pasted traceroute-style lines, one with RTT samples and one timeout.
Sample input:
Processing: Match numbered lines, collect the three ms values and IPv4 address, then mark the star-only second hop as timed out. For 1 router (192.0.2.1) 10 ms and 2 edge (192.0.2.2) 70 ms, local means are 10 and 70 ms; the 60 ms rise is highlighted. A following 3 * * * card has no RTT and no congestion conclusion.
Illustrative output:
Addressing limits & protocol boundaries
Both inputs must be strictly below 500000 UTF-8 bytes. The card view accepts increasing hop numbers 1–255 and ms or <ms probes. MTR tables, other output dialects and annotation meanings are not parsed. No packets, DNS lookup, geolocation or route validation are performed. Values are displayed to six decimals.
Addressing calculations and subnet models in Traceroute Hop Cards follow IETF RFC definitions. Ensure subnet masks and CIDR prefixes match your network topology.
Offline network inspection boundary
Address parsing and CIDR calculations in Traceroute Hop Cards run entirely client-side without probing external IP networks or transmitting routing data.
IETF RFC specifications & IANA registries
IETF Request for Comments (RFC) standards and IANA registry references:
- Implementation-specific browser utility or reference guide (no single governing external standard)
Traceroute Hop Cards verification · Audit standards
How to use it
- Enter, paste, or select your input data into the Traceroute Hop Cards workspace controls.
- Review parameter fields, units, or options configured for Traceroute Hop Cards.
- Click the action button or observe immediate live calculations rendered by Traceroute Hop Cards.
Frequently asked questions
What does the card view parse?+
Operational requirements for "What does the card view parse?" are verified in local memory during execution of Traceroute Hop Cards.
Do stars mean a broken link?+
A star records an unanswered probe before the terminal timeout, not proven forwarding loss. Filtering, rate limits or router reply policy can cause stars. A later reply does not reveal why an earlier probe was unanswered.
Does red identify congestion?+
Red highlights mean the lowest possible increase in mean RTT versus the immediately preceding numbered hop is at least 50 ms. This is a comparison heuristic, not per-link delay or proof of congestion. Missing replies or skipped hop numbers prevent comparison. Return paths and reply priorities can differ.
What does the example show?+
Security isolation for "What does the example show?" ensures zero transmission beyond your local workstation.