utilitech

Network Hop Checker

Trace the route and see every hop from our server to your destination — a live, animated traceroute map with latency and packet loss per hop.

Traceroute settings

Echo requests, like Windows tracert. Usually shows the most complete path.

1–30. Most routes take 8–20 hops.

How long to wait for each hop to answer.

Network route

Enter a destination and press Start traceroute.
sourceutilitech serverdestination—
answered timed out unreachable packetsScroll sideways for long routes.

Total hops

0

Execution time

—

Average latency

—

mean of each hop's average

Maximum latency

—

Packet loss

0%

Hops

Hops appear here as the trace discovers them.

How to use
  • Enter a hostname (like google.com) or a public IP address and press Start traceroute. Each router on the way appears on the map as it answers, with its latency above it.
  • Green hops answered, grey ones didn't reply in time (many routers ignore traceroute probes, so a grey hop in the middle of a working route is normal), and red means a router reported the destination as unreachable.
  • The table lists all three round-trip times for every hop, its reverse-DNS name, and how many probes were lost. The cards above it sum up the whole route.
Protocols
  • ICMP sends echo requests, like Windows tracert. It usually shows the most complete path.
  • UDP is classic Unix traceroute: probes to high UDP ports.
  • TCP probes port 443 (HTTPS). Try it when a firewall drops ICMP and UDP and the trace stops early.
Good to know
  • The trace runs from our server, not from your computer, so it shows the path from our data centre to the destination. To trace from your own network, run tracert (Windows) or traceroute (macOS, Linux) yourself.
  • Only public destinations can be traced: private, local and reserved addresses are refused. Traces are limited to 30 hops and a few per minute, and destinations aren't stored.