How to Read Ping Results (Time, TTL, Packet Loss & Errors Explained)

A ping test is the fastest way to check if a device is reachable. But the raw output can look like a wall of numbers. This guide explains how to read ping results so each line makes sense. You will learn to spot latency, packet loss, and dead hosts at a glance.

Ping output looks intimidating at first. Once you know what each field means, it becomes a fast diagnostic. The same skills apply on Windows, macOS, and Linux. The wording changes a little, but the numbers mean the same thing.

What Ping Actually Measures

Ping sends a small ICMP echo request to a target and waits for an echo reply. The round trip is timed in milliseconds. That single number tells you whether a host is reachable and how quickly it answers.

Ping is a small network test built into every operating system. It sends a packet called an ICMP echo request. The target replies with an ICMP echo reply. Ping measures the time between sending and receiving that reply.

ICMP is the messaging layer of the internet protocol suite. Devices use it to report status and errors. Ping rides on top of ICMP to ask a simple question. That question is: are you there, and how fast can you answer?

Running a Ping on Any System

You can run ping from a terminal on any platform. Open Command Prompt or PowerShell on Windows. Open Terminal on macOS or Linux. Then type the command followed by an address.

ping google.com

By default, Windows sends four requests and then stops. On macOS and Linux, ping keeps running until you stop it. The basic command is the same across systems. Only the options differ a little.

Here is a typical successful result from Windows:

Pinging google.com [142.250.80.46] with 32 bytes of data:
Reply from 142.250.80.46: bytes=32 time=14ms TTL=117
Reply from 142.250.80.46: bytes=32 time=15ms TTL=117
Reply from 142.250.80.46: bytes=32 time=13ms TTL=117
Reply from 142.250.80.46: bytes=32 time=16ms TTL=117

Ping statistics for 142.250.80.46:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 16ms, Average = 14ms

How to Read Ping Results, One Line at a Time

Each reply line shows three useful fields: the bytes sent, the time in milliseconds, and the TTL value. Learning how to read ping results means reading those three numbers together. The time field is the one you watch most often.

Each successful reply packs three numbers worth reading. The bytes field shows the size of the packet sent. The time field shows the round-trip latency in milliseconds. The TTL field shows the remaining time-to-live value.

Reply from 142.250.80.46: bytes=32 time=14ms TTL=117

Field	Meaning
bytes=32	Size of the test packet, in bytes.
time=14ms	Round-trip latency for this reply.
TTL=117	Time-to-live value left on arrival.

The time value is the one that matters most day to day. It tells you how long the round trip took. Lower numbers mean a faster, snappier connection. A steady time across replies signals a stable link.

TTL is short for time-to-live. It starts at a set number and drops by one at each router hop. The value you see hints at how many hops the reply crossed. It also hints at the remote operating system.

What Counts as Normal Latency

Normal latency depends on distance and link type. A wired LAN often replies in under five milliseconds. Good broadband sits near ten to forty milliseconds. Anything above one hundred milliseconds starts to feel slow in real-time apps.

Normal ping times are not a single number. They depend on distance, link type, and load. A local device should answer almost instantly. A server across the world will always take longer.

Connection type	Typical round-trip time
Wired LAN	under 5 ms
Good broadband	10 to 40 ms
Mobile (4G or 5G)	30 to 80 ms
Cross-continent	80 to 150 ms
Satellite (geostationary)	500 ms or more

Use the table as a rough guide, not a hard rule. A satellite link can read 500 milliseconds and still be healthy. What matters most is consistency over time. A sudden jump above your normal range is the real signal.

Ping is one step in a larger process. Our network troubleshooting guide shows where each test fits. Start there if your whole connection is down, not just slow.

Reading Packet Loss and the Summary Stats

The summary line reports packets sent, received, and lost as a percentage. It also shows minimum, average, and maximum round-trip times. Zero percent loss is ideal. Even one or two percent loss can disrupt calls and video.

The summary appears after the replies finish. The first line counts packets sent, received, and lost. The loss percentage is the headline number here. Zero percent means every packet made the round trip.

Ping statistics for 142.250.80.46:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 16ms, Average = 14ms

The second block reports timing across the whole test. Minimum is your best round trip. Maximum is your worst. Average is the figure to watch over many pings.

Packet loss is often more telling than latency. A few lost packets can break a video call. Run a longer test if you suspect loss. A four-packet sample is too small to trust.

Request Timed Out vs Destination Host Unreachable

These two messages mean different things. Request Timed Out means no reply came back at all. Destination Host Unreachable is an actual reply from a router that has no path to the target. The second message gives you more to work with.

Request Timed Out

Request Timed Out means no reply arrived in time. Your packet left, but nothing came back. The cause could be a firewall dropping ICMP. It could also be a downed host or a broken route.

On macOS and Linux you may see silence instead. The line simply does not appear for that attempt. Both behaviors mean the same thing. No echo reply came back within the wait period.

Destination Host Unreachable

Destination Host Unreachable is different. It is an actual ICMP error reply. A router or your own machine sends it back. The message says there is no known path to the target.

This often points to a routing or gateway problem. Your device may lack a route to the network. A failed address lookup on the local subnet can also trigger it. Either way, you got useful feedback to act on.

Some failures start before ping even runs. If your address starts with 169.254, DHCP failed first. See our guide on the 169.254 APIPA address. A full Windows network reset can clear stale settings.

Running a Continuous Ping to Spot Patterns

A continuous ping reveals patterns a short test hides. It exposes drops that happen only every few seconds. Watch for loss that lines up with other activity on your network. Steady replies with occasional spikes usually point to congestion.

A single burst of four pings can miss an intermittent fault. A continuous ping runs until you stop it. It is the best way to catch drops that come and go. Watch it while you reproduce the problem.

Windows:        ping -t 8.8.8.8        (runs until you press Ctrl + C)
macOS / Linux:  ping 8.8.8.8           (runs until you press Ctrl + C)

On Windows, add the -t flag to ping without stopping. On macOS and Linux, plain ping already runs until you stop it. Press Control plus C to end the test. The summary then prints as usual.

Scan the stream for timeouts mixed among good replies. A drop every few seconds suggests interference or a failing cable. Loss that spikes during big downloads points to congestion. Note the timing of each gap.

What Ping Cannot Tell You

Ping confirms reachability and round-trip time, but little else. It cannot show the route packets take or which hop is slow. It cannot test a specific application port. For path problems, traceroute picks up where ping stops.

Ping answers one question well: can I reach this host, and how fast. It stops short of many other useful answers. It does not reveal the path your packets take. It cannot tell you which hop along the way is slow.

Ping also cannot test a specific service or port. A web server may answer ping but still refuse connections on port 443. For that you need a port or service test. Ping checks the host, not the application.

Name resolution is another blind spot. If pinging an IP works but a domain fails, DNS is the cause. Confirm name resolution with our DNS lookup tool. A common symptom is the DNS_PROBE_FINISHED_NO_INTERNET error in Chrome.

When the path itself is the mystery, traceroute is the next tool. Traceroute maps every router between you and the target. It shows where latency climbs or where packets stop. Ping tells you that something is wrong; traceroute helps show where.

Related Tools & Resources

Ping is one piece of a full diagnostic kit. Pair it with a DNS lookup when names fail but IP addresses work. Our free network tools run in the browser. Each tool shows output you can read with these same skills.

• All NetworkCheckr tools run in your browser with no install.
• Network troubleshooting guide walks through the full connectivity workflow.
• DNS lookup tool checks whether a name resolves when ping by name fails.
• Windows network reset commands clear stale network settings in minutes.
• 169.254 APIPA address explained covers what a self-assigned IP means.

Frequently Asked Questions

These quick answers cover the questions people ask most about ping output. Use them to settle a reading fast. For a full walkthrough, work back through the sections above. Each answer stays short on purpose so you can scan it.

References

The sources below are primary and vendor-neutral where possible. They cover the ping command, the ICMP protocol behind it, and the original standard. Use them to verify any detail in this guide. Each link opens in a new tab.