Traceroute (Visual)
Run a remote traceroute to a public hostname and review the returned path as a numbered visual timeline. Each parsed hop can show a hostname, IP address, and average round-trip time, while timed-out hops appear as asterisks; the raw provider output remains available for comparison. The measurement is made by the ToolsLibrary traceroute service through Globalping, not from your browser or local router, so it reflects the remote probe's route and may differ from a desktop traceroute. Use it only for legitimate troubleshooting of public destinations you own or are authorized to examine.
How to Use the Traceroute (Visual)
Run a remote traceroute to a public hostname, then compare the numbered hop timeline with the provider's raw output.
- Enter a public hostname such as example.com in the Host field.
- Select Trace route and wait while the server requests and polls the remote measurement.
- Read the timeline from hop 1 toward the destination, noting hostnames, IP addresses, and average milliseconds where available.
- Treat asterisks as non-responsive hops, not automatic proof of packet loss or failure.
- Expand Raw traceroute to compare the visual parsing with the original provider output.
How to interpret the route
A latency increase matters most when it starts at one hop and continues through later hops. A single slow intermediate response may only mean that router deprioritizes diagnostic traffic.
Hop hostnames and addresses identify routing interfaces, not verified organizations or physical locations.
Common mistakes
- Comparing this remote route directly with a local desktop trace without accounting for the different source network.
- Treating every asterisk as an outage even when later hops and the destination respond.
- Assuming an intermediate hop with a high response time is slowing forwarded traffic.
Limitations and privacy
The trace runs through the ToolsLibrary network endpoint and Globalping, not from your browser. Provider availability, rate limits, filtering, and the selected remote probe affect results.
The target hostname leaves your browser and is sent for measurement. Do not submit confidential internal names or expect private network routes to be reachable.
Acceptable use
Use traceroute for proportionate diagnostics, education, and systems you manage or are authorized to examine. Do not automate abusive probing, bypass limits, or use route data to target third-party infrastructure.
FAQ
Does this traceroute run from my computer?
No. The ToolsLibrary network endpoint requests a remote Globalping traceroute, so the hops represent the provider-selected probe's path to the target rather than your home or office route.
What information is shown for each hop?
The visual timeline can show the hop number, resolved hostname, IP address, and average round-trip time parsed from the provider response. The raw traceroute output is also available below the timeline.
Why does a hop appear as an asterisk?
An asterisk means that hop did not return a usable response within the measurement. Routers commonly filter or deprioritize traceroute probes, so one missing hop does not by itself prove an outage.
Why is the route different from traceroute on my laptop?
Source location, ISP peering, routing policy, IP version, and current network conditions all affect the path. This tool uses a remote probe, while your laptop starts from your own connection.
Does a high-latency intermediate hop mean the destination is slow?
Not necessarily. Routers may answer diagnostic probes slowly while forwarding traffic normally. Look for latency that begins at one hop and remains elevated through later hops, especially the destination.
Can the tool trace private or internal hosts?
No. The remote measurement service can reach public internet destinations only; private addresses, localhost, and internal DNS names are not meaningful from that environment.
Does the result prove where a server is located?
No. Hostnames and IPs describe routing interfaces, not verified physical locations, and some hops may be hidden or use misleading geographic labels.
What data is sent when I run a trace?
The public target hostname is sent through the ToolsLibrary network endpoint to the traceroute provider. Do not enter confidential internal hostnames or other sensitive identifiers.
What is acceptable use for this traceroute?
Use it for reasonable diagnostics, learning, or checking systems you manage or have permission to examine. Do not automate abusive probing, evade rate limits, or use results to target third-party infrastructure.
Why might the trace fail or time out?
The service may be unavailable, unconfigured, rate-limited, or unable to complete the remote measurement within its timeout. Filtering by the target or intermediate networks can also prevent a usable result.