How do I check server latency with ping from Windows?
Ping sends ICMP echo probes and reports replies and round-trip time. It provides a limited network signal, not a full server or website health test. Some networks intentionally block or rate-limit these replies.
Instructions
1. Send a small fixed number of probes
Use the server address you are authorised to test.
ping -n 4 203.0.113.10-n limits the test to four requests. This Windows option differs from common Linux ping syntax.
2. Read the summary in context
Review sent and received counts and minimum, maximum and average latency. A brief four-packet sample is useful for an immediate check, but it cannot establish a long-term availability percentage or guarantee that no intermittent loss exists.
3. Check the actual service
If the problem concerns SSH, test its TCP port as well.
Test-NetConnection 203.0.113.10 -Port 22A successful service-port check can coexist with missing ping replies. Use the actual configured port.
Check the result
- The test uses the expected resolved address.
- Results are compared with the relevant service test rather than interpreted alone.
Troubleshooting
- Request timed out
- This may be ICMP filtering, loss or lack of reachability. Check the real service before declaring an outage.
- Latency spikes once
- Repeat a bounded sample and correlate timestamps with workload or network events before attributing a cause.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.