networkutils.org

Home / Network Tools / Traceroute

Traceroute

Network Tools

Hop-by-hop path with per-hop latency and ASN owner.

Run this tool: the interactive Traceroute loads here (requires JavaScript). Input: Hostname or IP — e.g. 198.51.100.24.

Description

Traceroute discovers the layer-3 path packets take from our probe to a destination, revealing every intermediate hop (router), the round-trip latency to each, and the ASN that owns each hop so you can see where traffic enters a given network.

Features

✓ Hop-by-hop path discovery with TTL probing
✓ Per-hop round-trip latency across multiple probes
✓ ASN ownership lookup for each hop
✓ IPv4 and IPv6 path tracing

How to Use

Enter a hostname or IP address and run the tool. The probe increments the time-to-live value to force each successive router to respond, mapping the full path to the destination.

Input: Hostname or IP — e.g. 198.51.100.24.

Understanding the Results

Each row is one hop, numbered from 1. The columns show the hop address, resolved hostname, ASN owner, and the latency of each probe attempt. A row of asterisks (* * *) means that hop did not respond within the timeout — common for routers that rate-limit ICMP. A sudden latency jump often pinpoints the link or network where congestion or a routing problem begins.

Common Use Cases & Examples

→ Find which hop or ASN a latency spike is introduced at.

→ Confirm traffic is taking the expected transit path to a partner.

→ Diagnose why one region reaches a service slower than another.

→ Identify the ISP or carrier responsible for a black-hole segment.

Frequently Asked Questions

Why do some hops show only asterisks (* * *)?

Those routers received the probe but chose not to reply with an ICMP time-exceeded message, usually because they rate-limit or block ICMP for security. The path continues beyond them — asterisks do not mean the route is broken, only that the hop is silent.

Where is the congestion if latency jumps at one hop?

A latency jump at hop N usually indicates the delay is introduced on the link between hop N-1 and hop N, or by hop N itself. However, asymmetric return paths can make a hop look slow when the real delay is elsewhere, so confirm with multiple runs.

Does traceroute show the path my users take?

It shows the path from our probe network to the target. Your users’ traffic enters the internet from their own ISP, so their path can differ. Run it from multiple vantage points or compare with the BGP Route View tool to understand variation.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
Probes run from the NetworkUtils.org server using Node.js standard networking libraries. Ping attempts an ICMP echo via the system ping utility and falls back to a TCP connect probe on port 80 when ICMP is unavailable in the probe environment; traceroute uses the system traceroute utility; the Port Check and TCP Handshake tools open real TCP connections to the specified port; the MTU Probe sends progressively larger packets with the Don’t-Fragment flag set.
Technical references
RFC 1393 — Traceroute Using an IP Option · RFC 792 — ICMP