{"id":55024,"date":"2022-05-19T07:49:46","date_gmt":"2022-05-19T07:49:46","guid":{"rendered":"\/tutorials\/?p=55024"},"modified":"2025-08-26T11:47:51","modified_gmt":"2025-08-26T11:47:51","slug":"traceroute-command","status":"publish","type":"post","link":"\/tutorials\/traceroute-command","title":{"rendered":"How to use the traceroute command to diagnose network issues"},"content":{"rendered":"

The traceroute command is a network diagnostic tool that shows where connection problems occur<\/strong>. It works by mapping the path your data packets take from your computer to a destination server, displaying each “hop” along the way.<\/p>

Traceroute is especially useful when your internet connection feels slow or a website won’t load.<\/p>

Keep reading to learn how to use traceroute on macOS, Linux, and Windows. We’ll also explain how to read the output to identify common network issues like high latency and packet loss, so you can pinpoint the source of connection problems.<\/p>

\n\n\n\n\n\n\n<\/p>

What is the traceroute command?<\/h2>

The traceroute command maps the path data packets take from a source computer to a destination server<\/strong>. It reveals every step, or “hop,” of the journey, making it essential for network troubleshooting.<\/p>

The command works on most operating systems, though its name varies: Linux and macOS use traceroute<\/strong>, while Windows uses tracert<\/strong>.<\/p>

Here’s a simple breakdown of how it works:<\/p>

    \n
  1. Traceroute sends a small data packet with a time-to-live (TTL) value of 1<\/strong>. This value is like a countdown timer. The packet travels to the first router, which decrements the TTL to 0<\/strong>, causing it to “expire.” The router then sends a “Time Exceeded” message back to your computer.<\/li>\n\n\n\n
  2. Traceroute sends another packet, this time with a TTL of 2<\/strong>. This packet successfully passes the first router and reaches the second router before its TTL expires. The second router then sends the “Time Exceeded” message back.<\/li>\n\n\n\n
  3. This process continues, with traceroute increasing the TTL value by one for each new packet. By recording the source of each “Time Exceeded” message, it builds a complete map of the route your data takes until it finally reaches its destination.<\/li>\n<\/ol>

    This step-by-step mapping is what separates traceroute from the simpler ping command<\/a>.<\/p>

    In short, ping tells you if you can reach a server<\/strong> and measures the total round-trip time, while traceroute shows you how you get there<\/strong> and pinpoints where any delays are happening along the way.<\/p>

    When should you use traceroute?<\/h3>

    You should use the traceroute command to diagnose network performance issues and pinpoint the exact location of connection slowdowns or failures<\/strong>.<\/p>

    It helps you determine whether a connectivity problem lies within your local network, with your internet service provider (ISP), or on the destination server’s network.<\/p>

    The main situations where running a traceroute is useful are below:<\/p>