When diagnosing connectivity issues between your device and a remote server—such as your website or VPS hosted on Ava.Hosting—a traceroute is an essential tool. It helps you trace the exact path your data takes across the internet, identifying each hop (router) along the way and measuring latency at each point.
Whether you’re troubleshooting slow network performance, investigating packet loss, or confirming that traffic is reaching your Ava.Hosting server correctly, running a traceroute provides clear, actionable insight.
A traceroute is a network diagnostic command that tracks the journey of data packets from your local machine to a target IP address or domain. It lists each network hop the packet passes through, along with the time it takes to reach each one. This can reveal bottlenecks, failed nodes, or routing loops—information crucial for resolving DNS, latency, or routing issues.
Press Win + R to open the Run dialog.
Type cmd and press Enter to open the Command Prompt.
Enter the following command:
Replace example.com with the domain or IP address of your server (e.g., tracert ava.hosting or tracert 192.0.2.1).
The output will list each hop, including response times in milliseconds.
Open Terminal (you can find it via Spotlight or in Applications → Utilities).
Run the command:
Wait for the results, which will show the sequence of routers and associated latency.
Open a terminal window.
Use the same command as on macOS:
Note: On some Linux distributions, you may need to install the traceroute package first using a package manager like apt
, yum
, or dnf
:
Each line in the traceroute output represents a “hop” between routers. For each hop, you’ll typically see:
The IP address or hostname of the router
Three response time measurements (in milliseconds)
*
symbols if a response is missing or timed out
Key signs to look for:
Sudden spikes in latency: May indicate network congestion or overloaded nodes.
Asterisks throughout: Could mean that a firewall or filter is blocking ICMP replies.
Timeouts at the end: May suggest the destination is unreachable.
Run traceroute from multiple locations (e.g., a local device, a VPS, or a third-party tool).
Compare results when the issue occurs versus when it does not.
Share full traceroute results with Ava.Hosting support to expedite issue resolution.
Understanding how to run and interpret a traceroute can save time and improve communication with technical support. It’s a simple yet powerful way to identify connectivity problems and understand the health of your network path.
At Ava.Hosting, our infrastructure is optimized for stability and performance, but if you ever encounter connectivity issues, traceroute results can help us resolve the problem faster. Keep it in your toolbox—it’s one of the most important diagnostic commands available.