Network Path Analysis

Analyze network traffic between server and destination using MTR. Detect packet loss and identify bottlenecks.

Start Network Trace

Enter a hostname or IP address to analyze

Hop Analysis

Latency Measurement

Packet Loss Detection

What We Measure

Hop Latency

Response time for each node

Packet Loss

Identify where packets are lost

Bottleneck Detection

Find nodes causing slowdowns

Network Trace & MTR: Complete Guide to Network Path Analysis

Network path analysis is essential for diagnosing connectivity issues, identifying bottlenecks, and understanding how data travels across the internet. Our free MTR (My TraceRoute) tool combines the functionality of traceroute and ping to provide comprehensive network diagnostics.

Understanding Network Trace Results

Hop Number

Each hop represents a router or network device between source and destination.

Host/IP Address

The hostname or IP address of each network node in the path.

Loss %

Percentage of packets lost at each hop. High loss indicates network issues.

Latency (Avg/Best/Worst)

Round-trip time in milliseconds. Lower values indicate better performance.

Common Network Issues Detected

High Packet Loss

Indicates network congestion, faulty hardware, or configuration issues at specific hops.

Latency Spikes

Sudden increases in response time may indicate overloaded routers or long-distance routing.

Routing Loops

When packets circle between the same hops, indicating misconfigured routing tables.

Frequently Asked Questions

What does "* * *" mean in traceroute results?

Asterisks indicate that the hop didn't respond within the timeout period. This could mean the router is configured to not respond to ICMP packets, or there's a firewall blocking responses.

Why is my latency high at the first few hops?

High latency at initial hops usually indicates issues with your local network, ISP connection, or the first routing nodes. Check your modem, router, and contact your ISP if the issue persists.

What is acceptable packet loss?

Ideally, packet loss should be 0%. Loss under 1% is generally acceptable. Loss above 2-3% can noticeably affect VoIP, gaming, and video streaming quality.