Route completeness
A responding target hop and a mostly observed path distinguish a usable RTT bound from an unexplained timeout.
Experimental instrument · Network location
Geography by round-trip time.
Send traceroutes from a world probe cohort, retain the fastest observation from each source, and watch the plausible geography become professionally narrower.
Powered by Globalping · Direct browser APIRequested targetph.aisb.dev
Locked endpointResolved before measurement
MeasurementNot started
Constraint policyIntersection · minimum RTT · vacuum c
Global trace awaiting authorization
Run the measurement to place source probes and construct latency envelopes.
Bounded probe No target RTT Complete feasible area
Probes retained00Awaiting measurement
Finite constraints000 narrower than the globe
Fastest bound—No finite bound
Median prior—Minimum final-hop RTT
Unbounded probes00Awaiting path evidence
Source register0 bounded · 0 unbounded
ProbeMinimumTrace evidence
No source priors yet.
Selected traceNo probe
Select a source probe to inspect its route and request intermediate-hop refinement.
Why traceroute, not only ping?
Ping draws each disk. Traceroute shows why some probes fail to bound it.
Delay localization
Hop timing shows whether latency appears gradually or arrives in one routing jump. It explains a loose bound; it does not turn that bound into distance.
Path stability
Reruns retain the minimum RTT while tracking route fingerprints. Stable ingress evidence raises confidence; route churn lowers it.
Topology corroboration
Shared late hops across independent sources can identify a common ingress network. A separately geolocated ingress could later become another spatial anchor.