Online Ping Test
Measure round-trip response time and packet loss from our server to any hostname or IP address, and use the results to understand latency and reachability more clearly.
Measure response time in seconds.
Spot loss or reachability problems quickly.
Test reachability from outside your own network.
What this ping test shows
This tool gives you a quick network reachability check from an external server, including response time and packet loss across multiple ping attempts.
That makes it useful for developers, operations teams, gamers, support teams, and anyone checking whether latency or reachability may be part of a problem.
Why it matters
Ping is one of the fastest ways to understand whether a host is reachable and whether delay or packet loss may be affecting performance.
What is a ping test?
A ping test sends a small ICMP echo request packet to a target host and measures how long it takes to receive a reply. The result is called round-trip time (RTT) and is expressed in milliseconds (ms).
Low latency (under 50ms) is ideal for most uses. Latency above 150ms may cause noticeable delays for real-time applications like video calls or gaming. Packet loss — when some pings get no reply — indicates network congestion or filtering.
Why use an online ping tool?
Running ping from your own device only tells you about your local connection. An online ping tool tests from a neutral, external server — so you can tell whether a host is reachable from the public internet, independent of your ISP or local network.
If our server can reach the host but you can't, the issue is likely on your local network or ISP. If neither can reach it, the host or its firewall is likely blocking ICMP.
Understanding ping results
- RTT (Round-Trip Time) — the total time in milliseconds for a packet to travel to the host and back. Lower is better.
- Min / Avg / Max — the best, average, and worst RTT across multiple pings. A large gap between min and max suggests network jitter.
- Packet loss — if some ICMP packets receive no reply, it often means network congestion, firewall filtering, or an unstable link.
- TTL (Time to Live) — the maximum number of hops the packet is allowed to traverse. A low TTL in the reply can indicate a distant host.
What is a good ping?
What counts as a "good" ping depends on your use case:
- < 20 ms — excellent. Ideal for competitive gaming and low-latency trading.
- 20–50 ms — very good. Smooth for video calls, VoIP, and interactive apps.
- 50–100 ms — acceptable for general browsing and streaming.
- 100–200 ms — noticeable delay. May affect real-time applications.
- > 200 ms — high latency. Investigate routing, ISP issues, or geographic distance.
Why might a ping fail?
A ping failure (100% packet loss or "host unreachable") can be caused by:
- ICMP blocked by firewall — many servers and cloud providers disable ping responses by default.
- Host is down — the server is offline or unreachable.
- DNS resolution failure — the hostname cannot be resolved to an IP address.
- Network routing issues — intermediate routers may be dropping packets.
If ping fails, try a traceroute to pinpoint where along the path packets are being dropped.
Frequently asked questions
What does an online ping test measure?
It measures round-trip time and packet loss between a server and a target host.
What is a good ping time?
For many uses, under 50 ms is very good, while higher values can create noticeable delay in real-time use cases.
Why can a host respond slowly?
Latency can be affected by distance, routing, congestion, server load, or filtering along the path.
What should I use after ping?
If you need more detail, traceroute and DNS tools can help explain where a connectivity issue is happening.