Fusion Proxy
LoginGet Started

Free Network Tool

Online traceroute

See every router on the path between us and a target host, with country and ASN per hop when known. Helpful for diagnosing routing issues or understanding why latency to a server looks the way it does.

30 hops maxCountry & ASN per hopThree RTT samples per hopPrivate targets blocked

Targets that resolve to private, loopback, or reserved ranges are refused.

What traceroute is good for

Each hop in a trace is a router that handled your packets along the way. By looking at where latency jumps, where the path goes geographically, and which ASNs the traffic crosses, you can usually narrow down whether a slow connection is a local issue, an upstream peering problem, or just physics.

Find where latency jumps

A 200 ms jump between two adjacent hops usually marks the slow link on the path.

See the geographic path

If your traffic to a nearby host detours through another continent, that explains a lot.

Identify the network at fault

The ASN per hop tells you which provider holds each link, which is what you need before opening a ticket.

Compare two paths

Run a trace to a working host and a failing host to see where they diverge.

How to read the output

  1. Hop number. The position of each router on the path. Hop 1 is the first router after our edge.
  2. IP and hostname. Some routers don’t reply — those show up as * * *. That’s normal and not a sign of a problem.
  3. Country and ASN. Best-effort lookup against a public IP-to-ASN dataset. Useful for spotting unexpected detours.
  4. RTT. Three round-trip-time samples per hop in milliseconds. Look for sudden, sustained jumps.

Frequently asked questions

Why do some hops show * * *?
Many routers are configured to ignore or rate-limit the probes traceroute uses. That hop is still forwarding your traffic just fine — it’s simply not replying to us.
Why do my own ISP’s routers not show up?
This trace runs from our network, not yours. The first hops are the routers between us and your target. To see your local hops, run traceroute from your own machine.
Why does the path change between runs?
Internet routing is dynamic. ECMP, load-balancing, and provider-side failover can each pick a different path on every run.
Can I trace to my home router or office network?
No. Targets that resolve to private, loopback, or link-local addresses are refused. Use a local tool from inside your own network for that.
Why is the country wrong for some hops?
IP-to-country lookups reflect the registration of the address, not where the hardware physically sits. A backbone router may answer with an IP registered in another country.
How many hops can a trace go?
Up to 30 hops, with three probes per hop. Anything beyond that is treated as unreachable.

Looking for proxies with predictable routes?

Our datacenter and ISP plans run on a flat network with stable peering across regions.

View plans