Skip to content
PhoneEmailFacebookInstagramWebsite

How to Perform a Traceroute

A traceroute is a network diagnostic tool that tracks the path a data packet takes from your computer to a specified destination on the internet. It shows you each “hop” (router or server) the packet passes through and how long it takes to reach each hop. This can help identify where slowdowns or connection issues might be occurring between your home and the internet destination you are trying to reach.

If you’re experiencing connection problems, running a traceroute can provide valuable information for troubleshooting. You may be asked to provide this information to us, in order to help identify a problem with your service.

Performing a Traceroute to 1.1.1.1

The steps to perform a traceroute vary slightly depending on your operating system. Choose your operating system below and follow the instructions, testing specifically to the IP address 1.1.1.1.

To perform a traceroute on Windows, you will use the Command Prompt.

  1. Open Command Prompt:

    • Click the Start button (Windows icon).
    • Type cmd in the search bar.
    • Click on “Command Prompt” in the search results.
  2. Run the Traceroute Command:

    • In the Command Prompt window, type the following command:

      Terminal window
      tracert 1.1.1.1
    • Press Enter.

  3. Collect the Results:

    • The command prompt will display the results hop by hop. This process may take a minute or two to complete.
    • To copy the results, you can right-click anywhere in the Command Prompt window, select “Mark,” drag your cursor to select the text you want to copy, then press Enter or right-click again.
    • Paste the results into a document or email if you need to share them.
    • Please share these results with Solitary Technology support if you are troubleshooting a connection issue. This information is very helpful for diagnosing problems.

Understanding the Traceroute Output

The output of a traceroute shows a list of hops the data takes. Here’s an example of what a traceroute to 1.1.1.1 might look like:

Terminal window
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 103.189.241.254 (103.189.241.254) 8.423 ms 8.199 ms 7.852 ms
2 et31.nxtpe04.syd01.nexthop.net.au (180.222.192.73) 8.008 ms 7.836 ms 7.776 ms
3 et30-1.nxtpe01.syd01.nexthop.net.au (103.251.4.52) 7.884 ms 8.059 ms 7.857 ms
4 202.77.88.7 (202.77.88.7) 8.679 ms 9.399 ms 9.137 ms
5 108.162.247.81 (108.162.247.81) 31.371 ms 108.162.250.7 (108.162.250.7) 8.925 ms 108.162.247.81 (108.162.247.81) 97.561 ms
6 one.one.one.one (1.1.1.1) 8.569 ms 8.351 ms 8.742 ms
Trace complete.
  • Numbers 1, 2, 3, etc.: These are the hop numbers, indicating each step the data packet takes.
  • Times (e.g., <1 ms, 8 ms, 15 ms): These three numbers represent the time it took for a small test packet to travel to that hop and back (measured in milliseconds). Lower numbers are better. There are usually three tests per hop.
  • Request timed out. or * * *: If you see this for several consecutive hops, it might indicate a problem at that point in the network path. A single timeout might not be an issue, but multiple consecutive timeouts could point to a problem router or a connection issue.
  • Names/IP Addresses (e.g., gateway.local, 103.189.241.254, one.one.one.one): This is the hostname or IP address of the device at that hop.

This output helps identify if the delay or issue is happening near your home (first few hops), within your internet provider’s network, or further out on the internet path.

Still Having Network Issues?

If you’ve run a traceroute and are still experiencing problems, the results can be helpful for our support team.