Skip to content

Online Traceroute

See the path packets take across the internet, hop by hop, with network names and times.

This tool runs on our server, because a browser cannot send DNS queries, pings or raw network connections. Only the domain, address or URL you enter is sent; results are not stored. Privacy

Shows every router between our server and the host, with response times, reverse DNS and network (AS) names. Takes 10–45 seconds.

Report a problem

Don't include personal or sensitive information.

What happened, and what did you expect? (10–2000 characters) 0 / 2000

Your browser and system, screen size and recent error messages on this page. Never what you typed or your files. Privacy

What is sent
 

Traceroute shows the routers that packets pass through on their way to a host. For each hop you get the router's IP address, its reverse DNS name, the network (autonomous system) it belongs to with its country flag, and the round-trip time of two probes. It is the classic tool for finding where a connection becomes slow or stops.

This online version runs from our server, so you can trace from outside your own network – useful when a customer says your site is unreachable, or to compare the route to two hosting locations. Choose ICMP probes (like Windows tracert) or UDP probes (like Linux and macOS traceroute); routers sometimes answer one and not the other.

How to use the Traceroute tool

  1. Enter a host name or IP address.
  2. Pick the probe type (ICMP is the default) and, if needed, IPv6 only.
  3. Click Trace route and wait 10–45 seconds.
  4. Look for the hop where times jump or replies stop.

Why use ToolOrca Traceroute

  • Up to 20 hops, 2 probes each
  • Reverse DNS and AS number / network name for each public hop
  • Country of each network shown with a flag
  • ICMP or UDP probes, IPv4 and IPv6
  • Private hops inside our own network are hidden
  • Copy the trace as text for a support ticket

How to read a traceroute

Times normally grow as hops get farther away. A big jump between two hops (for example from 20 ms to 180 ms) usually means a long-distance link such as an undersea cable. If one hop shows a high time but the following hops are fast again, that router simply answers traceroute slowly – it is not the problem.

Rows with * mean the router did not answer the probe. A few such rows in the middle are normal. If every hop after a certain point shows * and the destination is never reached, packets are being dropped there or the destination ignores probes – try the other probe type.

What the network names tell you

Each public hop is matched to its autonomous system (AS), the network of an ISP, carrier or cloud provider, using Team Cymru's free IP-to-ASN service. Seeing where the path crosses from your ISP to a transit carrier and then to the hosting provider helps you tell who to contact about a problem.

Frequently asked questions

Why does the trace stop before the destination?

Many servers and firewalls do not answer traceroute probes. The site can still work fine; test it with the port checker or HTTP headers checker.

What is the difference between ICMP and UDP?

They are two ways of sending the probes. Some networks filter one of them, so if one trace stops early, try the other.

Why is the first hop hidden?

The first hops are inside our own network. They are private addresses and are not shown.

How often can I run a traceroute?

A couple of times per minute per visitor, because each trace takes many probes and up to 45 seconds.

Can I check a device on my home or office network?

No. For safety, private and local addresses (192.168.x.x, 10.x.x.x, localhost, .local names and similar) are refused. Our server can only test public hosts on the internet.