How to Use Ping, Traceroute, and Packet Loss Tests to Diagnose Slow Internet Connections

Slow internet can feel like a mystery: one minute your video call is crisp, the next it freezes into a pixelated slideshow. Your first instinct may be to blame your internet provider, your router, or the website you are trying to reach. But before you restart everything for the tenth time, there are three simple diagnostic tools that can reveal what is actually happening: ping, traceroute, and packet loss tests.

TLDR: Use ping to check whether a destination responds quickly and consistently. Use traceroute to see the path your traffic takes across the internet and identify where delays begin. Use packet loss tests to find out whether data is disappearing in transit, which often causes lag, buffering, and dropped calls. Together, these tools help you determine whether the problem is inside your home network, with your internet provider, or farther out on the internet.

Why Slow Internet Is Not Always About Speed

When people say their internet is “slow,” they often mean one of several different things. A file may download slowly, a game may lag, a website may take forever to load, or a video call may keep stuttering. These issues can have different causes, and a speed test alone does not always tell the whole story.

Your connection might have plenty of bandwidth but still feel terrible because of high latency, jitter, or packet loss. Bandwidth is like the width of a highway, while latency is how long it takes a car to make the trip. Packet loss is like some of those cars vanishing before they reach the destination. A connection can be “fast” on paper and still perform badly if the trip is unreliable.

That is where basic network tests become useful. They do not require advanced equipment, and they are built into most operating systems. With a few commands, you can gather evidence instead of guessing.

Understanding Ping: The Internet’s Echo Test

Ping is one of the simplest and most useful network tools. It sends a small packet of data to a destination and waits for a reply. The result tells you whether the destination is reachable and how long the round trip took.

Think of ping as shouting into a canyon and listening for the echo. If the echo comes back quickly, the path is clear. If it takes a long time, the route is delayed. If no echo returns, something may be blocking or dropping the traffic.

How to Run a Ping Test

On Windows, open Command Prompt and type:

ping google.com

On macOS or Linux, open Terminal and type:

ping google.com

On macOS and Linux, ping may continue running until you stop it. Press Ctrl + C to end the test.

You can also ping a public DNS server such as:

ping 8.8.8.8

Using an IP address like 8.8.8.8 helps separate general connectivity issues from DNS problems. If pinging an IP address works but pinging a domain name does not, your internet connection may be fine but your DNS service may be failing.

How to Read Ping Results

A typical ping result includes several important numbers:

• Reply time: Usually shown in milliseconds, such as 24 ms. Lower is better.
• Packets sent and received: Shows whether packets are making the round trip.
• Packet loss percentage: Indicates how much data failed to return.
• Minimum, maximum, and average time: Helps reveal whether latency is stable or jumping around.

For general web browsing, ping times under 50 ms are usually good. Between 50 and 100 ms is acceptable for many uses. Above 150 ms, real-time activities like gaming and video calls may feel sluggish. However, distance matters: pinging a server on another continent will naturally produce higher results.

Using Ping to Find Local Network Problems

One of the smartest ways to use ping is to test in stages. Start close to home, then move outward.

1. Ping your router: This checks your local Wi-Fi or Ethernet connection.
2. Ping a public IP address: This checks whether your internet connection is responding.
3. Ping a website: This checks both internet connectivity and DNS resolution.

To ping your router, you need its local IP address. Common router addresses include 192.168.1.1, 192.168.0.1, or 10.0.0.1. Try:

ping 192.168.1.1

If pinging your router shows high latency or packet loss, the issue is likely inside your home or office network. It could be weak Wi-Fi, interference, a bad cable, an overloaded router, or a device consuming too much bandwidth.

If your router responds quickly but public internet addresses respond slowly, the problem may be with your modem, your internet provider, or the wider internet route.

What Packet Loss Means and Why It Matters

Packet loss occurs when pieces of data fail to reach their destination. A small amount of loss can cause big problems, especially for real-time applications. Unlike downloading a file, where missing pieces can be requested again, live audio, video, and gaming traffic are time-sensitive. If packets arrive late or never arrive, you experience glitches.

Common symptoms of packet loss include:

• Robotic or choppy audio during voice calls
• Video freezing or dropping to low quality
• Online games lagging, rubber banding, or disconnecting
• Web pages loading halfway before stalling
• Remote desktop sessions feeling jerky or unresponsive

Even 1% to 2% packet loss can be noticeable in voice and video calls. Higher loss can make a connection nearly unusable, even if a speed test says your download rate is excellent.

How to Test for Packet Loss

A basic ping test can show packet loss, but a longer test gives better evidence. On Windows, you can send a specific number of pings:

ping 8.8.8.8 -n 100

On macOS or Linux, use:

ping -c 100 8.8.8.8

This sends 100 packets and reports how many were lost. If you see 0% loss, that is a good sign. If you see repeated loss, especially when testing multiple reliable destinations, you likely have a real connection issue.

It is important to test more than one destination. A single website or server may ignore or limit ping traffic. Try testing a mix of reliable targets, such as your router, your internet provider’s gateway if known, and public DNS servers.

Traceroute: Mapping the Journey of Your Connection

While ping tells you whether a destination responds, traceroute shows the route your traffic takes to get there. Internet traffic rarely travels directly from your device to a website. Instead, it passes through multiple routers, also called hops. Traceroute lists those hops and shows how long each one takes to respond.

This is useful because slow internet problems often begin at a specific point along the path. Your home network may be fine, but traffic could slow down at your provider’s network, a regional exchange, or a distant server.

How to Run Traceroute

On Windows, the command is:

tracert google.com

On macOS or Linux, use:

traceroute google.com

The output will show a numbered list of hops. Each line usually includes response times and the address of a router along the route.

How to Interpret Traceroute Results

Traceroute can look intimidating at first, but you only need to focus on a few patterns:

• Low times at the first hop: Your device is communicating well with your router.
• High latency starting at hop one: Your local network may be the problem.
• High latency beginning after several hops: The delay may be outside your home network.
• Stars or timeouts: Some routers do not respond to traceroute requests, which is not always a problem.
• Latency that rises and stays high: This may indicate where the route becomes slow.

A common mistake is assuming that any timeout in traceroute means failure. Many routers are configured to ignore diagnostic requests while still forwarding normal traffic. What matters more is whether later hops continue responding and whether the final destination is reachable.

For example, if hop 5 shows a timeout but hops 6 through 12 respond normally, hop 5 is probably just ignoring traceroute. But if latency jumps from 20 ms to 300 ms at hop 6 and stays high for every hop after that, the problem may begin around that part of the route.

Combining Ping, Traceroute, and Packet Loss Tests

The real power comes from using these tools together. Each one answers a different question:

• Ping: Is the destination reachable, and how quickly does it respond?
• Packet loss testing: Is data being lost along the way?
• Traceroute: Where does the traffic go, and where do delays appear?

Here is a practical troubleshooting sequence:

1. Ping your router. If this is slow or lossy, focus on Wi-Fi, cables, or local equipment.
2. Ping a public IP address. If your router is fine but this is poor, investigate your modem or internet provider.
3. Ping a domain name. If IP addresses work but names fail, check DNS settings.
4. Run a longer packet loss test. Use 100 or more pings to identify intermittent problems.
5. Run traceroute. Look for where latency increases and whether the final destination is reached.
6. Repeat at different times. Problems that appear only in the evening may indicate network congestion.

This step-by-step approach helps you avoid jumping to conclusions. If only one website is slow, the issue may be with that website. If every destination is slow after the first hop outside your home, your provider may need to investigate. If your router itself responds poorly, replacing your internet plan will not fix the underlying Wi-Fi issue.

Common Causes These Tests Can Reveal

These tools cannot fix the problem by themselves, but they can point you in the right direction. Common causes include:

• Weak Wi-Fi signal: High ping to your router often suggests poor wireless quality.
• Wi-Fi interference: Neighboring networks, microwaves, and thick walls can disrupt signals.
• Overloaded router: Older routers may struggle with many devices or heavy traffic.
• Bad Ethernet cables: Damaged cables can cause intermittent loss and speed drops.
• ISP congestion: Slowdowns during peak hours may happen beyond your home network.
• DNS problems: Websites may seem slow to start loading if name resolution is delayed.
• Remote server issues: The website or game server itself may be overloaded or far away.

Tips for Getting More Accurate Results

Network conditions change constantly, so a single test is only a snapshot. For better results, run tests more than once and compare patterns.

• Test over Ethernet if possible: This removes Wi-Fi as a variable.
• Close heavy applications: Cloud backups, downloads, and streaming can distort results.
• Test multiple destinations: Do not rely on one server.
• Record the time of day: Evening congestion can be very different from morning performance.
• Save screenshots or command output: Evidence helps when contacting support.

If you contact your internet provider, saying “my internet is slow” may not get you far. Saying “I have 5% packet loss to multiple public IP addresses over Ethernet, but no loss to my router” is much more useful. It shows that you have narrowed the issue and can help support teams escalate the problem faster.

When to Restart, Replace, or Call for Help

If tests show problems inside your local network, start with simple fixes. Restart your modem and router, check cable connections, update router firmware, and try moving closer to the Wi-Fi access point. If Ethernet works well but Wi-Fi does not, consider changing Wi-Fi channels, repositioning the router, or upgrading to a mesh system.

If tests show clean local results but consistent loss or high latency beyond your router, contact your internet provider. Provide your test results, including ping statistics and traceroute output. If the problem affects only one service, such as a specific game or streaming platform, the issue may be with that service’s network or the route to it.

The key is to diagnose methodically. Ping tells you how responsive the connection is. Packet loss tests tell you whether the connection is reliable. Traceroute shows where the journey slows down. Once you understand those three views, slow internet stops being a vague frustration and becomes a problem you can investigate with confidence.