What is the difference between packet loss and latency?

Latency is the time it takes for a packet to travel to a destination and back. Packet loss is the percentage of packets that never arrive. High latency means delays; packet loss means missing data that must be retransmitted, causing stutters.

How do I fix high ping?

First, determine if the high ping is due to distance. Ping a server close to you; if it is low, the issue is distance. If ping is high even to local servers, check for bufferbloat by running a ping during a download. If ping jumps, enable QoS on your router or replace it.

Jitter is caused by variable delays in the network, often from router queues filling up during traffic bursts. Wi-Fi interference and ISP congestion also contribute. To reduce jitter, use a wired connection and ensure your router is not overloaded.

How can I tell if packet loss is on my network or my ISP's?

Ping your router's IP address. If you see loss there, the problem is local. If not, ping a public IP like 8.8.8.8. If loss appears there, the problem is beyond your router, likely with your ISP.

Is there a way to fix packet loss without calling my ISP?

If the loss is on your local network, replace Ethernet cables, move closer to the Wi-Fi router, or update the router's firmware. If loss persists on a wired connection, restart the router. If loss continues, it is likely ISP-side and you need to contact them.

Packet Loss vs Latency: Fix Lag | Think Like a Computer

When a connection feels slow or unresponsive, the usual word is “lag.” But lag is three different problems that require three different fixes. Packet loss, latency, and jitter each affect a connection in a distinct way, and each points to a different part of the network. This page explains what each one is, how to measure them separately, and which cases you can fix yourself versus which require the ISP or carrier to act.

The Three Problems

Problem	What it does	Typical cause	When it is NOT your fault
Latency (high ping)	Every round trip takes longer. Actions feel delayed but data arrives intact.	Long physical distance, satellite links, overloaded router, bufferbloat.	When the delay is caused by the physical distance to the server (e.g., playing on a server on another continent).
Packet loss	Some packets never arrive. Data must be retransmitted, causing stutters, teleporting, and dropped calls.	Faulty cable, Wi-Fi interference, overloaded switch, ISP congestion, failing hardware.	When loss happens on the ISP’s backbone or at a carrier peer, outside your local network.
Jitter	Delay varies from packet to packet. Audio and video break up even if average latency is fine.	Variable queueing on routers, Wi-Fi interference, competing traffic.	When the variation comes from the ISP’s routing or a congested upstream link.

Measuring Each Problem

Latency

Latency is the round-trip time for a packet to reach a destination and return. It is measured in milliseconds (ms). A ping of 20 ms is excellent; 100 ms is noticeable; 300 ms makes real-time games unplayable.

To measure latency, use the ping command. It sends a small packet and waits for a reply, reporting the time taken.

ping 8.8.8.8

The output shows a time in milliseconds for each reply. The average is a rough latency figure. Ping measures latency but does not tell you about jitter or loss in detail.

Packet Loss

Packet loss is the percentage of packets that never reach their destination. Even 1% loss can cause noticeable problems in real-time applications. To measure loss, ping with a count and look for “Request timed out” or “Destination host unreachable” messages.

ping -n 100 8.8.8.8

On Windows, the -n flag sets the number of pings. The summary at the end shows “Lost = X (Y% loss).” If you see loss here, the problem is somewhere between your computer and 8.8.8.8.

To narrow down where the loss occurs, ping your router’s IP address first (usually 192.168.1.1 or 192.168.0.1). If loss appears there, the problem is on your local network. If not, ping a public IP like 8.8.8.8. If loss appears there, the problem is beyond your router, likely with your ISP.

Jitter

Jitter is the variation in latency between packets. It is not directly shown by ping, but you can estimate it by looking at the range of times in the ping output. If some replies take 20 ms and others take 200 ms, jitter is high. A more precise measurement requires a tool like pathping or a dedicated jitter test.

pathping 8.8.8.8

pathping sends many packets to each hop along the route and reports loss and latency for each. The last column, “Jitter,” is the variation at each hop. This helps identify which router is introducing jitter.

What Causes Each Problem

High Ping Causes

High latency is often a physical distance issue. Light in fiber travels at about 200,000 km/s, so a round trip across the Atlantic adds about 60 ms. Satellite links add 500 ms or more. If the server is far away, nothing you do locally will reduce that.

But high ping can also be caused by your own router. If it is overloaded with too many connections or has a slow CPU, it adds delay to every packet. This is called “bufferbloat” when the router’s queue fills up. To test, run a ping while downloading a large file. If ping times jump, bufferbloat is present. Many routers allow you to enable Quality of Service (QoS) to prioritize traffic, but the most reliable fix is to replace a router that cannot handle your connection speed.

Packet Loss Causes

Packet loss on your local network is often a physical problem. A damaged Ethernet cable, a loose connector, or a failing network port can drop packets. Wi-Fi is prone to loss from interference, walls, or distance. To test, connect a computer directly to the router with a known-good Ethernet cable and run a ping test. If loss disappears, the problem is Wi-Fi or the cable.

If loss persists on a wired connection, the router or modem may be failing. Try restarting the router. If loss continues, the issue might be the ISP’s line. Contact them and report the loss percentage and the test results.

Jitter Causes

Jitter is usually caused by variable queueing delays. When a router has a burst of traffic, packets wait in line, and the wait time varies. This is common on shared connections, such as cable or DSL, where neighbors’ traffic affects your line. Wi-Fi also introduces jitter because radio interference changes the retry rate.

To reduce jitter on your network, use a wired connection and ensure your router is not overloaded. If jitter persists, the ISP’s network is likely the cause, and you may need to contact them.

What People Get Wrong

A common mistake is blaming high ping on packet loss. A user sees a high ping and assumes the connection is dropping packets, then runs a packet-loss test that shows 0% loss and concludes the network is fine. In reality, high ping with no loss means the network is working but the distance is long or a router is slow. The fix for that is different from fixing loss.

Another mistake is using a single ping test to judge the connection. A ping to a local server might show 5 ms, but a ping to a game server might show 150 ms. The connection is not “bad” in one case and “good” in the other; the distance is different. Always test against the actual server you care about.

People also confuse jitter with latency. A connection with 100 ms average latency but 5 ms jitter is stable; a connection with 50 ms average but 40 ms jitter is unstable. Real-time applications care more about jitter than average latency. If you see variable ping times, focus on jitter.

Which Cases You Cannot Fix

If packet loss or jitter appears only when pinging a public IP, and your local network tests are clean, the problem is beyond your router. It could be the ISP’s line, a congested carrier, or a problem at a data center. You cannot fix that from your side. Contact your ISP with the test results and ask them to check their equipment.

Similarly, if high ping is due to physical distance, no local change will help. You can only choose a server closer to you or accept the delay. Satellite internet will always have high latency; that is a physical limit.

What to Do When You Cannot Fix It

When the problem is outside your control, document the evidence. Run ping tests to several public IPs and save the output. Note the time of day, as congestion often peaks in the evening. Provide this to your ISP. If they refuse to act, you may need to escalate or switch providers.

Reinstall as a Last Resort

If you have exhausted network troubleshooting and suspect your operating system’s network stack is corrupted, you can reset it. This step does not delete personal files, but it resets all network adapters to their default settings, removes any custom IP configurations, and clears the DNS cache. You will need to reconfigure static IPs or VPN connections afterward.

To reset the network stack, open an elevated Command Prompt and run:

netsh int ip reset
netsh winsock reset

Restart the computer after running these commands. If the problem persists after a reset, the issue is almost certainly hardware or ISP-related, not software.

Summary of Tools

Command	What it measures	When to use
`ping`	Latency and packet loss to a single host	Quick check
`pathping`	Latency, loss, and jitter per hop	Identify the faulty router
`tracert`	Route and per-hop latency	See the path packets take
`iperf`	Throughput and jitter between two machines	Test local network performance

tracert shows the route and latency to each hop, but it does not measure loss well. iperf is a separate tool that must be run on two machines to test the link between them.

Conclusion

Packet loss, latency, and jitter are separate problems with separate causes. Measure each one independently, test locally first, and know when the problem is not yours to fix. A methodical approach will save time and avoid blaming the wrong component.

Packet Loss vs Latency: Diagnosing Lag