Skip to content

🛰 Traceroute

Trace the network path to any server and visualize every hop with latency and packet loss data

TL;DR:

Traceroute shows the network path to a host: every hop (router), round-trip-time to each, ISP/ASN, and geolocation. Helps pinpoint where a connection slows down — home router, ISP, backbone, or target hosting. Uses MTR (Multi Traceroute) under the hood.

Packet RouteEvery hop from source to target
RTT per HopLatency at each routing node
Hop GeolocationCountry and provider for each IP
MTR EngineMore accurate than ping, fuller than traceroute

Why teams trust us

MTR
full route
ms
RTT per hop
30+
hops traced
Free
no limits

How it works

1

Enter host or IP

2

Trace route via MTR

3

Get hop map with RTT

What is Traceroute?

Traceroute shows the path of packets through the network from our server to the target host. Each intermediate router (hop) is displayed with latency and geolocation.

Path Visualization

Each hop with IP, hostname, RTT, and country — all in one table.

Hop Geolocation

See which countries and providers your traffic passes through.

MTR Accuracy

MTR combines ping and traceroute: summary statistics per hop.

Quick Launch

Results without installing software — directly in the browser for any domain or IP.

Who uses this

DevOps

network latency diagnosis

Network engineers

route bottleneck detection

Security

unusual hop analysis

Developers

API latency debugging

Common Mistakes

Treating * as packet lossAsterisks mean the router doesn't reply to ICMP probes, but traffic still passes through.
Only checking the last hopLatency issues can occur mid-path, not necessarily at the target server.
Running only onceRoutes change dynamically. Run multiple times to confirm findings.
Ignoring hop geolocationTraffic through an unexpected country may indicate suboptimal BGP or a security issue.

Best Practices

Compare with baselineSave traceroute under normal conditions and compare during incidents.
Find high-RTT hopsA hop with >100ms latency while neighbors are fast — likely the problem point.
Use during incidentsTraceroute is the first tool when facing slow site or unavailability complaints.
Complement with pingPing measures end-to-end latency; traceroute shows exactly where the problem is.

Get more with a free account

Traceroute history and network latency monitoring for your servers.

Sign up free

What is Traceroute

Traceroute is a diagnostic tool that shows the path data packets take from our server to the target host. Each hop displays the IP address, hostname, and response time. This helps identify problematic network segments and determine where delays or packet loss occur.

Traceroute reveals each network hop between our server in Russia and the target host, showing IP addresses, hostnames, and latency at every point. Use it to diagnose routing problems, identify slow network segments, and compare ISP paths.

Combine with ping to measure overall latency and packet loss, or use DNS lookup to verify name resolution at each hop. Traceroute is particularly useful when debugging CDN routing, peering issues, or geo-restricted content delivery.

Learn more

Frequently Asked Questions

What is traceroute?

Traceroute is a utility that shows the path packets take from your server to a target host. Each "hop" is an intermediate router. It helps diagnose exactly where delays or packet loss occur.

How to read traceroute results?

Each line is one hop: number, IP address/hostname, response time (3 attempts). Asterisks (*) mean the hop did not respond (may be a firewall). A sharp increase in time indicates a bottleneck.

What does packet loss at a hop mean?

Loss at an intermediate hop does not always mean a problem — some routers limit ICMP. If there is loss at an intermediate hop but the endpoint works fine, everything is OK. Loss at the last hop is a real problem.

What is the difference between MTR and traceroute?

MTR (My Traceroute) combines traceroute and ping — continuously sends packets and shows loss and latency statistics for each hop in real time. More informative for diagnosing intermittent issues.

Why does traceroute show asterisks?

Asterisks mean the hop did not respond within the timeout. Causes: firewall blocks ICMP/UDP, router configured not to respond, high load. This is normal for intermediate hops.

How to use traceroute for diagnostics?

Run traceroute to the problematic server. Look for: sharp latency increase (bottleneck), loss at last hops (hosting issue), routing loops (same IPs repeating). Compare with traceroute to a working server.

Automate this check

Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.