Advanced route diagnostics

Trace the route from real Globalping probes.

This version uses Globalping’s free REST API to run traceroute from distributed probes. A measurement is created with POST /v1/measurements, then the page polls /v1/measurements/{id} until the status is no longer in-progress. Globalping supports traceroute and uses a default “world” location when you provide no location.

Hostname or public IP address

Location

Probe limit

Back to Network Check

Default destination is google.com. Use your detected public IP as the destination to see how the selected remote probe reaches your connection.

Route test results

Hop-by-hop output from the selected Globalping probe location to the destination.

Ready to start

Methodtraceroute

TargetPending

Measurement IDPending

StatusPending

ProbePending

Hop	Details
Run a route test to see hop details.

Live route pulse

The route graphic expands to map the actual hop count with more breathing room as the hop-by-hop results populate below.

Remote probe route Waiting

Ready to trace

Enter a destination or use your public IP as the destination, then run the route test.

Waiting for hops

SourceSelected Globalping probeThis is a remote probe, not the visitor’s local device.

Destinationgoogle.comDefault target. You can switch this to your public IP.

How this trace route tool works

This page runs a remote traceroute from public Globalping probes to the destination you enter. The destination defaults to google.com. The Use My Public IP as Destination button only changes the destination to the visitor’s detected public IP, so the route becomes selected probe → visitor public IP.

Destination: a public hostname or IP address, such as google.com, 8.8.8.8, or the visitor’s public IP.
Location: a Globalping location hint such as world, Florida, Miami, United States, London, Comcast, eyeball, or datacenter.
Probe limit: how many matching remote probes should run the test.