When your internet stops working — or works inconsistently — the first thing you need is a way to test where the connection is actually failing. Not a speed test. Not a browser refresh. You need a diagnostic tool that checks whether your device can even reach another device on the network.
That tool is the ping command, and it has been the starting point for internet troubleshooting on every version of Windows, including Windows 11. This article explains every switch, every output field, and a step-by-step method to isolate exactly where your connection breaks — using nothing but Command Prompt.
What the Ping Command Actually Does in Windows
The ping command sends a small test packet to a target — an IP address or a hostname — and waits for a response. If the response comes back, the connection between your computer and that target is working. If it does not come back, something along the path is broken.
It does not test speed in the way a bandwidth test does. It tests reachability and round-trip delay. That distinction matters because a connection can be slow without being broken, or broken without appearing slow.
If you want a deeper explanation of the protocol behind it, the guide on what is ping and how does it work covers the full mechanism.
What ICMP Echo Request Means in Plain Terms
Ping uses a protocol called ICMP — Internet Control Message Protocol. When you run a ping command, your computer sends an ICMP Echo Request packet to the target. If the target is reachable and not blocking ICMP, it sends back an ICMP Echo Reply.
Think of it as knocking on a door. The Echo Request is the knock. The Echo Reply is someone opening the door. If nobody opens it, either nobody is home, the door is locked, or the hallway between you and the door is blocked.
Windows 11 uses this exact mechanism every time you type ping followed by an address in Command Prompt.
Why Ping Is the First Tool to Use When Internet Has Problems
Ping is the first tool — not because it tells you everything, but because it tells you the most important thing first: whether your machine can communicate with another machine at all.
Before checking DNS settings, before resetting adapters, before calling your ISP — a simple ping to your router or to an external IP address tells you immediately whether the problem is local, somewhere in your ISP’s network, or beyond.
No other built-in Windows tool gives you that answer as quickly. That is why every network troubleshooting guide — from enterprise IT to home networking — starts with ping.
How to Open Command Prompt and Run Ping on Windows 11
To use the ping command on Windows 11, you need to open Command Prompt. The fastest way is to press Windows + R, type cmd, and press Enter. Alternatively, you can click the Start menu, type cmd or Command Prompt, and select it from the results.
You do not need to run it as administrator for basic ping operations. A standard user Command Prompt window is enough.
Once the window is open, type a ping command in this format:
ping 8.8.8.8
Press Enter. Windows sends four ICMP Echo Request packets to the target by default and displays the results line by line. That output is what you need to learn to read — because every field in it tells you something specific about the state of your connection.
How to Read Ping Results Line by Line
The output of a ping command on Windows 11 is divided into three sections: the resolution line at the top, the individual reply lines in the middle, and the summary at the bottom. Each section answers a different diagnostic question.
What the First Line Means — Hostname and IP Address
When you ping a website by name — for example, ping google.com — the first line of output shows the hostname being pinged and the resolved IP address in square brackets.
It looks like this:
Pinging google.com [142.250.193.206] with 32 bytes of data:
This line confirms two things. First, DNS resolution is working — your system successfully translated the hostname into an IP address. Second, it shows the actual IP your packets are heading toward. If this line fails or shows an error, the problem is likely DNS-related, not a full connectivity failure.
When you ping an IP address directly, this line simply confirms the target IP and the packet size being sent.
What Each Reply Line Means — Bytes, Time, TTL
After the first line, you see individual reply lines — one for each packet sent. A typical reply looks like this:
Reply from 142.250.193.206: bytes=32 time=14ms TTL=117
Each field means something specific:
- bytes=32 — The size of the packet that was returned. By default, Windows sends 32-byte packets.
- time=14ms — The round-trip time in milliseconds. This is how long it took the packet to travel to the target and return. Lower is better.
- TTL=117 — Time to Live. This value starts at a maximum set by the target’s operating system and decreases by one at each router hop along the path. A TTL of 117 typically means the target started at 128 and the packet crossed 11 hops. If you want to understand what TTL reveals about the route your packets take, the explanation of what TTL means in networking breaks it down fully.
What the Summary at the Bottom Means — Sent Received Lost
After all reply lines are displayed, Windows prints a summary block:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
This tells you how many packets were sent, how many came back, and how many were lost. In a healthy connection, you see 0% loss. Any loss above zero means packets are being dropped somewhere between your machine and the target — which could indicate congestion, a failing link, or a misconfigured device along the path. The article on what packet loss actually is explains why even small percentages matter.
Below the packet stats, you also see round-trip time statistics:
Minimum = 12ms, Maximum = 18ms, Average = 14ms
This gives you the fastest, slowest, and average response times across all replies. If the difference between minimum and maximum is large, that signals jitter — inconsistent latency that affects real-time applications like video calls and gaming.
What a Good Ping Result Looks Like vs a Bad One
A good result has zero packet loss, a low average time (under 50ms for domestic targets), and consistent round-trip values with minimal variation between minimum and maximum.
A bad result shows one or more of these: packets lost, reply times above 100ms, extreme variation in response times, or complete timeouts where no reply is received at all.
Knowing the difference between these two outcomes is what turns ping from a simple command into a real diagnostic tool.
All Ping Command Switches Explained — Windows 11
By default, the ping command on Windows 11 sends four 32-byte packets with a one-second timeout. That is useful for a quick check, but real troubleshooting often requires more control — longer tests, larger packets, or specific protocol behavior. That is what switches are for.
A switch is a parameter you add after the ping command to modify how it operates. Windows 11 supports several switches, and each one serves a specific diagnostic purpose. Below is a complete breakdown of the most important ones.
ping -t — Continuous Ping Until You Stop It
ping -t 8.8.8.8
By default, Windows sends only four packets and stops. The -t switch overrides that and tells Windows to keep sending packets continuously until you manually stop it by pressing Ctrl + C.
This is essential when you need to monitor a connection over time — for example, while restarting a router, switching between Wi-Fi and Ethernet, or waiting for an ISP outage to resolve. A four-packet test might look fine, but a continuous ping running for several minutes can reveal intermittent drops that a short test would miss completely.
When you press Ctrl + C, Windows displays the same summary statistics — sent, received, lost, and round-trip times — covering the entire duration of the test. That summary is what you use to calculate overall packet loss and latency trends.
ping -n — Set Number of Requests
ping -n 50 8.8.8.8
If you want more than four packets but do not need an indefinite continuous test, the -n switch lets you specify the exact number of Echo Requests to send. The example above sends 50 packets.
This is useful when you want a controlled, repeatable test. A 50-packet or 100-packet test gives you a statistically meaningful loss percentage without requiring you to sit and watch the screen waiting to press Ctrl + C.
ping -l — Change Packet Size
ping -l 1472 8.8.8.8
The -l switch changes the size of the data payload in each packet. The default is 32 bytes, but you can increase it up to 65,500 bytes.
Why would you change it? Because some network problems only appear with larger packets. A 32-byte ping might succeed while a 1,472-byte ping fails — revealing an MTU (Maximum Transmission Unit) issue somewhere along the path. Testing with -l 1472 is a common method to check whether your connection can handle full-sized Ethernet frames without fragmentation.
ping -a — Resolve IP Address to Hostname
ping -a 192.168.1.1
When you ping an IP address with the -a switch, Windows attempts to perform a reverse DNS lookup and display the hostname associated with that IP. This is useful when you are looking at an IP in your network and want to identify what device or server it belongs to without opening a separate lookup tool.
If no reverse DNS record exists for that IP, the command still works — it simply shows the IP address without a hostname, just like a regular ping.
ping -4 and ping -6 — Force IPv4 or IPv6
ping -4 google.comping -6 google.com
When you ping a hostname, Windows decides whether to use IPv4 or IPv6 based on your system configuration and what the DNS resolver returns. If your network supports both protocols, Windows 11 may default to IPv6 — which can be confusing when you expect an IPv4 address in the output.
The -4 switch forces the ping to use IPv4 only, and -6 forces IPv6 only. This is particularly useful when troubleshooting connectivity issues that affect one protocol but not the other. For example, your IPv4 connection might work perfectly while IPv6 is misconfigured — or the reverse. These switches let you test each path independently.
ping -w — Set Timeout in Milliseconds
ping -w 5000 8.8.8.8
By default, Windows waits 4,000 milliseconds (4 seconds) for a reply before declaring a timeout. The -w switch lets you change that value.
Increasing the timeout is useful when pinging a target that is geographically distant or known to have high latency — such as a server on another continent. If a server takes 4,500ms to respond due to heavy load or satellite routing, the default timeout would report it as lost. Setting -w 5000 gives it an extra second to reply, which produces more accurate results in those specific conditions.
Decreasing the timeout below 4,000ms is rarely useful for external targets but can speed up internal network scans where you expect fast responses.
ping -i — Set TTL Value Manually
ping -i 10 8.8.8.8
The -i switch sets the Time to Live value in the outgoing packet. Each router the packet passes through decreases this value by one. When it reaches zero, the packet is discarded and the router sends back an ICMP “Time Exceeded” message.
Setting a low TTL manually lets you test how far your packets travel before being dropped. For example, -i 10 means the packet can only cross 10 router hops. If the target is 15 hops away, the ping will fail — but you will see which router at hop 10 sent the expiration message. This technique is similar to what tracert does under the hood.
Step-by-Step Ping Troubleshooting Method — From Inside Out
Using the ping command for internet troubleshooting on Windows 11 is most effective when you follow a structured sequence — starting from your own machine and working outward toward the internet. Each step tests a different segment of the connection path. When a step fails, you have found the segment where the problem exists.
Step 1 — Ping Loopback Address 127.0.0.1
ping 127.0.0.1
This pings your own machine’s loopback address. The packet never leaves your computer — it tests whether the TCP/IP stack inside Windows is functioning correctly. If this fails, the problem is inside your operating system’s network configuration, not your router or ISP. A failure here usually means the network adapter is disabled, the TCP/IP stack is corrupted, or a driver is malfunctioning.
Step 2 — Ping Your Default Gateway
ping 192.168.1.1
Your default gateway is typically your router’s local IP address. You can find it by running ipconfig in Command Prompt and looking for the Default Gateway line. Pinging it confirms that your computer can reach the router over your local network — whether through Ethernet or Wi-Fi.
If the loopback test succeeds but the gateway ping fails, the issue is between your machine and the router. This could be a bad cable, a Wi-Fi authentication problem, or a router-side issue. The guide on fixing the inability to ping a default gateway covers every common cause.
Step 3 — Ping Your ISP DNS
ping <your ISP DNS address>
Your ISP assigns DNS server addresses when your router connects. You can find these in your router’s admin page or by running ipconfig /all. Pinging your ISP’s DNS server tests whether traffic can leave your local network and reach your ISP’s infrastructure. A failure here — with gateway ping working — points to a problem between your router and your ISP.
Step 4 — Ping Google DNS 8.8.8.8
ping 8.8.8.8
This tests whether your connection can reach a public server beyond your ISP’s network. Google’s public DNS at 8.8.8.8 is a reliable target because it is almost always online. If this succeeds, your internet connection is working at the IP level.
Step 5 — Ping a Website by Name
ping google.com
This final step tests DNS resolution on top of connectivity. If pinging 8.8.8.8 works but pinging google.com fails, the problem is specifically with DNS — your system cannot translate hostnames into IP addresses, even though the underlying connection is functional. In that case, the fix involves DNS settings, not your physical connection or ISP link.
How to Use Ping to Check for Packet Loss
A quick four-packet ping test can tell you if a connection is alive, but it cannot reliably measure packet loss. Four packets are too few — one dropped packet shows as 25% loss, which could be a fluke or a serious problem. To get a meaningful picture, you need a larger sample.
Run a 100-Packet Continuous Ping Test
ping -n 100 8.8.8.8
This sends exactly 100 ICMP Echo Requests to the target. You can also use the continuous method with -t and let it run for a few minutes before pressing Ctrl + C, but the -n 100 approach gives you a fixed, repeatable test that is easy to compare across different times of day or different targets.
For a more thorough test — especially when diagnosing intermittent problems — run the same command against multiple targets: your default gateway, your ISP DNS, and a public DNS like Cloudflare’s 1.1.1.1. Comparing the results across these targets tells you which segment of the path is dropping packets.
How to Calculate Packet Loss from Ping Results
Windows calculates it for you in the summary line:
Packets: Sent = 100, Received = 97, Lost = 3 (3% loss)
In this example, 3 out of 100 packets were lost — a 3% packet loss rate. For most general browsing, anything under 1% is acceptable. For gaming and video calls, even 1% can cause noticeable issues. Anything above 5% consistently points to a real problem — either on your local network, at your ISP, or along the route to the target.
If loss only appears when pinging beyond your gateway but not when pinging the gateway itself, the issue is upstream from your router. If loss appears even when pinging the gateway, the problem is on your local network — a bad cable, Wi-Fi interference, or a failing router.
What Each Ping Error Message Means
Not every failed ping looks the same. Windows returns different error messages depending on where and why the failure occurred. Each one points to a different part of the connection path.
Request Timed Out
This means your computer sent the packet, but no reply came back within the timeout window. The packet either never reached the target, or the reply was lost on the way back. Common causes include firewall blocking, ISP routing failures, or the target being offline. If you see this intermittently while the internet otherwise works, the detailed guide on fixing ping request timed out walks through every scenario.
Destination Host Unreachable
This error means a router along the path — or your own machine — determined that the target cannot be reached. It often appears when there is no valid route to the destination, the target device is powered off on a local network, or an ARP resolution failure occurs. The full breakdown of destination host unreachable causes and fixes covers each case in detail.
Ping Transmit Failed General Failure
This error does not come from the network — it comes from inside Windows itself. It means the operating system could not even send the packet. Typical causes include a corrupted TCP/IP stack, a disabled network adapter, or conflicting IPv6 configuration. This is one of the few ping errors that indicates a local software problem rather than a network path issue. The guide on fixing ping transmit failed general failure provides step-by-step solutions.
Reply from a Different IP Address
Sometimes you run a ping to one IP address but receive a reply from a completely different one. This happens when an intermediate router intercepts the packet and responds on behalf of the target — usually with a TTL Expired or Destination Unreachable message. It does not always indicate a problem, but it can signal route hijacking or misconfigured network equipment. The explanation of why ping replies come from a different IP address explains how to interpret this correctly.
When Ping Is Blocked and Does Not Mean the Site Is Down
A common mistake is assuming that if ping fails, the target is offline. That is not always true. Many servers and firewalls intentionally block ICMP traffic as a security measure. A website can be fully operational — serving web pages without any issue — while refusing to respond to ping requests entirely.
For example, some major websites do not respond to ping at all. If you ping them, you get “Request Timed Out” for every packet — yet opening them in a browser works perfectly. This is because their firewalls are configured to drop ICMP Echo Requests while still accepting HTTP and HTTPS connections on ports 80 and 443.
This is why the step-by-step troubleshooting method uses well-known public DNS servers like 8.8.8.8 as targets instead of random websites. These servers are specifically configured to respond to ping, making them reliable diagnostic endpoints. When ping fails to a public DNS but works to your gateway, you have a genuine connectivity issue — not a firewall false positive.
Frequently Asked Questions
How do I use the ping command in Windows 11?
Open Command Prompt by pressing Windows + R, typing cmd, and pressing Enter. Then type ping followed by an IP address or hostname — for example, ping 8.8.8.8 or ping google.com — and press Enter. Windows sends four test packets and displays the results immediately.
What does ping -t do in Windows?
The -t switch tells Windows to send ICMP Echo Requests continuously without stopping after four packets. The ping keeps running until you manually press Ctrl + C, at which point Windows displays the full summary of sent, received, and lost packets.
How do I stop a continuous ping in Windows?
Press Ctrl + C in the Command Prompt window. This stops the continuous ping and displays the statistics summary for the entire test duration. If you want to see interim stats without stopping the test, press Ctrl + Break instead.
How do I read ping results in Windows?
Ping output has three parts. The first line shows the target and resolved IP. The middle lines show individual replies with packet size, round-trip time, and TTL. The bottom summary shows total packets sent, received, lost, and min/max/average response times.
What is a good ping time in milliseconds?
For domestic targets within your country, anything under 30ms is excellent and under 50ms is good. For international targets, under 150ms is acceptable. Times consistently above 200ms indicate a slow or congested route. For gaming, staying below 50ms is generally recommended.
What does TTL mean in ping results?
TTL stands for Time to Live. It represents the remaining hop count for the packet. Each router along the path decreases TTL by one. The starting value depends on the target’s operating system — Windows devices typically start at 128. A reply showing TTL 128 means the target is directly reachable with no intermediate hops. The detailed explanation of why ping shows TTL 128 in Windows covers what this reveals about the route.
How do I use ping to test for packet loss?
Run ping -n 100 8.8.8.8 to send 100 packets. The summary line at the end shows exactly how many packets were lost and the loss percentage. Any consistent loss above 1% warrants further investigation.
What does Request Timed Out mean in ping?
It means your computer sent the ICMP Echo Request but received no reply within the timeout period. The target may be offline, a firewall may be blocking ICMP, or packets may be dropping along the route between you and the target.
How do I ping my router to test my connection?
Run ipconfig in Command Prompt and find the Default Gateway address — usually something like 192.168.1.1 or 192.168.0.1. Then run ping 192.168.1.1. If this succeeds, your local connection to the router is healthy. If it fails, the problem is between your computer and the router.
What is the difference between ping by IP and ping by hostname?
Pinging by IP tests network connectivity only. Pinging by hostname tests both DNS resolution and connectivity. If ping works by IP but fails by hostname, the problem is with DNS — your system cannot translate domain names to IP addresses, even though the underlying network path is functional.
Why does ping say General Failure on Windows 11?
General Failure means Windows could not send the packet at all. This is a local operating system issue — not a network path problem. Common causes include a corrupted TCP/IP stack, a disabled adapter, or a broken IPv6 configuration. Resetting the network stack with netsh int ip reset and restarting the computer resolves it in most cases.
How do I run a 100 packet ping test?
Use the -n switch: ping -n 100 8.8.8.8. This sends exactly 100 ICMP Echo Requests to the target. After all 100 packets are sent, Windows displays the complete statistics including packet loss percentage and round-trip time averages.
Can ping tell me where my internet problem is?
Yes — if you follow the inside-out method. Ping the loopback (127.0.0.1), then your gateway, then your ISP DNS, then a public DNS, then a website by name. The step where ping first fails identifies the exact segment of your connection path that is broken.
Why does ping work on IP but not on website name?
This means DNS resolution is failing while your internet connection is working at the IP level. Your computer can send and receive packets, but it cannot look up domain names. The fix is to change your DNS servers — either in your network adapter settings or on your router — to a reliable public DNS, and then flush the local DNS cache with ipconfig /flushdns.
A final detail worth noting: if you see a TTL value of 117 in your ping results, it typically means the target started with a TTL of 128 and the packet crossed 11 router hops — a perfectly normal result for most external servers.
Final Summary
The ping command remains the most efficient first-response tool for internet troubleshooting on Windows 11. It tells you whether a target is reachable, how long the round trip takes, and whether packets are being lost along the way.
The structured inside-out method — loopback, gateway, ISP DNS, public DNS, hostname — systematically narrows down where a failure occurs. Combined with the right switches like -t for continuous monitoring, -n for controlled sample sizes, and -l for packet size testing, ping covers the majority of first-line network diagnostics without needing any third-party tools.
If your ping tests show consistent packet loss or timeouts beyond your default gateway — especially when pinging reliable public targets like 8.8.8.8 — and you have confirmed your local network is healthy, the problem is with your ISP. At that point, share your ping results with your ISP’s support team. A 100-packet test with visible loss percentages is concrete evidence that speeds up the troubleshooting process on their end.
Ping does not solve every network problem. But it tells you exactly where to look — and that is the most valuable thing a diagnostic tool can do.