Traceroute
A deep-path analysis tool that maps every network hop between the source and the target. It pinpoints the exact location of bottlenecks or failures within the global internet infrastructure.
Enter a domain or IP address and select a specific region.
The tool maps out every single network hop between your chosen region and the target.
For each hop, you get: The IP address (along with the hostname, if it resolves). Three separate round-trip times (RTT). The country and network operator responsible for that hop.
If a hop fails to respond, it is explicitly marked rather than left as a blank row. This allows you to easily differentiate between a slow hop and a completely silent one.
At the end you get a summary: how many unique hops the path passed through, how many countries and networks it crossed, and how many hops timed out along the way. That summary is often the fastest way to read a trace without scanning every line by hand.
Ping tells you if a server is reachable and provides a rough estimate of its speed.
Traceroute pinpoints exactly where delays are occurring along the network path.
When ping times are high, a traceroute reveals the root cause by determining if the issue is:
The destination server itself.
An issue occurring three networks upstream.
A congested transit link.
Traffic being routed through a longer physical path than necessary.
This is especially useful for anything international. A visitor connecting from one continent to a server on another crosses several networks to get there, and occasionally one of those networks has a bad day. Traceroute shows you exactly which hop that is, rather than leaving you to guess whether it's your server, your host's network, or something entirely outside your control.
It's also a good way to check routing after any kind of network change, a new CDN, a BGP update on your provider's side, a change in upstream transit. Comparing a trace before and after a change is often the clearest way to confirm traffic is actually taking the path you expect, and to catch it quickly if a change routes visitors somewhere less direct than before.
The path to a server is not the same from everywhere. A trace from Cape Town crosses different networks than one from Frankfurt, and that difference is usually where the problem actually lives.
Run the same target from a few regions and you can tell whether a slow hop is local to one carrier or something every path has to cross. The tool runs from Cape Town, Frankfurt, Singapore, St. Louis and Sydney, which covers the routes most of your visitors actually take.
It also shows CDN behaviour. A site served from multiple edges should trace short and fast from nearby regions and still look sane from far away. When it doesn't, the trace shows which edge is missing.
Each hop resolves over the address family you picked. IPv4 and IPv6 can take completely different routes to the same destination, through different transit providers and different bottlenecks.
A site can be fast over one family and broken over the other. Running both traces side by side shows whether a problem is specific to one address family or affects the whole path.
The five regions matter here too. IPv6 coverage varies by region, so a route that works from Singapore can fall back or fail from somewhere with thinner v6 transit.
What is a traceroute?
It maps every network hop between a source and a target, with per-hop timing, the IP and hostname when it resolves, and the country and network operator responsible for that hop.
How do I read the results?
Each row is one hop. Three round-trip times are shown per hop, and a hop that doesn't answer is marked as a timeout rather than left blank, so a silent hop is easy to tell apart from a slow one.
Why run a traceroute from more than one region?
Because paths are different from different places. One trace shows the route from a single vantage point, several traces show whether a slow hop is regional or affects everyone.
What's the difference between IPv4 and IPv6 traceroutes?
Different address families take different paths. The two can route through different transit providers and hit different bottlenecks, so testing both catches problems that only affect one.
When should I use traceroute instead of ping?
Ping tells you whether a server answers and how fast. Traceroute tells you where the delay is, which is the step that turns a slow response into something you can act on.
Free Network & Website Tools
Domain Search Tool
Search available domain names instantly with real-time pricing. AI powered brandable name suggestions turn a business idea into ready to register names.
Ping Test
An essential latency test that measures real-time responsiveness and connection stability. It provides critical data on packet loss and round-trip times to ensure a consistent user experience.
Server Check
A comprehensive health audit that verifies server reachability, SSL validity, and CDN performance. It ensures your site is correctly configured and accessible across both modern and legacy IP versions.
DNS Lookup
Verify DNS record consistency across our global network. Check A, AAAA, MX, TXT, and more records from 5 regions with 4 public resolvers each.
MAC Address Lookup
Identify the manufacturer of any network device by its MAC address. Powered by the IEEE OUI database with real-time vendor details.
Robots.txt Tester
Analyze your site's robots.txt file for format errors, crawl rules, and get AI powered optimization suggestions.
IPv6 Test
Check whether your connection and server support IPv6, and verify dual-stack reachability. Confirms your site resolves correctly over both IPv4 and IPv6.
Broken Link Checker
Crawl your site to find broken internal and external links, broken images, and missing ALT text with sitemap validation against search-bot best practices.
