Home › All Tools ›

Traceroute Tool

Use Traceroute Tool online for free at FreeToolZones — no sign-up, no watermark.

Loading tool...

When you visit a website, your traffic does not travel directly to the server. It hops through a series of routers: your home router, your provider network, transit networks, and finally the destination network. A traceroute maps those hops, showing each router address and the time to reach it, which reveals where delays and failures occur. The Traceroute Tool on FreeToolZones is planned as a server-side service, and this page explains honestly why it cannot yet run in your browser, what it will show once the required service is connected, and how to run a traceroute today from your own computer.

The widget on this page currently shows a “coming soon” notice. A traceroute sends packets with increasing time-to-live values and listens for ICMP replies to map each hop, and browsers cannot send raw ICMP packets or control packet TTL. This article explains how traceroute works, gives the exact commands named in the notice for Windows, Mac, and Linux, teaches you to read the output, and points to the working browser tools that answer related timing questions now.

What Is a Traceroute?

A traceroute is a network diagnostic that discovers the path packets take from a source to a destination, hop by hop. It works by exploiting the time-to-live, or TTL, field in IP packets. The sender transmits a packet with TTL set to 1. The first router decrements it to 0, discards the packet, and returns an ICMP Time Exceeded message, revealing its address. The sender then transmits with TTL 2, revealing the second router, and so on, increasing the TTL until the packet reaches the destination, which returns a different reply indicating arrival. Each hop is typically probed three times, and the round-trip time for each probe is recorded.

The output is a numbered list of hops. Each line shows the hop number, the router host name where reverse DNS provides one, the router IP address, and three round-trip times in milliseconds. The pattern of times tells a story: a sudden jump between two hops indicates a slow link or a long-distance hop, consistent high times after a certain hop indicate congestion or distance beyond that point, and asterisks indicate probes that received no reply, which can mean a router that does not answer ICMP, a firewall filtering the replies, or packet loss. Reading a traceroute is a skill of pattern recognition, not of judging any single number.

Traceroute is a standard tool in every network engineer toolkit because it localizes problems. A ping tells you the total time and whether the destination answers, but not where the time is spent or where packets are lost. A traceroute shows the intermediate path, so an engineer can tell whether a delay is in the local network, the provider network, a transit network, or the destination network, and can direct the complaint or the fix to the right party. Without it, slow connections produce blame without evidence.

Why This Tool Shows a Coming Soon Notice

The notice states the reason directly: a traceroute sends packets with increasing TTL values and listens for ICMP replies, and browsers cannot send raw ICMP packets or control packet TTL, so a traceroute cannot run inside your browser. Browsers expose no API for crafting IP packets, setting TTL, or receiving ICMP messages. Those capabilities require raw socket access, which operating systems restrict to privileged programs for security. A web page that claimed to run a traceroute purely in the browser would have no way to perform the measurement it describes.

The correct implementation is server-side: a server runs the traceroute from its own location, collects the hop list, and returns it to the browser. That version is planned for this tool. Until it is connected, the notice gives the command-line alternative, which is the most useful form anyway for diagnosing your own connection, because a traceroute is meaningful only from the source whose path you care about. A server-side traceroute shows the path from the server, not from your home, and the two paths can differ completely.

This location dependence is worth emphasizing. If your connection to a site is slow, a traceroute from a distant server will not show your local bottleneck. The command-line traceroute from your own computer is the right diagnostic for your own path, while a server-side traceroute is right for checking the path from a hosting location or a monitoring point. Both have their place, and the planned tool will make its viewpoint explicit so results are not misread as representing your connection.

How to Run a Traceroute Today

The notice names the commands for each operating system. The steps below expand on them so first-time users can run a traceroute confidently and read the result.

  1. Open a terminal. On Windows, open Command Prompt or PowerShell. On Mac, open Terminal from Utilities. On Linux, open your terminal application. No installation is needed on most systems, because the tools are built in.
  2. Run the command for your system. On Windows, type tracert example.com and press Enter. On Mac and Linux, type traceroute example.com and press Enter. Replace example.com with the domain or IP address you want to trace. The trace takes from a few seconds to a minute, depending on the number of hops and on timeouts at unresponsive hops.
  3. Read the hop list top to bottom. Hop 1 is usually your home router. The next hops are your provider network, then transit networks, then the destination network, ending with the destination itself. Each line shows three times; compare them within a line for consistency and across lines for jumps.
  4. Look for the pattern, not single numbers. A jump that persists for all later hops indicates a slow or distant link at that point. A jump that appears at one hop and disappears at the next usually means that one router was slow to answer ICMP, not that traffic is delayed, because routers prioritize forwarding over answering probes. Asterisks at one hop with normal times afterward usually mean that router ignores probes, not that packets are lost.
  5. Save the output for support. Copy the full output, including the command and the destination, into your report. Support teams need the complete hop list, not a summary, because the pattern across hops is the diagnostic evidence. Note the time and the network you traced from.

On Linux, if traceroute is not installed, your distribution package manager can install it, and the mtr tool combines traceroute with repeated ping statistics for a richer view. On Windows, the pathping command provides similar combined statistics. These are optional enhancements; the basic commands named in the notice are sufficient for most diagnosis.

How the Traceroute Tool Will Work

Once the server-side service is connected, the planned tool will run traceroutes from the server location and display the hop list in the browser. This description is a plan for the future version. The current page shows only the notice, and none of these steps can be completed here yet.

  1. Enter a host. You will type a domain name or IP address to trace to, without a scheme or path.
  2. Run the trace. A single button will ask the server to run the traceroute and return the hop list. Traces take time, because each hop must be probed and unresponsive hops must time out, so a short wait with progress indication is expected.
  3. Read the hop table. The planned result will show each hop number, host name, address, and round-trip times in a readable table, with the server location and the trace time stated, so the viewpoint is clear.
  4. Interpret with the guidance provided. The result will include the reading guidance summarized in this article: persistent jumps matter, single-hop spikes usually do not, and asterisks need context from later hops.

The planned version will limit the hop count and the probe rate to sensible values, both to keep traces fast and to avoid abusive use. It will trace to the host you specify from the server location only, and it will not offer traces from multiple locations in its first form. Users who need a trace from their own location should continue to use the command-line method, which remains the authoritative tool for that viewpoint.

Reading Traceroute Output: Common Patterns

  • Steady increase with distance. Times rise gradually as hops get farther away, especially across oceans. This is normal physics: light and signals take time to travel, and a transoceanic hop adds tens of milliseconds that no configuration can remove.
  • Sudden persistent jump. Times jump at one hop and stay high for all later hops. This indicates a slow link, congestion, or a long-distance hop at that point. If the jump is inside your provider network, the provider is the right party to contact.
  • Single-hop spike. One hop shows high times but the next hops return to normal. This usually means that router deprioritized ICMP replies, not that forwarded traffic was delayed. Do not report it as a fault on its own.
  • Asterisks at a hop. No reply was received for some or all probes. If later hops answer normally, the router likely filters ICMP. If asterisks continue to the end, the destination or the path beyond is unreachable or filtering, and the last answering hop is the boundary of visibility.
  • Timeouts at the end. The trace never reaches the destination. This can mean the destination blocks ICMP, a firewall drops the probes, or the destination is down. Combine with a ping test and an uptime check to distinguish those cases.
  • Changing paths between runs. Load balancing can send probes over different routes on different runs, producing different hop lists. This is normal on large networks and is why a single trace is a snapshot, not a fixed map.

Practical Use Cases

Locating the slow segment

When a connection to a specific service is slow, a traceroute shows whether the delay appears early, in the local or provider network, or late, near the destination. An early delay is a local or provider issue. A late delay is a destination or transit issue. That localization determines who can fix the problem and prevents wasted effort on the wrong segment.

Diagnosing packet loss

Repeated traces, or the mtr tool, show which hop drops probes consistently. Loss that starts at one hop and continues suggests a faulty link or congested router at that point. Loss that appears at one hop but not later is usually ICMP rate limiting, not real packet loss for forwarded traffic. The distinction matters, because only the first pattern indicates a problem affecting real traffic.

Verifying routing after a change

After a network change, a provider switch, or a VPN configuration, a traceroute confirms traffic takes the expected path: through the VPN gateway, through the new provider, or directly to the destination. An unexpected path explains surprising latency or access failures and confirms whether the change took effect as intended.

Documenting a fault for a provider

Providers ask for traceroutes because the hop list is objective evidence about their network and its neighbors. A report with a full trace, the destination, the time, and the source network lets the provider identify the affected segment and check its routers and links. A report without a trace usually receives a request for one, so including it first saves a round of messages.

Limitations and Responsible Use

Traceroute shows the forward path for probe packets, which may differ from the return path and from the path taken by other traffic types, because routing can be asymmetric and load-balanced. ICMP handling by routers is often rate-limited or deprioritized, so probe times overstate the delay experienced by forwarded traffic at some hops. Firewalls and MPLS networks can hide hops entirely, producing traces with gaps that do not indicate faults. A traceroute is therefore a diagnostic aid to be read with its patterns in mind, not a precise map or a performance benchmark.

Traceroutes should only be run to hosts you have a legitimate reason to diagnose, such as services you use or systems you manage. Repeated, high-rate tracing can look like reconnaissance and can trigger security alerts. The planned tool will rate-limit traces appropriately, and command-line users should run traces at a normal pace for genuine diagnosis. Results contain router addresses and host names that are public infrastructure details, but they should still be shared thoughtfully, with only the parties who need them for diagnosis.

Frequently Asked Questions

Why does this page not run a traceroute yet?

Because browsers cannot send ICMP packets or control packet TTL, both of which a traceroute requires. A server-side version is planned. The command-line tools on your computer run traceroutes today and show your own path, which is usually the path you need.

What is the difference between tracert and traceroute?

They are the same diagnostic on different systems: tracert on Windows, traceroute on Mac and Linux. The output format differs slightly, but the hop list, addresses, and times convey the same information.

Why do some hops show asterisks?

The router did not reply to those probes, usually because it filters ICMP or rate-limits replies. If later hops answer normally, the asterisks do not indicate a problem. If asterisks continue to the end, the path beyond the last answering hop is hidden or unreachable.

Why is one hop much slower than the others?

It may be a slow link, a long-distance hop, or a router that answers ICMP slowly while forwarding traffic normally. If later hops return to normal times, the spike is likely an ICMP answering delay, not a traffic delay. Persistent jumps matter more than single-hop spikes.

Can a traceroute show my exact route to a website?

It shows the route taken by the probe packets at that moment. Load balancing and routing changes mean the route can vary between runs and can differ for other traffic. Treat a trace as a snapshot of one path, not as a permanent map.

How is a traceroute different from a ping test?

A ping test measures the total round-trip time to a destination. A traceroute measures the time to each intermediate hop, revealing where the total time is spent. Use ping for a quick reachability check and traceroute when you need to localize a delay or failure.

Related Tools

These working tools check timing and reachability from your browser today.

Browse More Tools