Traceroute is a tool for measuring the speed and routes that data takes when it goes to the server.

How Traceroute Works

Traceroute sends a series of messages called ICMP Echo Requests to the destination server with the first request with a TTL (Time to live) is 1.

The device will look at the IP address of its route and calculate how long the response time will be, then display it on your screen.

After that, the traceroute will repeat the process above with a larger TTL number (multiple of one), until the data reaches your destination server.

At each process, the route with the IP address will be displayed on your screen. This is what is called a hop, which is the "point" that your data passes through on its way to the server.

Generally, the division of hops is as follows:

  • Hops 1-3 are your devices

  • The hop in the middle is the ISP

  • The hop at the end of the traceroute is the destination server


Unfortunately, not all tracert checks will run smoothly like the example above. If the response is too high, there will be problems with the following terms:

  • Request time out: the server on the hop does not receive the ICMP Echo Request message. This often happens if the server is busy.

  • Asterisk: the server on that hop did not respond to the tracert request. If it only appears once, you can wait for a response at the next hop. However, if several lines of asterisks appear, it is likely that the server is having problems. So, try to make sure by pinging the server.

  • Destination net unreachable: ICMP Echo Request cannot go to the first route. This usually occurs due to incorrect network settings or entering the wrong destination server URL.


Example implementation for trace

$ traceroute