Traceroute
Real server-side traceroute from 6 global probes — see the full hop path (hostname, IP, RTT) from each probe to any host, without installing anything.
How to Use
- Enter any hostname (example.com) or IP address.
- Pick how many probes to trace from (2-6).
- Each probe runs a traceroute from its location; hops stream in as they complete.
- Star rows (* * *) are hops that didn't respond within the timeout — common for ICMP-blocking routers mid-path.
Enter a host above and hit Traceroute — hops stream in from each probe in a few seconds.
How to read the results
Frequently Asked Questions
How is this traceroute possible in a browser?
Browsers can't send raw packets. globalping.io runs the actual traceroute on its probe nodes and returns the structured hop list to your browser via HTTPS.
Why so many star hops in the middle?
Many backbone routers rate-limit or drop the ICMP Time-Exceeded packets that traceroute relies on. The path is still there, we just can't see every hop.
Where are the probes located?
globalping.io has probes in 60+ countries contributed by volunteers and datacenter partners. The limit = how many randomly-selected probes run the trace.
Common Use Cases
Find where latency is added
Large RTT jumps between consecutive hops show you exactly where the slowdown is.
Diagnose routing issues
Detect asymmetric paths or unexpected intermediate ASNs.
Compare CDN edge reach
See which POP each probe's traffic terminates at.
Last updated: