If you want to test your computer connectivity or check the quality of your internet connection, all you need to do is perform a ping test. If you experience a connectivity issue, you’ll tell if you can narrow the issue to your local network (your home or office setup) or if the problem goes beyond (your internet service provider, host network, or a particular website). Here’s how to do a ping test on a Windows 10 PC and how to read the results.
What is a Ping Test?
A ping test measures your latency, which tells you the quality of your connection. Low latency connection becomes important for online gaming, loading web pages quickly, video chatting, and more.
When you do a ping test, your computer sends a small packet of data to your host, a web domain, or another device in your network. The results will show you how fast your computer gets a “pong” response back in milliseconds. You want your ping response time to be as low as possible.
How to Do a Ping Test on a Windows 10 PC
To do a ping test in Windows 10, open the Windows Search Bar, type CMD, and click Open. In the Command Prompt, type ping followed by a space and then the IP address or domain name you want to test and hit Enter.
- Open the Windows Search Bar. You can do this by clicking the magnifying glass icon in the bottom-left corner of your screen.
- Then type CMD into the search bar and click Open. This will open a Command Prompt window with a black background, white text, and a flashing cursor.
- Type ping followed by a space and an IP address or domain name. For example, you would enter “ping 192.168.1.1” or “ping hellotech.com”. If you want to ping your router, check out our guide on how to find your router’s IP address.
- Finally, hit Enter on your keyboard and wait for the ping test results.
How to Read Your Ping Test Results
When you do a ping test on a Windows 10 PC, you will see the results for four different ping tests. Each test will tell you the ping time in milliseconds (ms) and how many packets were received or lost. You will also see the minimum, maximum, and average ping response times.
If one of your ping tests showed that packets were lost or one ping response took a lot longer than the others, it could be a sign of a problem with your connection.
If you are doing a ping test to check your internet connection, you can ping Google’s DNS servers by entering “ping 220.127.116.11”. This will tell you if there is a problem with your internet connection, rather than just the connection to a certain site.
In order to see continuous ping results, you can append your command with “-t”. For example, you can enter “ping 18.104.22.168 -t” to see if your connection to Google’s DNS servers ever times out. Then, to stop the test, simply hit the Control + C keys on your keyboard at the same time.
Common Ping Error Messages
Here are the most common error messages you will see if your ping test returned failed results:
- Request timed out: This means the ping test took longer than the default limit of 4,000 milliseconds (4 seconds). This could be caused by network congestion, a firewall set to stop specific traffic, defective cables or ports, and more.
- Unknown host: This error message means that the requested host name is not recognized. Check that the name is entered correctly and that your router is functioning properly.
- TTL expired in transit: The TTL you see after your ping time for each test refers to the number of “hops” that the routers will allow your packet to make before being discarded. So, this error message means that your packet exceeded the maximum number of allowable hops.
- General failure: This either means your computer does not have the proper TCP/IP settings or that you may have a problem with your local area network (LAN) adapter or drivers, such as your router or WiFi card.
- <destination> is unreachable: This message means that the tool cannot find a route to the destination. If the message says, “Reply from <destination>: Destination Host Unreachable,” that means that the remote router has a routing problem, not with the <destination> itself.
If you see one of these error messages, you might need to troubleshoot network issues. You can try to ping other devices or other domains to see if the problem persists. This will help you determine whether the problem exists with your device or with your network connection.