Using Windows CMD to Check Ping

Windows Command Prompt gives you a built-in ping tool that measures the round-trip time between your PC and any server, with no extra software required. This guide covers opening CMD, running a basic test, reading every field the output gives you, and using the command's flags for real diagnostic work — plus how to trace exactly where latency is coming from with tracert and pathping.

Opening Command Prompt or PowerShell

There are three quick ways to get a command line on Windows 10 or 11:

Press Windows + R, type cmd, and press Enter.
Right-click the Start button and choose Terminal or Command Prompt from the menu.
Open the Start menu, type Windows Terminal, and launch it — this is the modern host for both CMD and PowerShell tabs.

The ping command itself works identically in CMD, PowerShell, and Windows Terminal, so use whichever you have open.

Running Your First Ping Test

Type ping google.com and press Enter. By default, Windows sends 4 packets and prints a line for each one, followed by a summary. A typical result looks like this:

Reply from 142.250.premise.com: bytes=32 time=18ms TTL=118

Reading it left to right: the packet reached the target and got a reply; the reply carried 32 bytes of data (Windows' default payload size); the round trip took 18ms; and the TTL (Time To Live) is the number of network hops the packet had left when it arrived — it starts at a fixed value (commonly 64, 128, or 255 depending on the remote system) and drops by one at every router it crosses, so a lower TTL hints at a longer path.

Reading the Statistics Block

After the four replies, ping prints a summary block. This is the part worth paying attention to:

Packets: Sent, Received, Lost — how many requests got answered. Any loss here is worth investigating; even 1 lost out of 4 is a signal to run a longer test.
Minimum — your best-case latency, useful as a baseline for "how good could this connection be."
Maximum — your worst-case latency during the test. A big gap between minimum and maximum means the connection is inconsistent, not just slow.
Average — the number most people quote as "my ping," but it can hide spikes if only a couple of replies were slow.

Ping Command Flags

The default 4-packet test is a quick check, not a diagnosis. These flags turn ping into a real troubleshooting tool:

Flag	What It Does	Example
-n	Sets how many packets to send instead of the default 4	ping -n 20 8.8.8.8
-t	Pings continuously until you stop it with Ctrl + C	ping -t 8.8.8.8
-l	Sets the packet size in bytes, useful for stress-testing a link	ping -l 1200 8.8.8.8
-w	Sets how many milliseconds to wait for each reply before it counts as timed out	ping -w 2000 8.8.8.8
-4 / -6	Forces IPv4 or IPv6, useful when a hostname resolves to both	ping -4 google.com

Practical Recipes for Gamers

A handful of specific commands cover most real troubleshooting situations:

Watch your router while you game. Open a second window and run ping -t 192.168.1.1 (use your router's actual address) while playing. If spikes in this window line up with the moments your game stutters, the problem is inside your home network, not your ISP or the game server.
Ping a game's DNS or matchmaking endpoint. Many games publish their regional server hostnames, or you can ping common public DNS resolvers like ping -n 20 1.1.1.1 or ping -n 20 8.8.8.8 as a stable, always-available reference point for comparison.
Trace the full route with tracert. Running tracert 8.8.8.8 lists every router (hop) your packet passes through on the way to the destination, along with the latency to each one. It is the fastest way to see roughly how far your traffic travels before it even reaches the game's network.
Find where latency actually appears with pathping. pathping 8.8.8.8 combines tracert with an extended ping test at every hop, so it can show you which specific router along the route is adding delay or dropping packets, rather than just delay at the final destination. It takes a few minutes to complete but gives far more actionable data than a single ping.

Interpreting Your Results

The spread between your average and maximum ping tells you about consistency, often called jitter. If four replies come back at 20, 21, 19, and 22ms, your connection is stable and predictable — ideal for fast-paced games. If they come back at 20, 21, 95, and 24ms, the average might still look acceptable, but that one 95ms reply is exactly the kind of spike that causes rubber-banding and missed shots in a real match. Run a longer test with ping -n 50 rather than judging a connection from four packets.

You will also occasionally see Request timed out instead of a reply. This means no response came back within the wait time, which usually indicates a dropped packet somewhere on the path — inside your home network, at your ISP, or at the destination itself. An occasional timeout during a long continuous ping is normal; frequent timeouts point to a real packet loss problem worth tracing with pathping.

The Limits of ICMP Ping

The ping command measures ICMP echo requests, a lightweight diagnostic protocol — not the actual game traffic your console or PC sends during a match, which typically uses UDP on different ports and can be prioritized differently by routers and ISPs along the way. A clean CMD ping does not guarantee a clean in-game connection, and some networks even deprioritize ICMP traffic, making ping look worse (or occasionally better) than what you will actually experience in a game.

For a quick, no-install way to check your real-world latency to nearby regional endpoints from any device, run our online ping test directly in your browser. If you also use a Mac, our guide to the ping command on Mac Terminal covers the same fundamentals with macOS-specific syntax. And if your CMD tests show occasional large spikes rather than a steady problem, see our dedicated guide on how to fix ping spikes for the most common causes and fixes.