Route on the map
Probe (start)
Located hop
Destination
—
Real probe · Globalping network
Traceroute — every hop, for real
See the actual hop-by-hop path packets take to reach a server: which networks they cross, where the latency arrives, and the route drawn on a real map. Run from a genuine probe on real infrastructure — not simulated from this server's own datacenter.
Protocol
Show hostnames
Locate hops & draw the map
TCP 443 looks like ordinary HTTPS to every network in between, so it is the variant most likely to complete through a firewall — ICMP and UDP are one click away. Locating hops costs one geolocation lookup per hop, so it is capped at the first 10 answered hops, with the destination always kept.
Probe location
The path depends entirely on where the trace starts — the same target from Singapore and from Germany very often takes completely different routes.
Enter a hostname or IP address above, pick a probe location, and run the trace.
Hop-by-hop path
Grouped by the network each hop belongs to, in order from the probe.
Nearby
Further away
Far / slow
No reply
Bar length = latency this hop adds
At a glance
Latency profile
Round-trip time at each answered hop.A hop that shows “No reply” is not necessarily a problem — many routers never respond to traceroute probes at all, or rate-limit them, while forwarding traffic through perfectly normally. What matters is whether the trace reaches the destination, and where latency jumps along the way.
HOW IT WORKS
A Real Trace From Real Infrastructure
This tool does not run traceroute from this server. That would produce a path starting inside whichever datacenter happens to host this site - real, but not what most people actually want to know. Instead, it requests a genuine traceroute from Globalping, a free network of thousands of community-run probes worldwide, from whichever real location you choose (or "Auto" to let Globalping pick a reachable one). Every hop shown is a router that genuinely replied to a probe packet on the way to your target, with its real address and round-trip time - not a simulation.
What else can you check?
These tools all work on the same connection and address data — pick whichever question you actually have.
Want to see the full path to a site?
DNS, redirects, every hop, the CDN, TLS and the origin server.
Want to know your public IP?
See your IPv4 and IPv6 addresses, location, ISP and ASN.
Want to check your tower & route?
Live ping, speed, DNS, traceroute and a map of nearby points.
Want to ping from around the world?
Real latency from real probes across 12 countries, live on a map.
Want to locate any IP address?
City, region, country and coordinates for any public IP.
Want to know if an IP is risky?
Proxy, VPN, Tor, hosting and abuse-report indicators.
Want to know if you're blacklisted?
Check an address against major spam and abuse DNSBLs.
Want to know who owns an IP?
Network owner, ASN, CIDR range and abuse contact.
Want to explore an AS number?
Announced prefixes, BGP neighbours and registry details.
Want to test your connection speed?
Measure real download, upload, ping and jitter.
Want to see what changed?
Word-level diff between two blocks of text or code.
Want to know if a DNS change is live yet?
Compare answers from five independent public resolvers.
Want to verify a domain's nameservers?
Direct authoritative checks, glue records and SOA serials.
Want to check a domain's DNSSEC setup?
DNSKEY, DS records, signature expiry and real validation.
Want to know if a server port is open?
A real TCP connection attempt - open, closed or filtered.
Want to measure latency to a server?
Real connect timing - min/avg/max, jitter and connection loss.
Want a clean URL slug from a title?
Real transliteration, stop words and batch mode.
Want to find and replace across a document?
Regex, capture groups and a live preview before you commit.
Want to find the invisible character?
Code points, escapes, bytes and hidden-character detection.
Want to escape text for HTML?
Minimal, named or numeric entities, attribute-safe.
Want to strip emoji cleanly?
Whole clusters - no half-flags or stray modifiers left.
Want to spot repeated words?
Frequency, density and accidental doubles like "the the".
Want to know if a URL is cached?
Two requests prove whether your CDN is really caching it.
Want to see what a site knows about you?
Storage, cookies, tokens and what your browser actually cached.
Want to run that check on any site?
One-click bookmarklet reads storage and tokens where they live.
Want to know who your site talks to?
Renders the page and names every outside company it contacts.
Is your site one address or four?
www, non-www, http and https - which serve, which redirect.
Need to build an Authorization header?
Basic, Bearer, API key, Digest and AWS SigV4 - signed in your browser.
Want to tidy up a messy SQL query?
Beautify, minify, lint and convert keyword casing for six dialects.
Need to work out a percentage?
Nine calculators covering every way a percentage gets asked.
Want to work out a rise or a raise?
Increases, growth, compounding and CAGR, with the working shown.
Want to work out a discount or a drop?
Discounts, stacked sales and depreciation, with the working shown.
What is actually on that page?
Words, reading time, readability, every image, embed and link.
Need a favicon that works everywhere?
Every size, a real multi-resolution .ico, and the tags to paste.
What headers does a site send back?
Every response header on every redirect hop, explained.
Need to test a regular expression?
Live matches, capture groups, replace preview and code snippets.
Need a JPG as a PNG?
Batch convert in your browser, with optional transparent background.
Need somewhere to jot things down?
Private notes, links, to-dos and reminders saved in your browser.
Need just some pages of a PDF?
Split by page, range or chunk, or extract the pages you pick.
What is hiding inside that image?
EXIF camera settings, GPS tags, colour palette and web checks.
Traceroute FAQ
Why do some hops show "No reply"?
Many routers are deliberately configured not to respond to traceroute probes, or deprioritize them under load, even though they forward your actual traffic normally. A few silent hops in the middle of an otherwise-working trace is expected, not a fault.
Why choose a probe location instead of tracing from "your" computer?
A browser cannot run a real traceroute at all - there's no API for it. Running it from this server would show the path from this server's datacenter, which is usually not useful either. A real Globalping probe gives you a genuine hop-by-hop path from an actual location of your choosing.
Why does the trace sometimes stop before reaching the destination?
Firewalls at or near the destination commonly block the probe packets traceroute relies on, even though the server itself is reachable for normal traffic like a web request. This shows up as the trace ending in unanswered hops rather than reaching the target directly.
Does the probe location affect the result?
Yes, meaningfully - the path (and every hop's latency) depends entirely on where the trace starts from. Tracing the same target from Singapore and from Germany will very often show completely different routes.
Why are only some hops shown on the map?
Placing a hop on the map needs a geolocation lookup for its address, and those cost one request each - so they are capped, and many router addresses are simply not present in geolocation databases or are registered to a company head office rather than the rack the device sits in. The map footer always states how many hops it actually managed to place, rather than looking complete while quietly plotting a handful.