Free Network Tool
Which route does traffic take to your domain?
Enter any domain and watch the network path drawn live, hop by hop: every router it crosses, how long each step takes, and where the slowdowns are — traced from a real probe in a city you pick.
Interactive Trace
Trace any domain. Watch it drawn live.
Browsers aren't allowed to send the raw packets a traceroute needs, so this tool runs the real thing on a volunteer probe in the Globalping open measurement network and streams the route back as each router answers. Pick a vantage point, run the trace, and read the path top to bottom — from the probe's own gateway to the server answering for the domain.
Visual Traceroute
Enter a domain to begin.
Traces run through the Globalping open measurement network of volunteer probes; the route starts at the probe city you pick, not at your own connection. ETTE stores nothing you trace.
Reading the Trace
Three things the route map is telling you.
Each row is a router
A trace works by sending packets that expire after 1 hop, then 2, then 3, forcing each router along the way to reveal itself. The rows read in order: the probe's own gateway first, its ISP next, then the long-haul carriers, and finally the network hosting the destination.
The bars show where time accumulates
Each bar is the round trip to that hop, so healthy routes step up gradually — a few milliseconds inside a city, tens of milliseconds across a continent, a hundred or more across an ocean. A jump that persists through every later hop marks the link where the delay really lives.
Quiet hops are normal
Routers answer trace probes as their lowest priority, and plenty of networks mute the replies entirely. A silent hop in the middle of a trace that still reaches the destination is cosmetic. The pattern that matters is a trace that goes quiet at one network and never comes back.
Common Questions
Traceroute, explained plainly.
What does a traceroute actually show?
Every packet you send crosses a chain of routers between the starting network and the destination server. A traceroute coaxes each router on that chain into identifying itself, one hop at a time, and records how long the round trip to each one takes. Read top to bottom, it is a map of the route your traffic takes and where along that route the time is spent.
Why does the trace start from a probe instead of my computer?
Traceroute needs to send raw network packets with hand-set time-to-live values, and browsers are deliberately not allowed to do that. So this tool runs the real traceroute on a volunteer probe in the Globalping open measurement network, in a city you pick, and streams the results back. To trace from your own connection, run 'tracert' in the Windows terminal or 'traceroute' on a Mac.
Why do some hops show no reply?
Many routers answer trace probes slowly, only sometimes, or not at all, because answering is their lowest priority and some networks switch it off entirely. A silent hop in the middle of a trace that still reaches the destination is cosmetic, not a fault. It only points to a problem when the trace goes quiet at one network and never comes back.
When is a slow hop actually a problem?
Latency should step up gradually and stay stepped up. A single hop showing a high time while later hops drop back down just means that router answers probes lazily, and it is not slowing your traffic. The pattern that matters is a jump that persists through every hop after it. That marks the link where the delay really lives, and which network is responsible for it.
Next Step
Latency where it shouldn't be? We find out whose network it's in.
A trace tells you where the slowdown lives; getting it fixed means proving the case to the right ISP, carrier, or host. ETTE runs this analysis for nonprofits, associations, and small businesses across the DC area — and handles the escalation, the vendor calls, and the follow-through.