Trace the route from our server to a host: every router hop with its times, up to 20
Checked from our server in India. Only the address you type is sent to us; nothing else leaves your device. Updated on 23 Oct 2026.Traceroute lists the routers a packet crosses on its way to a host. This one runs from our server in India, up to 20 hops with 2 probes each and 2 seconds per probe, and shows each router's address, its name where one exists, and the time it took to answer.
Type a host name or IP address, and keep ICMP probes or switch to UDP.
Press Trace route. The trace takes from a few seconds up to 45.
Read the hops, see where the times jump or stop, then copy the route.
Traceroute works by sending probes with a small time-to-live: the first router on the path discards a probe with a TTL of 1 and says so, the second discards one with a TTL of 2, and so on until the host itself answers. Each answer reveals one hop. This page runs Linux traceroute on our server with 2 probes per hop, waits up to 2 seconds for each, and stops at 20 hops or 45 seconds, whichever comes first.
Each row shows the hop number, the router's address, its reverse DNS name when it has one (names often hint at the city or the network), and the two times. A jump in time between two hops usually marks a long cable, such as the step from India to Singapore or Europe. Times that rise and stay high from one hop onwards point to congestion there.
A star means that router did not answer within 2 seconds. That is common and usually harmless: many routers are set not to reply to traceroute while still passing traffic on. Only stars from one hop to the very end suggest the path is broken or the host filters probes. If ICMP probes stop early, try UDP, which some firewalls treat differently.
The first hops are inside our hosting network, and routers there and inside other providers often use private addresses. Any hop with a private address is marked as private instead of shown. Only public hosts can be traced: private ranges, localhost and this site are refused.
The route shown is the one from India. The path from your own device is different, especially for the first and last few hops; run tracert (Windows) or traceroute (macOS, Linux) on your computer for that. Each visitor can run 3 traces a minute.
A star means a router did not answer the probe within 2 seconds. Many routers are configured not to reply to traceroute, or to reply slowly, while still forwarding traffic normally. Stars in the middle of a route are usually harmless; stars from one hop to the very end suggest a firewall or a broken path.
Both send probes with a rising time-to-live. ICMP mode sends echo requests, the same packets as ping; UDP mode sends packets to unused high ports. Firewalls often treat the two differently, so when one stops before the destination, the other can get further.
Yes, in purpose. Tracert is the Windows command and uses ICMP probes; traceroute on Linux and macOS uses UDP by default and ICMP on request. Both list the routers on the path with their response times, though firewalls that treat the two probe types differently can make their results differ.
Routers inside a hosting network or an internet provider often use private addresses, such as 10.x.x.x. Near the start of the route those belong to our own hosting network, and showing them would describe our infrastructure and help nobody, so any private hop is marked as private while public hops are shown in full.
Each visitor can run 3 traceroutes a minute, and every check on these network tools counts toward a shared limit of 10 a minute and 60 an hour. A trace sends up to 40 probes, which is why it has the tighter limit.
No. Every trace starts at our server in India, so it shows the path from there to the host. Your own route shares the end of the path at best. Run tracert in a Windows command prompt, or traceroute on macOS or Linux, to see the route from your device.
Still stuck? Ask about Traceroute Online and anybody who knows can answer. No account needed.
Also works as: Tracert Online.
On the related tools: IP to ASN Lookup – Map an IP address to the ASN that announces it, with the BGP prefix · DNSKEY Lookup – List a zone’s DNSKEY records with key tags, KSK or ZSK roles, algorithms and key sizes.