TRACE
ROUTE.
Run traceroute, tracert or mtr on your computer and paste the output. Parsing happens locally in your browser; only public IPs are looked up for the map.
Run locally
traceroute example.comtracert example.commtr -rwb example.comTo preserve hostnames, do not use -n on Linux/macOS or -d on Windows. Some routers do not reply to TTL exceeded; those hops appear as timeouts.
Parsed route
| # | HOSTNAME | IP | LATENCY | STATUS | NETWORK / COUNTRY |
|---|---|---|---|---|---|
| Paste output to begin. | |||||
Hops on the map
Only public IPs are sent to the Bit Happens API. Positions show the registry country of each network prefix, not where the router physically is.
Frequently asked questions
How do I use this tool?
Run traceroute, tracert or mtr on your computer, paste the output and the page builds the hop table. You can also run a traceroute or MTR from public probes in Network Diagnostic.
What do the asterisks (* * *) mean?
That router did not answer the probe in time. Many routers rate-limit or ignore these replies; if later hops answer, the path is working.
Does high latency on one hop mean a problem?
Not always. Routers answer traceroute with low priority. It only signals a problem when the high latency carries on through the following hops to the destination.
Does the map show where each router is?
Not exactly. The position is the registry country of the IP block, not the physical location of the equipment.
Is my traceroute output sent anywhere?
No. Parsing happens in your browser. Only for the map are the public hop IPs looked up through the Bit Happens API.