Use ping first to confirm whether a Windows host responds, then use tracert to find where the connection path starts to fail. That simple order saves time during most Windows network troubleshooting because each command answers a different question.
TLDR: ping tells you if a target is reachable and how long replies take, while tracert shows the route traffic takes through routers. For example, if ping 8.8.8.8 shows 75% packet loss, tracert 8.8.8.8 can help identify whether the loss starts at your gateway, your ISP, or farther out. In a small office with 40 users, this can cut a 30 minute guessing session down to 5 minutes. Use both, but do not treat either one as perfect proof on its own.
What ping tells you
ping is the faster test. It sends ICMP Echo Request packets to a destination and waits for Echo Reply packets. On Windows, the default command sends four requests, then reports replies, packet loss, and round trip time.
A basic test looks like this:
ping 192.168.1.1
ping google.com
ping 8.8.8.8The result answers three practical questions:
- Is the host responding? If replies come back, basic IP reachability exists.
- How much latency exists? High average time can point to congestion, Wi Fi trouble, or a distant service.
- Is packet loss present? Even 5% loss can make calls, remote desktop, and file transfers feel broken.
The catch is… a failed ping does not always mean the host is down. Many servers, firewalls, and routers block ICMP replies. A web server may ignore ping while still serving HTTPS traffic perfectly. That is why ping is a quick signal, not a full diagnosis.
What tracert tells you
tracert, short for trace route, shows the path from your Windows computer to a destination. It does this by sending packets with increasing Time To Live values. Each router that handles the packet reduces that value. When it reaches zero, the router usually replies with a time exceeded message. Windows then lists that router as a hop.
A common command looks like this:
tracert 8.8.8.8
tracert www.example.comThe output usually shows numbered hops, three round trip time tests per hop, and the router name or IP address. A clean result might show your local router first, then your ISP, then upstream networks, then the final destination.
Use tracert when ping says something is wrong but does not say where. It helps answer a sharper question: where along the route does the delay or failure begin?
Tracert vs ping: the serious difference
The main difference is scope. ping tests the destination. tracert tests the path toward the destination.
| Tool | Best for | Main weakness |
|---|---|---|
| ping | Fast reachability, latency, packet loss | Does not show where the problem is |
| tracert | Finding the failing or slow hop | Routers may ignore or limit replies |
If a user says, “The internet is slow,” start with ping:
ping 192.168.1.1
ping 8.8.8.8
ping microsoft.comThis sequence checks the local gateway, a public IP address, and DNS name resolution. If the gateway ping is poor, the problem is likely local. Think bad Wi Fi, failing switch, wrong duplex setting, or overloaded router. If the gateway is fine but the public IP is poor, test with tracert.
tracert 8.8.8.8If delays jump from 2 ms to 250 ms after the first ISP hop, you have a strong clue. It may not prove fault, but it gives support staff something concrete to work with.
How to read tracert output without overreacting
A typical line may look like this:
3 12 ms 14 ms 13 ms 203.0.113.1This means hop 3 replied to three probes. The replies took 12, 14, and 13 milliseconds. That is stable. A line like this is more concerning:
6 210 ms 245 ms 231 ms 198.51.100.9If every hop after that also stays high, latency likely increased around hop 6. If only hop 6 is high and later hops are normal, do not panic. Some routers give low priority to diagnostic replies but still forward real traffic normally. It drives me crazy that this looks like a failure when it may just be router policy.
You may also see asterisks:
8 * * * Request timed out.One timeout is not a disaster. Three timeouts can mean the router does not answer tracert probes. If the final destination still replies, the path may be working. If timeouts begin and never recover, that is more useful.
Useful Windows tracert options
Windows includes several switches that make tracert more practical:
tracert -d 8.8.8.8skips DNS lookups. This is often faster and cleaner.tracert -h 15 example.comlimits the maximum hops to 15.tracert -w 1000 example.comwaits 1000 milliseconds for each reply.tracert -4 example.comforces IPv4.tracert -6 example.comforces IPv6.
For daily troubleshooting, -d is especially useful. Reverse DNS lookups can add several seconds per hop. On a 20 hop path, that delay can make a simple test feel painfully slow.
When ping is the better tool
Use ping when you need a fast yes or no. It is ideal for checking a printer, router, server, or workstation. It also works well for watching stability over time.
ping -t 192.168.1.10This runs until you stop it with Ctrl + C. It is useful during cable swaps, router reboots, firewall changes, and Wi Fi testing. If replies drop every 30 seconds, you have a pattern worth checking.
When tracert is the better tool
Use tracert when the destination is slow, remote, or unreachable through several networks. It is the better choice for ISP disputes, VPN routing issues, cloud service access problems, and branch office complaints.
For example, a remote accounting server may fail from one office but work from another. Ping confirms the issue. Tracert may show that the failing office exits through a different ISP route. That is the kind of evidence that moves a support ticket forward.
A practical troubleshooting order
- Ping the local gateway. If this fails, fix the local network first.
- Ping a public IP address. This checks internet reachability without relying on DNS.
- Ping a domain name. If IP works but name fails, suspect DNS.
- Run tracert to the same target. Look for the first hop where loss or delay appears.
- Compare from another device. One bad laptop is different from a site wide fault.
ping and tracert are old tools, but they remain useful because they are built into Windows and give quick facts. Use ping for reachability. Use tracert for path analysis. Read both with care, because blocked ICMP and router policies can mislead you. The best result comes from combining the two commands with basic checks of DNS, Wi Fi signal, cabling, firewall rules, and recent network changes.