Measure RTT to this site's Cloudflare edge and separate real timing from unavailable hop data.
A real traceroute sends probes with increasing TTL values and records router responses. Standard browser JavaScript cannot send those probes, so this page does not claim to discover the real route.
Each router decrements a packet's TTL. When it reaches zero, a router may return a time-exceeded response. Use your operating system's traceroute or tracert command when you need that hop-by-hop evidence. This browser page measures only an HTTP request to its own edge.
The public egress row contains request metadata, and the Cloudflare edge row receives the only measured RTT. Neither row identifies intermediate routers.
Use a real traceroute to investigate routing paths. Use this page for a quick browser-to-edge RTT sample and to learn which details a browser cannot observe.
A traceroute sends probes with increasing TTL or hop-limit values and records eligible router responses. A missing response does not necessarily mean traffic stopped. See Microsoft's tracert documentation.
It measures HTTP RTT to the site's Cloudflare edge. All other path rows are explicitly unmeasured.
No. Use traceroute on macOS/Linux or tracert on Windows to send the required TTL-limited probes.
A hop is a router or network device that forwards a packet. This page explains that concept but does not discover the actual hops for your target.
Use only the Cloudflare edge RTT as measured timing. Public egress and edge codes are request metadata, not discovered hops.