Hopscotch is the category-defining network path intelligence platform. Trace, analyze, and optimize every gateway your packets traverse β in real time, at scale, with zero blind spots.
Hopscotch turns every TTL increment into actionable intelligence. Real features, enterprise scale.
Traces the exact route packets take from origin to destination, eliciting ICMP TIME_EXCEEDED responses from every gateway along the way. See the full topology.
core-mSet the maximum number of hops with surgical precision. Default 30, configurable to any depth. Stop wasting cycles probing past your network boundary.
-m max_ttl-qSend multiple probe packets per hop for statistically significant RTT measurements. Three probes by default β tune to your confidence interval.
-q nqueries-wSmart wait-time algorithms with three-tier sensitivity: max, here, and near factors. Eliminate premature timeouts without wasting seconds on dead hops.
-w max[,here,near]-APerform autonomous system path lookups in routing registries and print results directly after corresponding addresses. Map the organizational topology of the internet.
-A--mtuDiscover Maximum Transmission Unit along the traced path. Implies don't-fragment mode. See exactly where packet size bottlenecks live in your route.
--mtu-NSend up to 16 simultaneous probe packets. Dramatically accelerate trace execution without sacrificing accuracy. Speed and precision, together at last.
-N squeries-fSkip irrelevant near-side hops by setting the initial TTL. Start your analysis exactly where it matters β not from hop one every time.
-f first_ttlReal-time animated route topology. Every hop, every gateway, every millisecond of latency β rendered as it happens.
Hopscotch sends probe packets with incrementally increasing TTL values, starting from 1. Each packet is designed to expire at the next gateway in the chain.
Each gateway returns an ICMP TIME_EXCEEDED reply, revealing its IP address and hostname. Three probes per hop yield statistically robust round-trip measurements.
Responses are assembled into a complete hop-by-hop topology. Timeouts are flagged, AS numbers are resolved, and MTU bottlenecks are identified.
The full route is rendered with each hop's address, latency, annotations, and unreachability codes β giving you a first-principles view of your network topology.
Firewalls filter what they can't understand. Hopscotch adapts, using the protocol that gets through.
| Capability | UDP default |
ICMP -I |
TCP -T |
UDP Const -U |
|---|---|---|---|---|
| Firewall bypass | Limited | Moderate | Excellent | Good |
| Default port | 33434+ | N/A | 80 (HTTP) | 53 (DNS) |
Custom port -p |
β | β | β | β |
| Half-open technique | β | β | β | β |
| Unprivileged users | β | β (kernel 3.0+) | β | β |
| Destination visibility | Port unreachable | Echo reply | SYN+ACK / RST | Varies |
| Best for | General use | Standard tracing | Firewall evasion | DNS routes |
| Hop | Gateway | AS Number | Probe 1 | Probe 2 | Probe 3 | Status |
|---|---|---|---|---|---|---|
| 1 | 192.168.1.1 |
β | 2.438 ms | 1.921 ms | 1.764 ms | β |
| 2 | 10.0.0.1 |
AS7018 | 8.126 ms | 7.943 ms | 7.812 ms | β |
| 3 | 72.14.215.85 |
AS15169 | 12.643 ms | 12.219 ms | 11.987 ms | β |
| 4 | * * * |
β | * | * | * | β |
| 5 | 209.85.249.19 |
AS15169 | 24.318 ms | 23.891 ms | 23.654 ms | β |
| 6 | 142.250.80.46 |
AS15169 | 25.112 ms | 24.876 ms | 24.543 ms | β |
Start free. Upgrade when your network demands it.
-q 1)-n)-m)-q)-A)-s)-i)-w)-N)--mtu)-f)-z)-p)-D)-P)An asterisk (*) indicates a timeout β the gateway at that hop did not respond within the
configured wait time. This is common with firewalls that drop ICMP TIME_EXCEEDED messages.
It doesn't necessarily mean the hop is down; try switching protocols with -T
(TCP) or -I (ICMP) to probe through filtered paths.
Our TCP engine (-T) uses a half-open technique β sending SYN packets to common
ports like 80 (HTTP) or 25 (SMTP) that firewalls must allow. The destination never sees a
full connection. For DNS-filtered networks, our constant UDP mode (-U) targets
port 53 by default.
Absolutely. Hopscotch probe packets contain no user payload data. We send minimal probe packets (60 bytes for IPv4, 80 bytes for IPv6) with only TTL-manipulation headers. Your routing data is processed locally and never leaves your infrastructure unless you explicitly enable cloud sync.
Yes. Hopscotch automatically detects the appropriate protocol from the destination hostname.
You can also force IPv4 with -4 or IPv6 with -6. Our IPv6 mode is
fully equivalent with complete source routing and flow label support (-l).
UDP (default) sends datagrams to unlikely ports starting at 33434. ICMP (-I)
uses echo requests. TCP (-T) sends SYN packets with half-open technique for
firewall evasion. Constant UDP (-U) targets a fixed port (default 53/DNS). Each
has different firewall transparency profiles β see our Protocol Comparison chart above.