Ping
ICMP echo — is the host reachable, and how fast?
Enter a value above to run Ping
e.g. example.com
Quick answer
Ping sends ICMP echo requests to a host to check whether it is reachable and how long the round trip takes, measured in milliseconds. Lower response times mean a faster connection, while timeouts or packet loss point to an unreachable host or network problem.
Ping is the fastest way to answer two questions: is a host reachable, and how long does a packet take to get there and back? It sends ICMP echo request packets to a hostname or IP address and measures the time until each matching echo reply comes back. Because it works at the network layer, ping tells you whether the machine itself is responding, independent of whether any web server or application on it is running. It is usually the first check when a site or server suddenly feels slow or unreachable.
How it works
Ping sends an ICMP Type 8 (echo request) packet and waits for a Type 0 (echo reply). The round-trip time (RTT) is the gap between sending and receiving, reported in milliseconds. Each packet carries a sequence number and a TTL (time to live) that drops by one at every router hop. Ping repeats this several times so you can see not just one measurement but the pattern of latency and any dropped packets over a short window.
How to read the results
Look at three numbers: reachability, latency, and loss. Successful replies mean the host is up. RTT tells you speed: under 30 ms is excellent, 30-100 ms is normal for distant servers, and consistently over 200 ms feels sluggish. Watch the min/avg/max spread. A wide gap (jitter) points to congestion or an overloaded link. Any packet loss above 0% on a wired path is a warning sign worth investigating further with traceroute.
Common problems & fixes
A "request timed out" does not always mean the host is down. Many servers and firewalls silently drop ICMP for security, so a healthy web server can still refuse ping while serving pages fine. If ping fails, try the site in a browser or test the specific port instead. Occasional loss on Wi-Fi is normal; steady loss on a wired connection suggests a bad cable, saturated link, or a failing router along the route.
Frequently asked questions
- Why does a working website fail to respond to ping?
- Because ping uses ICMP, a separate protocol from the HTTP traffic that serves web pages. Many hosts, cloud providers, and firewalls block or rate-limit ICMP to reduce noise and deter scanning. The web server keeps answering on port 80 and 443 normally. A timed-out ping to such a host is expected and not proof of an outage.
- What is a good ping time?
- It depends on distance. Within the same city or region, expect single-digit to low double-digit milliseconds. Across a continent, 30-80 ms is typical, and intercontinental links often run 150-250 ms. For gaming and video calls, under 50 ms feels responsive. What matters most is consistency: stable RTT with no loss beats a low average that spikes erratically.
- What is the difference between ping and traceroute?
- Ping measures the total round trip to one destination and tells you if it responds and how fast. Traceroute maps every router hop between you and the host, showing where latency builds up or packets get lost. Start with ping to confirm there is a problem, then use traceroute to locate which hop along the path is responsible.