All articles
Troubleshooting 5 min read

Troubleshooting Network Connectivity with Ping and Traceroute

Two free tools that answer most "the internet is down" calls. Here is a repeatable way to use them to find where a connection breaks.

By MARJUN S. CASALTA · IT Network Support Specialist

When a user reports that "the network is down," the first job is to find out where the problem is. Ping and traceroute are built into every operating system and, used in the right order, they narrow the fault down in minutes.

Work from the inside out

Test each hop between the user and the destination, starting with the closest. The first test that fails tells you where to look.

  • Ping 127.0.0.1 — confirms the computer's own network stack works.
  • Ping the default gateway (for example 10.0.1.1) — confirms the local network and switch path.
  • Ping a public IP such as 8.8.8.8 — confirms the firewall and internet link.
  • Ping a domain name such as google.com — confirms DNS is resolving.

Reading ping results

Look at three things: whether replies come back, the response time, and packet loss. Occasional high times are normal on Wi-Fi; consistent loss above a few percent points to a bad cable, interference or an overloaded link.

ping -n 20 10.0.1.1        (Windows)
ping -c 20 10.0.1.1        (Linux / macOS)

Finding the broken hop with traceroute

Traceroute (tracert on Windows) lists every router between you and the destination. When replies stop or times jump sharply at a particular hop, that hop — or the link just before it — is where to focus.

tracert google.com          (Windows)
traceroute google.com      (Linux / macOS)

Some routers ignore traceroute probes and show asterisks even when traffic passes normally, so judge by whether later hops still respond.

Document what you find

Record the time, the tests you ran and the results. Patterns over several incidents — the same hop, the same time of day — often reveal the real cause, such as an ISP issue or a backup job saturating the link.

More articles