Ping is delay, jitter is changing delay, and packet loss is data that never arrives. Stable high ping makes every action feel late. High jitter causes uneven bursts, stutters, and sudden latency spikes. Packet loss can produce missing updates, rubber-banding, or brief freezes. Check all three before changing router settings because the same symptom can come from a different part of the connection.
Packet loss vs ping vs jitter at a glance
| Metric | What it measures | Typical gaming symptom | Useful first check |
|---|---|---|---|
| Ping | How long a round trip to the destination takes | Inputs, hit registration, and updates always feel late | Compare a nearby game region with a distant one |
| Jitter | How much packet delay changes over time | Performance is smooth, then suddenly choppy | Watch minimum, maximum, and spikes, not only the average |
| Packet loss | The share of sent packets that do not reach the destination | Rubber-banding, missing updates, freezes, or warning icons | Compare a router test with an internet test |
These measurements are related, but they are not interchangeable. Congestion can raise ping, increase jitter, and eventually drop packets. WiFi interference may create jitter and loss while the basic internet speed still looks normal. A distant server may give you high but steady ping without any packet loss.
What ping tells you
People often use ping and latency as if they mean exactly the same thing. In everyday gaming conversations, that is usually close enough. Technically, the Windows ping command sends ICMP echo requests and reports the round-trip time for the replies. A game’s latency display may use its own traffic and calculation method, so its number does not have to match a Command Prompt test.
High ping means information takes longer to travel between you and the server. The delay can come from physical distance, the route selected by your ISP, congested links, a busy home connection, or the game server itself. When the ping is high but steady, movement and hit registration tend to feel consistently delayed rather than randomly broken.
There is no single good-ping cutoff for every game. A tactical shooter, a turn-based game, and a cloud gaming service do not have the same timing demands. The server region and the game’s own networking also matter. For diagnosis, compare the connection with its usual baseline and look for sudden changes.
What jitter tells you
Jitter is the everyday name for variation in packet delay. The IETF uses the more precise term IP packet delay variation. If one update takes 20 ms, the next takes 22 ms, and the next takes 95 ms, the average alone hides the uneven delivery that you feel.
This is why a connection with a low average ping can still play badly. A game can often account for a small, predictable delay. It has a harder time when updates arrive in irregular clumps. High jitter may appear as short stalls, voice chat that breaks up, or a latency graph that repeatedly spikes and drops.
Jitter often points to changing queue conditions or an unstable local link. Common causes include a saturated upload, WiFi interference, weak signal, network roaming, background downloads, or another device sending bursts of traffic.
What packet loss tells you
Packet loss means a sent packet did not reach its destination within the measurement rules. What happens next depends on the application and protocol. Some data can be retransmitted. In a fast-moving game, a late update may already be less useful than the newer state that follows it.
Loss can happen on your PC, Ethernet cable, WiFi link, router, modem or ONT, ISP network, the route to the server, or the server side. It can also occur on a fast connection. Download speed describes capacity, not whether every time-sensitive packet arrives reliably.
One important caution: a router that does not answer every diagnostic ping is not automatically dropping the traffic it forwards. Microsoft notes that an intermediate router can show loss for packets addressed to itself while still forwarding later traffic normally. Treat loss at a hop as meaningful when it begins there and continues through the final destination.
Match the symptom to the likely metric
| What you notice | First suspect | Why |
|---|---|---|
| Every action responds late, but the delay is consistent | High ping | The round trip is slow but stable |
| The game alternates between smooth and choppy | Jitter | Packet timing changes from moment to moment |
| Your character snaps backward or remote players teleport | Packet loss or severe jitter | The client is missing timely state updates |
| The issue starts when someone uploads files or joins a video call | Queueing and congestion | Competing traffic raises delay and may cause loss |
| Only one game or one server region is affected | Server or route issue | Your local network may be healthy while that path is not |
| The image stutters but network stats stay clean | PC performance | Frame-time problems can resemble network lag |
A symptom is a clue, not proof. Rubber-banding is often associated with loss, but large jitter spikes can produce a similar correction. Use the next test sequence to separate the causes.
How to test ping, jitter, and packet loss in the right order
1. Turn on the game’s network statistics
Start with the game’s own latency, loss, and network graph if it provides them. Those measurements use the actual session and destination. Note the server region, time, connection type, and what was happening on the home network. A single number taken after the problem ends is less useful than the graph during the event.
2. Test the link to your router
On Windows, open Command Prompt and run ipconfig. Find the Default Gateway for the active adapter, then send a longer set of pings to that address:
ping -n 50 <your-router-IP>This test stays inside your home network. If it shows repeated timeouts or large swings, investigate the PC-to-router link first. Try Ethernet, move closer to the router, stop roaming between access points, and check for a weak or congested WiFi channel. Router placement can make a large difference, especially when walls, cabinets, and appliances sit between the client and access point. See our guide to placing wireless equipment for better reception.
3. Test beyond the router
Next, test a reliable public destination. This example sends 50 requests to Cloudflare’s public resolver:
ping -n 50 1.1.1.1Compare the minimum, maximum, average, and loss with the router test. A clean router test followed by unstable internet results moves the investigation toward the modem, ONT, ISP, or upstream route. Keep in mind that some destinations limit or ignore ICMP replies, so one failed ping target is not enough to prove a connection problem.
4. Repeat while the connection is busy
Run the tests once while the network is idle, then again while an upload, cloud backup, or large download is active. If latency and jitter rise sharply only under load, queued traffic is the likely trigger. Pause the traffic and test any QoS or smart queue feature your router offers. Change one setting at a time so you can tell whether it helped.
5. Use PathPing when the destination also loses packets
Windows PathPing traces the route, then sends repeated probes to build statistics for the routers and links along it:
pathping /n 1.1.1.1It takes longer than a basic ping test. Focus on loss that continues into the final destination. An intermediate hop that reports poor replies while every later hop remains clean is usually not the failure point.
How to interpret the results
| Router test | Internet test | Most useful next step |
|---|---|---|
| Unstable or lossy | Unstable or lossy | Fix the local WiFi, cable, adapter, or router link first |
| Clean | Unstable or lossy | Check the modem or ONT, ISP status, and upstream route |
| Clean | Clean | Test the actual game region and check the game’s status |
| Clean when idle | Bad only under load | Reduce competing traffic or tune QoS and queue management |
| WiFi is unstable | Ethernet is clean | Work on signal, channel use, placement, or access point coverage |
Fix the layer that is failing
If the router test is bad
- Compare WiFi with a direct Ethernet connection.
- Move closer to the router and avoid placing it behind a TV, inside a cabinet, or beside a large metal object.
- Switch bands if the current one is weak or crowded. A nearby 5 GHz or 6 GHz link can be cleaner, while 2.4 GHz reaches farther.
- Update the network adapter driver and router firmware using the device maker’s instructions.
- Swap the Ethernet cable and router port if the wired test loses packets.
If the connection fails only under load
- Pause cloud backups, game downloads, livestream uploads, and large file transfers.
- Test the router’s QoS or smart queue option if available.
- Set realistic bandwidth values if the feature asks for them. A limit slightly below the connection’s actual capacity may keep the queue under control.
- Retest in the same game region with the same background traffic.
If only one game is affected
Check the publisher’s service status and try another nearby server region. A DNS change rarely improves live-match latency once the connection is established, and a VPN can either improve or worsen the route. Do not treat either as a guaranteed fix.
If the problem is specifically Valorant packet loss, use our Valorant packet loss troubleshooting guide after completing the local and internet tests above.
Frequently asked questions
Is stable high ping better than low ping with high jitter?
Often, yes. A stable delay is easier for both the player and the game to handle than a connection that swings unpredictably. Low, stable ping is still the preferred result.
Can I have packet loss with a good speed test?
Yes. A speed test mainly measures how much data the connection can move during the test. Packet loss and jitter measure reliability and timing, so a fast connection can still behave poorly in a real-time game.
Does zero packet loss in Command Prompt prove the game connection is fine?
No. The test destination, protocol, route, and time are different. A clean result is useful evidence that the broader connection works, but the game’s own network statistics remain more relevant to that session.
Will a gaming router automatically fix jitter?
No. Better queue management or stronger WiFi may help when the router is the bottleneck. It cannot shorten physical distance to a server or repair an ISP routing problem. Test before buying new hardware.
