Run an online traceroute from a remote probe
An online traceroute asks a remote probe to collect replies associated with successive hops toward a public target. Enter an IP address or hostname, choose the address family, protocol, and probe region, then start the test. MyIP.dog uses one Globalping probe for each run. The resulting path starts at that probe's network. It does not describe the route from your browser, home router, or current VPN exit.
Read more
Enter a public online traceroute destination
The test form accepts public IPv4 or IPv6 addresses and ordinary public hostnames. Do not include a URL scheme, port, path, or private network address. The example button fills a public resolver address without starting a test. Review the settings and public-results disclosure before submitting. Use a destination you are authorized to diagnose, and avoid putting confidential internal names into a public measurement workflow.
When you enter a hostname, our server resolves the chosen family through Google Public DNS. It follows the relevant alias chain, validates the matching address records, and selects one supported public address. Online traceroute then receives that literal address as its target. Both the entered name and tested address remain visible. This makes the selected destination explicit, although it may differ from an address chosen by your browser's resolver.
Choose the online traceroute protocol
Online traceroute supports ICMP, TCP, and UDP. TCP uses port 443; UDP uses the provider's default traceroute settings. There is no arbitrary port control in this interface. Protocol choice affects how routers and destinations handle probes, so record it with your results. A path that returns more replies for one protocol does not automatically mean the other protocol is broken for ordinary application traffic.
Read an online traceroute report
The result includes the entered target, tested address, selected protocol, target-resolution method, requested region, and latest timestamp. It identifies the actual probe network and provides a link to the public Globalping response. Keep that origin, target, protocol and time attached when sharing a hop list.
Read more
Online traceroute hops are observations
Each online traceroute row represents a reported hop position. The table preserves positions that have no returned address or timing, instead of closing gaps and renumbering later replies. The hop number is not a distance in kilometers. Addresses can identify replying interfaces, and returned hostnames are operator-supplied labels. Neither establishes a router's precise location, ownership of every traversed link, or a complete physical topology.
Successive probes vary IPv4 TTL or IPv6 hop limit. Returned replies can be affected by tunnels, balancing, filtering and different reply paths; hop addresses are not a measured geographic map.
Online traceroute round-trip samples
The timing values in online traceroute are round trips between the remote probe and responding hops. They are not measured delays on the single link between adjacent rows. Subtracting one row from the next can be misleading because the replies can experience different handling or return paths. A later hop can legitimately have a lower RTT.
Missing replies in online traceroute
“No reply” in online traceroute means the corresponding evidence is absent from the received result. A router may forward traffic while declining, filtering, or rate limiting diagnostic responses. A gap can therefore appear before later responding hops. We retain that gap and describe it explicitly. We do not replace it with an invented address or declare the entire route unusable.
The interface also states whether the exact tested address appears among reported hops. If it has not appeared, online traceroute has not established that the target replied as a listed hop. This could reflect incomplete collection, filtering, measurement limits, or other conditions. It does not by itself establish a website outage. Check the collection and probe statuses before treating a partial path as the final result.
Online traceroute collection and probe outcome
Route trace may return partial hop information while the provider continues measuring. The interface updates available results without submitting another test. A finished collection can contain a failed or unavailable probe, so read the probe outcome as well as the collection status. If an unsupported status appears, the interface preserves the source link and identifies the uncertainty instead of assigning a success label.
Local collection has a 50-second deadline after creation. Stop waiting ends that collection while preserving information already received. Clear result removes the visible report. Neither control cancels a route trace at Globalping or deletes its public result. If the submission response is interrupted, the remote job may still exist even when we cannot display its identifier. Do not assume that closing a tab retracts a submitted measurement.
Limits of online traceroute
Route trace does not directly measure the reverse path taken by application traffic, the bandwidth available on each link, or whether an HTTPS transaction succeeds. It cannot expose every hop inside a tunnel. It also cannot prove that a VPN protects every application. For browser-visible exit addresses, use IP comparison. For a short remote reply sample, use the ping test. Those observations complement rather than replace the route report.
Read more
Public online traceroute evidence and limits
Globalping targets and results are public and may remain available for up to six months. A route trace can include router addresses, returned names, and network information. The entered hostname also reaches Google Public DNS when resolution is required. Read the disclosure before starting and review copied reports before sharing them. Clearing the local display does not remove upstream data or copies another person has already obtained.
Route trace here follows the Globalping measurement API and its response schemas. ICMP message behavior is defined in RFC 792 and RFC 4443. Hostname selection uses Google Public DNS. Read our methodology for evidence limits, or use ASN lookup to investigate a public address's observed routing context without assuming it identifies an individual subscriber.