Online ping test
Sends ICMP echo requests to a host or IP and reports whether it is reachable, the round-trip time and any packet loss. If ICMP is blocked, it falls back to a TCP connection test.
How the ping test works
The tool sends four ICMP echo request packets from our server to the host and measures how long each reply takes to come back. That round-trip time (RTT) is reported as a minimum, average and maximum, together with the percentage of packets that were lost on the way.
If ICMP is blocked - which many hosts and firewalls do on purpose - the tool falls back to opening a TCP connection on port 443, then port 80. A successful handshake proves the host is reachable even when it does not answer pings, and the time of that handshake is reported as the RTT.
Because the test runs from the public internet, it measures the path from our server to the host, not from your own computer. Your local latency will differ depending on your connection and physical distance to the host.
How to read the results
Three numbers tell most of the story:
- Average RTT - the typical latency. Under 30 ms is excellent, 30-100 ms is normal across regions, and consistently high values point to a slow path or an overloaded host.
- Min versus max RTT - a large gap (jitter) means the latency is unstable, which hurts real-time traffic like calls and gaming more than raw throughput does.
- Packet loss - anything above 0 percent on a wired path is suspicious. Loss causes retransmissions and stutter; sustained loss usually means congestion or a failing link.
Common problems
The host is up but ping reports unreachable. Many servers and firewalls block ICMP echo for security reasons while still serving web traffic normally. In that case the TCP fallback will still show the host as reachable - rely on that result rather than on ICMP alone.
High or unstable round-trip times. A long average RTT can mean the host is geographically far or the path is congested. A large min-to-max spread means jitter, often caused by an overloaded link or wifi interference closer to the source.
Intermittent packet loss. Loss that comes and goes usually indicates congestion or a marginal link somewhere on the path. Run the test a few times; if the loss persists, the problem is on the network rather than a one-off blip.
Frequently asked questions
What does ping actually measure?
Ping measures the round-trip time for a small ICMP echo packet to travel to the host and back, plus how many packets are lost. It is a quick way to confirm a host is reachable and to gauge network latency, but it does not test whether a specific service such as a website is working.
Why does the host not respond to ping even though it is online?
ICMP echo is often blocked by firewalls or disabled on the host as a security measure, so a missing reply does not mean the host is down. This tool then falls back to a TCP connection on port 443 or 80, which confirms reachability even when ping is filtered.
What is a good ping time?
Under 30 ms is excellent and typical within the same region. Between 30 and 100 ms is normal across countries. Consistently above 150 ms, or large variation between minimum and maximum, can make interactive applications feel sluggish.
What is the difference between the ICMP and TCP methods?
ICMP ping sends dedicated echo packets and gives a clean latency and packet-loss measurement. The TCP fallback instead times a real connection to port 443 or 80; it only confirms reachability and a single round-trip time, but it works even when ICMP is blocked.
Stop pinging by hand
ePulz.io pings your hosts automatically from one minute, verifies outages from multiple regions and alerts you by email or Telegram.
Try for free →About this tool
An online ping test is the quickest check of whether a host is reachable and how fast the network path to it is. It reports round-trip time and packet loss over ICMP, and because many hosts block ICMP on purpose, it falls back to a TCP connection so you still get a reliable reachability answer. Remember that a blocked ping does not mean the host is down.