You can pay for gigabit fiber with lightning-fast download speeds and still experience unbearable lag in online multiplayer games. That is because download speed (bandwidth) only measures how much data can pass through your pipe in one second. Multiplayer gaming requires very little bandwidth—usually less than 1 Mbps. What games demand above all else is low latency and packet consistency.

When game packets arrive late, out of order, or get dropped entirely, your character rubberbands across the map, shots fail to register, and actions feel unresponsive. While most games feature an in-game latency counter, those numbers are easily skewed by client render delays and server tick rates. To check network ping on Windows accurately and identify where packets are actually getting delayed or lost, you must test the network connection directly using built-in Windows command-line tools.

The Three Pillars of Network Health: Ping, Jitter, and Packet Loss

Before typing commands into your terminal, it is essential to understand what you are measuring:

  1. Ping (Latency): The time, measured in milliseconds (ms), that it takes for a data packet to travel from your computer to a remote server and return (Round-Trip Time, or RTT). Under 40ms is optimal; 40ms–80ms is standard; over 120ms causes perceptible delays.
  2. Jitter: The variance in ping over time. If your ping reads 30ms on one packet and suddenly spikes to 180ms on the next, that 150ms swing is jitter. High jitter makes smooth movement impossible.
  3. Packet Loss: The percentage of data packets that never reach their destination. Even a 1% to 2% packet loss rate ruins competitive play because game engines are forced to resend critical state updates, causing severe freezes and rubberbanding.

If your frame rate is consistently smooth but your character teleports backward every few seconds, review our dedicated guide on how to reduce high ping in Roblox and online games to check local Wi-Fi interference and router settings.

Network Hop Diagnostic Reference Matrix

A data packet rarely travels directly from your PC to a game server in one jump. It navigates a chain of intermediate routing hardware called hops. Identifying which hop introduces latency tells you who is responsible for fixing it.

Hop Number & LocationTypical LatencyNormal StateWarning SignsResponsible Entity
Hop 1: Local Router / Gateway< 1 ms (Ethernet) / < 4 ms (Wi-Fi)0% packet lossSpikes > 15 ms, packet dropsYour home router, cable, or local Wi-Fi
Hop 2–3: ISP Neighborhood Node5 ms – 18 msStable, low varianceSpikes > 50 ms, frequent timeoutsYour neighborhood fiber/coax line or modem
Hop 4–7: ISP Core / Regional Transit15 ms – 40 msGradual increase by distanceSudden 80ms jump at a specific IPYour ISP's routing infrastructure
Hop 8+: Tier-1 Backbone & Game Host30 ms – 90 msMatches geographic distance100% loss at end (ICMP blocked) or latency surgeGame server hosting provider (AWS, Azure, etc.)

1. Continuous Ping Testing with ping -t

The standard ping command sends only 4 ICMP echo requests and terminates. Four packets cannot reveal intermittent lag spikes, packet drops that occur every thirty seconds, or bufferbloat. Running a continuous ping test solves this.

Step-by-Step Instructions

  1. Press Windows Key + R, type cmd, and press Enter to open Command Prompt (or launch Windows Terminal).
  2. Choose a reliable, ultra-fast DNS resolver to test baseline internet stability:
    • Cloudflare DNS: 1.1.1.1
    • Google DNS: 8.8.8.8
  3. Enter the following command: 
    ping 1.1.1.1 -t
  4. Let the test run for at least 60 seconds while you observe the output. Each line shows the packet size, the round-trip time, and the Time-to-Live (TTL).
  5. Press Ctrl + C on your keyboard to stop the test and view the summary statistics.
Ping statistics for 1.1.1.1:
    Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 17ms, Average = 15ms

What the Results Mean

  • Healthy Connection: Packets show 0% loss, and the difference between Minimum and Maximum is less than 5ms to 10ms.
  • Jitter Problem: If your minimum is 15ms but your maximum spikes to 140ms or 220ms, your line suffers from bufferbloat, background downloads, or wireless interference.
  • Packet Loss: Lines displaying Request timed out indicate dropped packets. If Lost is greater than 0, packets are actively disappearing along the route.

If your ping spikes only when someone else in the house streams 4K video or when background programs initiate updates, follow our guide on how to check which programs use your internet on Windows to track down the responsible process.

2. Pinpoint the Exact Bottleneck with tracert

While ping -t tells you that you have a latency issue, tracert (Trace Route) tells you where the issue is located along the path.

tracert sends packets with increasing TTL values to identify every intermediate router between your computer and the target address.

Step-by-Step Instructions

  1. In Command Prompt, run: 
    tracert 1.1.1.1
  2. The command sends three probes to each consecutive hop along the route:
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     6 ms     8 ms  10.45.0.1
  3    12 ms    11 ms    13 ms  172.16.200.1
  4    15 ms    14 ms    16 ms  1.1.1.1

Trace complete.

How to Read the Trace

  • Hop 1 is your local router (usually 192.168.1.1 or 192.168.0.1). If Hop 1 shows high latency (e.g., 45 ms) or asterisks (* * *), the problem is inside your house—either bad Wi-Fi signal, a degraded Ethernet cable, or an overloaded local router.
  • Hop 2 is your ISP's neighborhood gateway. If Hop 1 is <1 ms but Hop 2 immediately surges to 90 ms or shows packet drops, your ISP's physical drop line or local node has an issue.
  • Hop 3 and beyond are regional transit routers. If latency is clean until a specific external IP where it suddenly doubles, an intermediate carrier has an overloaded peering link.
  • Asterisks (* * *) at later hops: Seeing asterisks at intermediate or final hops does not always mean packet loss. Many enterprise routers deliberately deprioritize or block ICMP traceroute requests while forwarding standard UDP/TCP gaming packets normally. Only consider it a failure if the latency surge persists across all subsequent hops.

3. Deep Statistical Loss Analysis with pathping

The pathping utility combines the route-tracing ability of tracert with the statistical rigor of continuous ping. It traces the route, and then sends 100 ICMP packets to every single router along the chain over several minutes to calculate exact packet loss percentages at each hop.

Step-by-Step Instructions

  1. In Command Prompt, run: 
    pathping 1.1.1.1
  2. Wait 2 to 4 minutes while pathping maps the route and calculates statistics for each node.
  3. Review the final loss table:
Computing statistics for 75 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-GAMING [192.168.1.50]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2    8ms     0/ 100 =  0%     0/ 100 =  0%  10.45.0.1
                                2/ 100 =  2%   |
  3   42ms     2/ 100 =  2%     0/ 100 =  0%  core-router.isp.net

Under Source to Here, you can immediately spot where loss begins. If Hop 1 has 0% loss but Hop 3 introduces 2% loss that persists to the destination, you have indisputable proof of an upstream ISP routing defect that you can report to customer support.

4. Test Specific Game Ports with PowerShell Test-NetConnection

Standard ping uses the ICMP protocol, but online games communicate over UDP and TCP ports. Sometimes a firewall or ISP throttles gaming ports while letting ICMP ping pass through cleanly.

PowerShell's Test-NetConnection allows you to test network connectivity against specific port numbers.

Step-by-Step Instructions

  1. Right-click the Windows Start button and select Terminal or PowerShell.
  2. Run Test-NetConnection against a remote target and port (for example, testing HTTPS port 443 or custom game server ports): 
    Test-NetConnection -ComputerName 1.1.1.1 -Port 443
  3. PowerShell validates the DNS resolution, displays the interface used, executes an RTT measurement, and confirms whether the TCP socket handshake succeeded (TcpTestSucceeded : True).

Common Causes of High Ping and Packet Loss

Once your diagnostic tests isolate where the latency originates, apply the matching fix:

1. Wi-Fi Interference and Bufferbloat (Hop 1 Issues)

If Hop 1 shows latency above 2ms–5ms or exhibits intermittent dropouts, your local wireless connection is the root cause. Walls, 2.4 GHz interference from household electronics, and wireless channel congestion degrade gaming packets.

  • The Gold Standard Fix: Connect your PC directly to your router using a Cat-6 or Cat-5e Ethernet cable. Ethernet eliminates wireless jitter and guarantees <1 ms latency to your router.
  • If You Must Use Wi-Fi: Switch to the 5 GHz or 6 GHz Wi-Fi band, position your router closer, and use a Wi-Fi analyzer app to pick an uncluttered channel.

2. Local Bandwidth Saturation

When your internet upload capacity is saturated by background cloud backups (OneDrive, Google Drive, iCloud) or game launcher updates (Steam, Epic, Xbox), small game packets are forced to queue in your router's buffer.

  • Enable Quality of Service (QoS) in your router settings to prioritize gaming traffic over bulk downloads.
  • Pause heavy downloads before starting competitive matches.

3. ISP Node Congestion and Physical Line Faults (Hop 2+ Issues)

If Hop 1 is <1 ms on Ethernet, but Hop 2 consistently drops packets or spikes during evening peak hours (7 PM to 11 PM), your ISP's neighborhood node is oversubscribed or the physical cable connecting your home to the street has signal degradation.

  • Power cycle your modem and router (unplug for 60 seconds).
  • Inspect physical coaxial and fiber cables for tight bends, corrosion, or loose splitters.
  • Contact your ISP with your pathping log showing the exact hop where packet loss occurs.

Note that network lag is distinct from local input latency, where delays happen between your mouse and display rather than across the internet. If your ping is below 30ms but actions still feel delayed, review our technical guide on how to reduce input lag in PC games to optimize display refresh rates and polling frequencies.

The Practical Diagnostic Checklist

Whenever your connection feels unstable, run through this 2-minute diagnostic sequence:

  1. Open Command Prompt and run ping 1.1.1.1 -t for 60 seconds to check baseline jitter and packet loss.
  2. If packet loss is detected, run tracert 1.1.1.1 to see whether the delay starts on Hop 1 (your home network) or Hop 2+ (your ISP).
  3. If the delay starts on Hop 1, switch to Ethernet, reboot the router, and eliminate background bandwidth hogs.
  4. If the delay starts on Hop 2 or Hop 3, run pathping 1.1.1.1 to collect evidence of ISP node failure.

Using built-in Windows diagnostics gives you verifiable data rather than guesswork, allowing you to fix local bottlenecks immediately and hold your service provider accountable when the problem is on their end.