Traceroute FAQs

Traceroute is a network diagnostic tool that maps the path packets take across the internet to reach a destination, revealing each intermediate router and the latency at every step.

Traceroute sends packets with gradually increasing time-to-live (TTL) values. Each router that decrements the TTL responds, allowing the path and timing to be measured hop by hop.

A hop represents a single network device, typically a router, that forwards traffic closer to the destination.

Latency is the round-trip time for a packet to reach a hop and return. Higher latency may indicate congestion, long physical distances, or routing inefficiencies.

Some routers block, rate-limit, or deprioritise traceroute probes. Missing responses do not necessarily indicate a failure.

Asterisks indicate that no response was received within the timeout window. Traffic may still be passing through the hop normally.

Traceroute provides useful diagnostics but is not perfect. Load balancing, asymmetric routing, firewalls, and ICMP filtering can affect results.

Traceroute usually reflects real routing paths, but diagnostic probes may be handled differently from production traffic.

Load balancing can cause traceroute to show multiple paths or inconsistent hop responses, even though connectivity is healthy.

Traceroute can suggest packet loss when responses are inconsistent, but it is not a definitive packet loss measurement tool.

Traceroute may use ICMP, UDP, or TCP probes depending on implementation and platform.

Yes. Firewalls often block or rate-limit traceroute probes, which can cause missing hops or misleading latency readings.

Traceroute is useful when diagnosing slow connections, unreachable services, routing loops, or identifying where delays occur along a network path.

Yes. Traceroute can reveal delays within local networks, ISP routing issues, or upstream connectivity problems.

Cloud networks often use internal routing and virtualised infrastructure, which can hide hops or return limited traceroute information.

Traceroute itself is not harmful, but some organisations restrict responses to avoid exposing internal network topology.

No. Velohost performs traceroutes live and does not store targets, IP addresses, results, or usage history.