network enabled verified low v1.0.0

traceroute

Network diagnostic tool for displaying the route and measuring transit delays of packets across an IP network.

📋 Live Preview
traceroute {flag-4} {flag-6} {debug} {dont-fragment} {first}
๐Ÿ“Ž flag-4 ๐Ÿ“Ž flag-6 ๐Ÿ“Ž debug ๐Ÿ“Ž dont-fragment ๐Ÿ“Ž first
traceroute {flag-4} {flag-6} {debug} {dont-fragment} {first}

Sandbox: execFile · Timeout: 120s

Capabilities

network.diagnostic.route
network.diagnostic.hop
network.diagnostic.latency
network.discovery.path

Parameters

Name Type Required Default Description Aliases
flag-4 string No - Use IPv4 -4
flag-6 string No - Use IPv6 -6
debug string No - Enable socket level debugging -d, --debug
dont-fragment string No - Do not fragment packets -F, --dont-fragment
first string No - Start from the first_ttl hop (instead from 1) -f, --first
gateway string No - Route packets through the specified gateway (maximum 8 for IPv4 and 127 for IPv6) -g, --gateway
icmp string No - Use ICMP ECHO for tracerouting -I, --icmp
tcp string No - Use TCP SYN for tracerouting (default port is 80) -T, --tcp
interface string No - Specify a network interface to operate with -i, --interface
max-hops integer No - Set the max number of hops (max TTL to be reached). Default is 30 -m, --max-hops
sim-queries integer No - Set the number of probes to be tried simultaneously (default is 16) -N, --sim-queries
flag-n string No - Do not resolve IP addresses to their domain names -n
port string No - Set the destination port to use. It is either -p, --port
tos string No - Set the TOS (IPv4 type of service) or TC (IPv6 -t, --tos
flowlabel string No - Use specified flow_label for IPv6 packets -l, --flowlabel
wait integer No - Wait for a probe no more than HERE (default 3) times longer than a response from the same hop, or no more than NEAR (default 10) times than some next hop, or MAX (default 5.0) seconds (float point ... -w, --wait
queries integer No - Set the number of probes per each hop. Default is 3 -q, --queries
flag-r string No - Bypass the normal routing and send directly to a -r
source string No - Use source src_addr for outgoing packets -s, --source
sendwait integer No - Minimal time interval between probes (default 0). If the value is more than 10, then it specifies a number in milliseconds, else it is a number of seconds (float point values allowed too) -z, --sendwait
extensions string No - Show ICMP extensions (if present), including MPLS -e, --extensions
as-path-lookups string No - Perform AS path lookups in routing registries and -A, --as-path-lookups
module string No - Use specified module (either builtin or external) -M, --module
options string No - Use module-specific option OPTS for the traceroute module. Several OPTS allowed, separated by comma. If OPTS is "help", print info about available options -O, --options
sport string No - Use source port num for outgoing packets. Implies --sport
fwmark string No - Set firewall mark for outgoing packets --fwmark
udp string No - Use UDP to particular port for tracerouting -U, --udp
dccp string No - Use DCCP Request for tracerouting (default port -D, --dccp
protocol string No - Use raw packet of protocol prot for tracerouting -P, --protocol
mtu string No - Discover MTU along the path being traced. Implies --mtu
UL boolean No - Use UDPLITE for tracerouting (default dest port -UL
back integer No - Guess the number of hops in the backward path and --back
help string No - Read this help and exit --help
version string No - Print version info and exit -V, --version

Artifacts

TypeDescriptionMIMESchemaTrust
network.diagnostic.routeHop-by-hop route trace resultstext/plain-verified

Contract

Inputs

network.target.host

Target hostname or IP address to trace

Outputs

network.diagnostic.route

Sequential list of hops with per-hop latency measurements

Side effects: network_traffic

Workflow Edges

Produces

network.diagnostic.route

Consumes

network.target.host

Resource Profile

ResourceValue
CPUlow
Memory8 MB
Networklow
Disk I/Onone

Examples

Standard route trace

traceroute google.com

Trace with numeric addresses only (faster)

traceroute -n google.com

Trace with custom max hops

traceroute -m 15 google.com

TCP-based traceroute to specific port

traceroute -T -p 443 google.com

Basic usage to display the route taken by packets to reach a host

traceroute hostname_or_IP_address

Specify the maximum number of hops (TTL) to be used

traceroute -m max_ttl hostname_or_IP_address

Use a particular protocol (ICMP or UDP)

traceroute -I hostname_or_IP_address   # For ICMP

cheat.sheets: traceroute

traceroute -U hostname_or_IP_address  # For UDP

Specify the number of probe packets per hop

traceroute -q n_queries hostname_or_IP_address

Set the initial TTL (Time-To-Live)

traceroute -f first_ttl hostname_or_IP_address

Specify the wait time for a response

traceroute -w wait_time hostname_or_IP_address

Change the default port

traceroute -p port_number hostname_or_IP_address

Specify the interface to be used

traceroute -i interface hostname_or_IP_address

Display the IP addresses numerically without resolving hostnames

traceroute -n hostname_or_IP_address

Set the source address

traceroute -s source_address hostname_or_IP_address

Documentation

traceroute โ€” Network Path Discovery

Traceroute maps the network path between your machine and a target host by sending packets with incrementing TTL (Time To Live) values. Each router along the path decrements the TTL and sends back an ICMP Time Exceeded message, revealing the route.

How It Works

  1. Sends packet with TTL=1 โ€” first router responds, TTL decremented to 0
  2. Sends packet with TTL=2 โ€” second router responds
  3. Continues until target reached or max hops exceeded

Output Interpretation

traceroute to google.com (142.250.80.14), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.234 ms  1.123 ms  1.456 ms
 2  10.0.0.1 (10.0.0.1)  5.678 ms  5.432 ms  6.012 ms
 3  * * *  (no response)
 4  72.14.237.194 (72.14.237.194)  15.234 ms  14.987 ms  15.567 ms
 5  142.250.80.14 (142.250.80.14)  12.345 ms  12.123 ms  11.987 ms

What to Look For

Indicator Meaning
* * * Hop not responding (firewall, ICMP disabled)
High latency Slow link, geographic distance, congestion
Latency jump Likely where the geographic distance is crossed
Request timeout Packet dropped or filtered at that hop

Related Tools

  • mtr โ€” Continuous trace with real-time statistics
  • ping โ€” Basic reachability and latency testing
  • pathping โ€” Windows tool combining ping and traceroute

Related Tools

mtrpingpathpingtracepath

References