How to Use the Ping Command to Check Your Internet Connection
When your internet feels slow or websites fail to load, the first question is always the same: is my connection actually working? One of the simplest and most reliable ways to find out is a decades-old command-line tool called ping. In this article, we will walk through what ping does, why it matters, and how you can use it on your own device to quickly test your connectivity.
The video below demonstrates the basics in under a minute: open a terminal, type a simple command, and let the network speak for itself.
What the Video Shows
The short video at the top of this post demonstrates the most straightforward use of ping: opening a terminal application and running a ping against Google. The command is as simple as typing ping google.com and watching the responses come back. If the terminal starts returning reply messages, your connection to the wider internet is alive and functioning at a basic level.
That simplicity is exactly why ping remains one of the first tools network professionals reach for, and why it is worth learning even if you are not a system administrator.
What Is Ping, Really?
Ping is a small utility that comes built into virtually every modern operating system including Windows, macOS, Linux, and even Android terminals. Its job is to test whether one device on a network can reach another device. It does this by sending a tiny packet of data and waiting for a reply.
Technically, ping uses a protocol called ICMP, the Internet Control Message Protocol. It sends what is known as an ICMP Echo Request to a target host, and if that host is reachable and configured to respond, it sends back an ICMP Echo Reply. The round-trip time, measured in milliseconds, tells you how long the packet took to travel to the destination and back.
Why Ping Google?
Google’s servers are highly reliable and respond to ping requests from most locations around the world. That makes google.com a convenient target when you want to know whether your own connection is the problem, rather than some random website being down. If you can ping Google successfully, your internet path is working end to end at the network layer. If web pages still will not load in your browser, the issue is likely somewhere higher up the stack, such as a browser problem, a DNS issue, or the website itself.
How to Run a Ping Test
Running a ping test is straightforward, and the exact steps vary only slightly depending on your operating system.
On Windows
Open the Command Prompt. You can do this by pressing the Windows key, typing cmd, and pressing Enter. In the terminal window, type:
ping google.com
Press Enter and watch the output. Windows will send four ping requests by default and then stop. Each reply line shows the round-trip time in milliseconds and the size of the packet received.
On macOS and Linux
Open the Terminal application. On macOS, you can find it in Applications > Utilities, or by searching with Spotlight. On Linux, it is usually available from the applications menu or by pressing a keyboard shortcut such as Ctrl+Alt+T. Type the same command:
ping google.com
Unlike Windows, the default behavior on macOS and Linux is to keep pinging continuously until you stop it. Press Ctrl+C when you have seen enough results. You can also limit the number of pings with a flag, such as ping -c 4 google.com to send exactly four requests.
On Android
The video title references Android, and many terminal emulator apps on Android support the ping command as well. Open your terminal app, type ping google.com, and review the output just as you would on a desktop.
Reading the Results
When ping works, you will see lines that look something like this:
64 bytes from 142.250.80.46: icmp_seq=1 ttl=118 time=14.3 ms
Here is what the key parts mean:
- Bytes – the size of the reply packet. This confirms a response was received.
- ICMP sequence number – the count of the ping request. If sequence numbers are missing or out of order, packets may be getting lost.
- TTL (Time to Live) – a value that decreases as the packet passes through routers. It can give a rough hint about how many network hops the packet traveled.
- Time (in milliseconds) – the round-trip latency. Lower numbers mean a faster connection. A time under 50 ms to a nearby server is generally good; a time over 100 ms may indicate congestion or distance.
At the end of a ping session, the summary tells you how many packets were sent, how many were received, and what percentage were lost. Zero percent packet loss is the goal. Any loss at all can signal an unstable connection.
A Step-by-Step Troubleshooting Method
Ping is most powerful when you use it in a structured way rather than pinging random addresses. A common approach is to work outward from your own machine, testing each link in the chain one at a time.
Step 1: Ping Your Own Machine (Loopback)
Start with:
ping 127.0.0.1
This target, called the loopback address, never leaves your computer. If this fails, your network stack itself has a problem, and no external connection will work until it is fixed.
Step 2: Ping Your Router or Gateway
Find the IP address of your local gateway, often something like 192.168.1.1, and ping it:
ping 192.168.1.1
If this succeeds, your device can reach your local network. If it fails while the loopback test passed, the problem is between your device and your router, such as a bad Wi-Fi connection or a disconnected cable.
Step 3: Ping an External IP Address
Ping a well-known public IP address that does not depend on DNS resolution, such as Google’s public DNS server:
ping 8.8.8.8
If this works, your connection to the internet is functioning at the network level. If it fails but step 2 succeeded, the problem is likely with your modem, your internet service provider, or the path beyond your home network.
Step 4: Ping a Domain Name
Finally, ping a hostname:
ping google.com
If step 3 succeeded but this one fails, your DNS resolution is broken. DNS is the system that translates human-readable names like google.com into IP addresses. When DNS fails, you may have a working internet connection but still be unable to load websites by name.
Continuous Ping for Ongoing Monitoring
Sometimes a single ping test is not enough. If you are troubleshooting an intermittent problem, or if you want to watch whether a connection stays stable over time, a continuous ping is very useful.
On Windows, add the -t flag:
ping -t google.com
This will keep sending pings until you press Ctrl+C. On macOS and Linux, the continuous default behavior already does this, and you can stop it with Ctrl+C as well. Some people run a continuous ping in one window while they restart a router, switch network cables, or make configuration changes in another window. When the replies stop or the latency spikes, they know exactly when the problem appeared.
Limitations of Ping
Ping is simple, but it is not a complete picture of your connection quality. There are a few important caveats to keep in mind.
- Not all devices respond. Some servers, firewalls, and network equipment are configured to ignore or block ICMP requests for security or performance reasons. A failed ping does not always mean a host is down.
- Latency is not the same as speed. Ping measures how long a small packet takes to make a round trip. It does not measure how fast you can download a large file. A connection can have low ping and still be slow in terms of bandwidth, or it can have higher ping and still deliver fast downloads.
- Firewalls can interfere. On some networks, especially corporate or heavily secured home networks, ICMP traffic may be filtered. If ping fails but websites load normally, this is often the explanation.
- Wi-Fi variability. On wireless connections, ping times can fluctuate due to signal strength, interference, and distance from the access point. A single high-latency reply may be a temporary glitch rather than a persistent problem.
When to Look Beyond Ping
If ping confirms that your connection is working but you still have problems, the next step is to narrow down where the breakdown is happening. Try loading a few different websites. If only one site is affected, the issue is probably with that site rather than your connection. If every site is slow, try a speed test to measure actual throughput. If DNS seems to be the problem, try switching to a public DNS server such as 8.8.8.8 or 1.1.1.1 and test again.
For more advanced diagnostics, tools such as traceroute (called tracert on Windows) can show the exact path your packets take across the internet and help identify where delays or failures occur along the way.
Conclusion
The ping command is a small tool with an outsized usefulness. It takes only a moment to run, requires no special software, and gives you an immediate answer to the most basic network question: can my device reach the outside world? The video at the top of this article shows how little it takes to get started. Open a terminal, type ping google.com, and let the results tell you what is happening with your connection.
Once you understand how to read the output and how to work through a structured sequence of tests, ping becomes a reliable first stop whenever your internet acts up. It will not solve every problem on its own, but it will point you in the right direction faster than guessing.
