Skip to content
DromlikDocs
sv

Use the Traceroute tool

Last updated: 2026-08-04

Traceroute maps every gateway a packet passes through on its way from your Dromlik system to a destination server. Where ping tells you whether a host is reachable, traceroute tells you where on the path a problem starts.

Run a traceroute

  1. 1

    Open the tool

    Go to Maintenance > Troubleshooting > Traceroute in the admin console.

  2. 2

    Enter the target

    In Target Host, type the domain name or IP address to trace.

  3. 3

    Start the trace

    Click Start. The system begins tracing the route hop by hop.

  4. 4

    Stop or let it finish

    Click Stop, or wait — the trace terminates automatically when it completes or hits the 30-hop limit.

Read the output

traceroute to example.com (93.184.216.34), 30 hops max, 46 byte packets
 1  * * *
 2  192.168.1.1 (192.168.1.1)  1.853 ms  11.642 ms  19.951 ms
 3  110.80.36.161 (110.80.36.161)  3.008 ms  2.966 ms  3.943 ms
 4  202.97.36.117 (202.97.36.117)  26.446 ms  22.534 ms  20.897 ms
 5  * * *
 6  93.184.216.34 (93.184.216.34)  40.599 ms  41.233 ms  40.481 ms

Each line follows the format HOP Domain Name (IP Address) RTT1 RTT2 RTT3:

  • Hop — each time a packet is passed between routers it counts as one hop. The last hop is the destination.
  • Domain name (IP address) — the router's reverse DNS name when available, which often reveals the carrier and geographic location. If there is no name, only the IP is shown.
  • RTT1, RTT2, RTT3 — the round-trip time in milliseconds for each of the three probes sent to that hop. Three values let you judge how consistent the latency is.
  • * — no response for that probe. This may mean packet loss, or simply that the router is configured not to answer.

Interpreting a trace

What you seeWhat it means
Asterisks at a few middle hops, destination still repliesNormal. Those routers deprioritise or block ICMP; the path is fine.
Asterisks from one hop onward to the endThe path breaks at that hop. Note the last responding hop and its owner.
Latency jumps sharply at one hop and stays highThat hop is congested or is a long-distance link. It is the likely source of call latency.
Latency spikes at one hop then drops againUsually harmless — that router simply deprioritises ICMP replies.
The same hops repeatingA routing loop. Escalate to the network provider.

See also: IP Ping tool, Capture network packets.