About the Trace Route tool

Network packets traverse the global Internet by "hopping" from one router to another.

Every router knows where it needs to send a packet next to reach its destination, by using routing tables that are dynamically shared across the Internet.

Examining the hops a packet takes to reach its destination can give an indication of where a fault lies.


Use Cases

Use the Trace Route tool on Solid Tools for Developers to:

  • See the path a packet takes from the Solid Tools for Developers server to an IP address
  • Find out where a fault may lie in reaching your IP address from an external network

Usage

Enter a hostname, IPv4 or IPv6 address in the "Hostname or IP address" field.

To trace the route to a server if you don't know its IP address, enter its hostname (e.g. www.google.com) and select whether to use an IPv4 or IPv6 connection. If you select IPv6, the hostname must have an IPv6 (AAAA) DNS record.

To trace the route to a server using its IPv4 address, enter the IP address and ensure the IPv4 option is selected.

To trace the route to a server using its IPv6 address, enter the IP address and ensure the IPv6 option is selected.


Results

The raw output from the "traceroute" command will be displayed. The following example shows a traceroute to www.google.com.

Each line represents another "hop" in the packet's journey.

Hop number 1 is the Solid Tools for Developers server's upstream router. The final hop is the last known position of the packet, which will be the final destination if the trace successful reached the target.

The time displayed is a cumulative elapsed time from when the packet was transmitted.

traceroute to www.google.com (172.217.26.164), 30 hops max, 60 byte packets
 1  10.128.9.115 (10.128.9.115)  0.182 ms  0.181 ms  0.174 ms
 2  fw-d6-x2.memset.net (5.153.250.3)  0.236 ms  0.328 ms  0.330 ms
 3  rtr-dun-2.memset.net (37.128.135.131)  0.637 ms  0.750 ms  0.750 ms
 4  rtr-lon-1.memset.net (37.128.135.99)  21.991 ms  22.099 ms  22.099 ms
 5  v215.core1.lon1.he.net (216.66.85.121)  6.375 ms  6.644 ms  6.874 ms
 6  google1.lonap.net (5.57.80.136)  1.863 ms  1.586 ms  1.659 ms
 7  108.170.246.176 (108.170.246.176)  1.767 ms  1.625 ms  1.704 ms
 8  216.239.58.129 (216.239.58.129)  2.784 ms  2.594 ms  2.558 ms
 9  72.14.236.9 (72.14.236.9)  78.272 ms  78.302 ms  78.301 ms
10  209.85.252.38 (209.85.252.38)  92.251 ms  92.380 ms  92.378 ms
11  209.85.241.43 (209.85.241.43)  132.322 ms  132.406 ms  132.407 ms
12  209.85.240.228 (209.85.240.228)  138.401 ms  138.457 ms  137.594 ms
13  209.85.245.110 (209.85.245.110)  222.938 ms  222.850 ms  222.857 ms
14  209.85.246.43 (209.85.246.43)  290.170 ms  284.781 ms  284.804 ms
15  216.239.63.210 (216.239.63.210)  316.145 ms  316.042 ms  316.119 ms
16  108.170.237.61 (108.170.237.61)  319.109 ms  319.091 ms  319.058 ms
17  maa03s22-in-f164.1e100.net (172.217.26.164)  319.763 ms  319.701 ms  319.806 ms

Run the Trace Route tool