Free Traceroute Tool & Shareable Network Report

Traceroute maps the exact sequence of Layer-3 routers (hops) that data packets traverse to reach a remote server. It works by sending packets with incrementing Time-To-Live (TTL) values. When the TTL reaches 0 at a router, that router discards the packet and replies with an ICMP Time Exceeded message, revealing its IP address and round-trip latency.

Asterisks on an intermediate hop do not necessarily indicate a broken network. Many Tier-1 backbone routers and firewall appliances (such as Cisco or Juniper border gateways) deliberately deprioritize or drop ICMP TTL Exceeded responses to protect their control plane from denial-of-service attacks. If subsequent hops respond normally and the final destination is reached, the connection is healthy.

A web-based traceroute measures the network path originating from Uzvera's cloud data center probe to the target destination. In contrast, running traceroute from your local terminal measures the path from your local ISP / office router. Web traceroutes are ideal for verifying whether a server is accessible from global cloud backbone networks.

When diagnosing ISP routing issues or packet loss for a client, technicians can click 'Share Report' to generate a clean, unlisted URL or 'Download Branded PDF'. The resulting report contains no confusing advertising, includes formal Uzvera verification metadata and a QR code, making it suitable for attaching to ISP escalation tickets or client deliverables.

Within the same metropolitan or regional area, hop latency should typically remain under 15ms to 30ms. Transcontinental cross-country routes (e.g., US East to West Coast) typically measure 60ms to 80ms, while transoceanic intercontinental routes (e.g., US to Europe or Asia) range from 100ms to 200ms depending on undersea fiber cable paths.