Help / Traceroute
Traceroute
Shows every router between a location and a host, which network each belongs to, and where delay or loss begins. Run it from probes worldwide, or paste a traceroute from your own computer.
How to use it
- Type a hostname or public IP address and pick where to trace from.
- Press Trace. It takes 10 to 20 seconds; hops appear as they’re found.
- Read down the table: each row is one router. The notes under a row explain anything unusual.
- To trace from your own computer, copy the command for your system, run it, and paste the output into the box. You’ll get the same table with networks and notes.
Reading the results
- Hop
- One router along the path. Hop 1 is usually your own router.
- No reply (*)
- That router didn’t answer the trace. Very common and harmless if later hops answer.
- Avg ms
- Average round trip to that hop. It should mostly climb as you go; a jump that stays high marks a long link or congestion.
- Loss
- Probes that hop didn’t answer. Only loss that continues to later hops is real loss.
- Network (ASN)
- The organization that runs that router, such as your provider, a backbone carrier, or the destination’s host.
- MTR
- A traceroute that probes each hop several times to measure loss and latency per hop. Probe traces here use MTR.
- Carrier-grade NAT
- Addresses in 100.64.0.0/10 that providers use inside their own network.
Examples
- cloudflare.com A short path to a nearby Cloudflare data center
- bbc.co.uk From the US, usually shows a transatlantic jump
From the command line
curl "https://tools.nexayori.com/traceroute?q=cloudflare.com" curl "https://tools.nexayori.com/traceroute?q=cloudflare.com&format=json"
| q | Host or public IP to trace |
| from | near (default), world, a region, country, city, US-NY, AS13335, AWS… |
| proto | icmp (default), udp or tcp |
| port | Port for TCP/UDP (default 443 for TCP) |
| id | A saved result ID |
| paste | Traceroute output to annotate (text, up to 8,000 characters) |
| format | text (default for curl), json, or html |
Questions
The trace stops before the destination. Is the site down?
Not necessarily. Many hosts and firewalls drop traceroute packets. Try TCP on port 443, and check whether the site loads.
One hop shows 200 ms but the next is 20 ms. Problem?
No. That router answers traceroute slowly because it’s busy forwarding real traffic. Only delay that carries on to later hops matters.
Why is there no “from our server” option?
Cloudflare’s servers can’t send the special packets traceroute needs, so traces run on Globalping probes or your own computer.
Is it safe to paste my traceroute?
Private addresses from your own network are never looked up. Public router addresses are looked up in DNS to name them.
Limitations
- Probe results are public to anyone with the result link, for about six months.
- Paths can differ by direction and change minute to minute.