Trace the network path to any server and visualize every hop with latency and packet loss data
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.
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.
Each hop with IP, hostname, RTT, and country — all in one table.
See which countries and providers your traffic passes through.
MTR combines ping and traceroute: summary statistics per hop.
Results without installing software — directly in the browser for any domain or IP.
network latency diagnosis
route bottleneck detection
unusual hop analysis
API latency debugging
Traceroute history and network latency monitoring for your servers.
Sign up freeTraceroute 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.
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.
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.
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.
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.
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.
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.
Longer-form reading on this topic from the knowledge base.
Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.