How to Understand Traceroute results
Select one of the links below to jump to a query:
Understanding Traceroute results
Traceroute results are similar for both Windows and Mac OSX.
- During a traceroute, each new server the data goes to is called a hop. By default, a maximum of 30 hops will be traced.
- In a list of traceroute results, these hopes will be numbered, with the last hop always being your destination address (unless the data is unable to reach teh destination).
- Three latency times (in milliseconds) will be shown next to each hop. The mean average of these times is considered to be the latency for that server.
- Following the latency times, the server’s domain and/or IP address will be shown. Typically you’ll be able to search online for a specific IP address to get a better idea of where it is.
- It’s not uncommon for certain hops to be traced as “* * * Request timed out”, such as hop 3 in the example below. This is because the server is deliberately ignoring the ICMP packets sent by a traceroute program, so there’s nothing to worry about.
As usual, if you happen to run into some problem while following the steps, please make sure to let us know in the comment section below, and we’ll do our best to solve it. Apart from that, you can contact us on Facebook and Twitter, however we can’t guarantee you an as rapid a reaction time over on those platform