How to Ping an IP Address (Windows, Mac, Linux)

ping is the oldest tool in the network troubleshooting kit — it sends a tiny "are you there?" message (an ICMP echo request) to an address and measures how long the reply takes. It answers two questions in one: can I reach this device, and how fast?

Running a ping

Windows: open Command Prompt and run:

ping 192.168.1.1

Windows sends 4 pings by default; add -t to ping continuously (Ctrl+C to stop).

Mac / Linux: open Terminal and run the same command — it pings continuously by default; press Ctrl+C to stop and see the summary. You can ping domains too: ping google.com (which also confirms DNS is working).

Reading the output

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.31 ms

• time — round-trip latency. Under 5 ms: same network. 10–50 ms: normal internet. 100 ms+: distant server or congestion.
• ttl — hops remaining; see what TTL means.
• icmp_seq — sequence number; gaps mean lost packets.

The summary's packet loss figure is the key health metric — anything above 0% on a stable link deserves investigation, and 5%+ makes calls and games miserable.

A practical troubleshooting ladder

1. ping 127.0.0.1 — tests your own network stack (loopback).
2. ping 192.168.1.1 — tests the link to your router.
3. ping 1.1.1.1 — tests your internet connection without DNS.
4. ping google.com — tests DNS on top.

Where the ladder breaks tells you where the problem lives: device, router, ISP, or DNS.

When ping fails but the target is fine

No reply doesn't always mean offline — many hosts and firewalls simply drop ICMP. Plenty of major websites won't answer pings while serving traffic perfectly well. Pinging your own public IP (find it here) from outside typically fails too, because home routers ignore unsolicited probes — that's NAT and the firewall doing their job. For path-by-path diagnosis, step up to traceroute.

Frequently asked questions