Traceroute
Inspect network hops to an IP or domain.
A traceroute maps the routers between a probe and your target by sending packets with increasing hop limits, so each router in turn reports back. It shows where along the path delay appears — which is how you tell a slow server from a slow route.
Start a check
Public internet targets onlyResults
Ready when you are
Enter your details above and run the tool.
How Traceroute works
What it does
Inspect network hops to an IP or domain.
What you get
The responding network hops along a remote probe’s route.
Live data sources
The target is sent to a network provider. Results include their source; timeouts and unavailable data are clearly marked.
What if a check cannot finish?
Confirm your input and try again. A timeout, blocked request, or unavailable provider is not proof that a domain is broken. Internet measurements and third-party services have limits.
Traceroute — frequently asked questions
Some hops show asterisks. Is the route broken?
No. Many routers are configured not to answer traceroute probes while still forwarding traffic normally. Gaps in the middle are expected; only a trace that stops and never resumes indicates a real break.
Why does one hop show high latency but later hops are fast?
That router deprioritised your probe, which is cosmetic. Real trouble looks like latency that rises at a hop and stays high for every hop after it.
Does the reply take the same path back?
Not necessarily. Internet routing is often asymmetric, so the return route can be completely different. Tracing from both ends gives the full picture.