How to Run a Ping Test in CMD (Command Prompt)
The ping command is built into every version of Windows. This guide shows you exactly how to open CMD, run basic and continuous ping tests, and read the results — plus an online ping test you can use right now without a command line.
Ping Test - Enter Target
Test network latency and connection quality
Step 1: Open Command Prompt
- Press Win + R to open the Run dialog.
- Type cmd and press Enter.
- A black terminal window opens. You are ready to run ping commands.
You can also click the Start menu, type cmd or Command Prompt in the search box, and press Enter. Administrator rights are not required for ping.
Step 2: Run a Basic Ping Test
Type ping followed by a hostname or IP address and press Enter:
ping google.com
Windows sends 4 ICMP echo requests and prints something like this:
Pinging google.com [142.250.72.206] with 32 bytes of data:
Reply from 142.250.72.206: bytes=32 time=14ms TTL=117
Reply from 142.250.72.206: bytes=32 time=13ms TTL=117
Reply from 142.250.72.206: bytes=32 time=15ms TTL=117
Reply from 142.250.72.206: bytes=32 time=13ms TTL=117
Ping statistics for 142.250.72.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 15ms, Average = 13msThe time value is the round-trip latency of each packet. The summary at the bottom shows packet loss and the minimum, maximum and average round-trip time.
Step 3: Useful Ping Options
The basic command sends only 4 packets. These flags make the test more useful:
ping -t google.com :: continuous ping, stop with Ctrl + C ping -n 20 google.com :: send exactly 20 packets ping -l 1472 google.com :: send larger 1472-byte packets ping -4 google.com :: force IPv4 ping -6 google.com :: force IPv6
- -t keeps pinging until you stop it — best for watching stability over minutes. Press Ctrl + Break to print statistics without stopping.
- -n 20 sends more packets, which gives a more reliable average and reveals intermittent packet loss.
- -l 1472 tests with realistic packet sizes and can expose MTU or fragmentation problems.
Step 4: Read the Results
Focus on three numbers: average time (overall latency), loss percentage (reliability), and the gap between minimum and maximum (stability).
- Under 20 ms average: excellent, typical for nearby servers.
- 20–60 ms: good, fine for gaming and video calls.
- 60–100 ms: acceptable, slight lag in fast-paced games.
- Over 100 ms or any loss above 0%: worth investigating.
If the average is fine but the maximum is far higher, your connection has jitter. Use the jitter test to measure it properly.
Common Errors and Fixes
- Request timed out — the target blocks ICMP or is unreachable. Ping 8.8.8.8 first: if that works, the problem is the target, not your network.
- Ping request could not find host — the hostname cannot be resolved. Check the spelling, then try an IP address directly. If IPs work but names do not, your DNS is misconfigured.
- General failure — usually a local network stack problem. Reconnect to the network, restart the router, or reset TCP/IP with netsh int ip reset and reboot.
- Destination host unreachable — your PC has no route to the target. Check that you are connected to the network and that the gateway is up.
Ping Without a Command Line
If you prefer not to type commands — or you are on a phone, tablet, or a locked-down computer — use the online tool at the top of this page. It sends real ICMP pings from our servers to any hostname or IP you enter. To test from many countries at once, use the global ping test. For Android-specific instructions, see how to ping test on Android.