Traceroute from a SIM to a host

Trace the route from the SIM to a host and time every hop, to find where along the path latency or packet loss appears.

A hop is one router that the traffic passes through on its way to the host. When a Ping degrades, traceroute shows at which hop the latency or the loss starts.

Parameters

ParameterRequiredDescription
HostYesDestination to trace.
ProtocolNoicmp (default).
Max hopsNoStop after this many hops. Default: 30.
Packets per hopNoPackets sent at each hop. Default: 10.
Packet sizeNoPacket size in bytes. Default: 64.
Show IPNoDisplay hop IPs instead of hostnames. Default: off.

Plus the shared connection settings.

Results and metrics

In the action report (result):

FieldDescription
total_hopsNumber of hops to the destination.
hops[]Per hop: host, packet_loss_percent, avg_res_time_ms, min_res_time_ms, max_res_time_ms, standard_deviation_ms.
durationTotal execution time in seconds.

In Analytics, each run feeds the traceroute measurement: total_hops plus, per hop (tagged hop_number), the average, min, max, and standard deviation of response times and the hop's packet loss. Tags include source and destination host, protocol parameters, antenna, and access technology.

What's next?

Ping

The end-to-end measurement that triggers a traceroute

DNS Lookup

Rule out resolution before blaming the path

Last updated on