How to Diagnose Your Internet Connection with Ping

Ping is one of the oldest and still most useful tools for figuring out whether a connection problem is real, and roughly where it is happening.

Ping works by sending ICMP echo requests

The ping command sends a small ICMP "echo request" packet to a target address and measures how long it takes to receive an "echo reply" back β€” that round-trip time is the number ping reports.

Running it takes one line in a terminal

On Windows, open Command Prompt and type "ping" followed by a domain or IP (e.g. ping google.com). On Mac, open Terminal and use the same command β€” Mac's ping runs continuously by default until stopped with Ctrl+C, while Windows sends a fixed number of requests automatically.

Response time (ms) reflects distance and congestion

Lower is better. Under about 20ms is excellent (typical for a nearby server), 20-100ms is generally fine for browsing and video calls, and consistently over 150ms often causes noticeable lag in real-time applications like gaming or video calls.

Packet loss means some replies never arrived at all

A ping summary reporting anything above 0% packet loss means some requests went unanswered β€” occasional loss can be normal, but sustained loss above a few percent usually points to a real connectivity problem, such as Wi-Fi interference or an overloaded network link.

TTL (Time to Live) hints at the path and often the OS

Each reply includes a TTL value that decreases by one at every router it passes through. Comparing the received TTL to common starting values (64, 128, 255) gives a rough idea of how many hops away the target is, and sometimes hints at what operating system it's running.

Ping tells you if a path works; traceroute shows the path itself

Ping only reports whether a destination responded and how long it took β€” it does not show the route. When ping reveals a problem, traceroute (or tracert on Windows) is the natural next step to see which specific hop along the way is failing.

What a ping test can and cannot tell you

Ping is excellent for a first, quick diagnosis: is the destination reachable at all, and roughly how far away does it feel. It cannot tell you why a connection is slow β€” that could be your Wi-Fi signal, your ISP, network congestion, or a problem on the destination server's end, all of which require further tools to isolate.

Some servers deliberately ignore ping

A "timeout" or "request timed out" result does not always mean a server is offline. Many servers and firewalls are configured to ignore ICMP echo requests entirely for security reasons, so a failed ping to a well-known, working website is not unusual and does not necessarily indicate a real problem.

Frequently Asked Questions

Is a high ping the same thing as slow download speed?

No, they measure different things. Ping measures round-trip delay (latency), while download speed measures throughput (how much data arrives per second). A connection can have low latency but low bandwidth, or the reverse.

Why does my ping to the same website vary each time I test it?

Network conditions change constantly β€” background traffic on your own network, Wi-Fi interference, and congestion at any point along the route can all cause the response time to fluctuate between individual pings.