Ping Check
Global multi-node ICMP ping from multiple regions — measure latency and packet loss
Usage
• Target: domain or IP address (e.g. example.com or 1.1.1.1)
• Count: number of ping packets to send (4, 10, or 20)
• Result metrics: average / min / max latency and packet loss
• Nodes: pick specific nodes; defaults to all available nodes
What multi-location ping testing is for
Multi-location ping sends ICMP echo requests to your target host from real probe nodes around the world, measuring the round-trip latency (RTT) and packet loss seen from each region. A single ping shows one path; multi-location ping reveals how connectivity and latency differ for users in different regions at a glance.
Multi-node Ping compares connectivity, latency and loss at selected nodes. If ICMP does not respond, use TCPing to check transport connections or HTTP probing to check application responses.
Frequently asked questions
Does a failed ping mean the server is down?
Not necessarily. Many servers and network devices deliberately drop ICMP, so ping times out while HTTP/TCP services still work. Combine it with a TCPing or HTTP check to judge whether the service is actually available.
What latency is normal?
Ping latency has no universal passing threshold. Compare the same nodes, target, protocol and time window against a historical baseline, and assess sustained changes, jitter and loss against application needs.
What causes high packet loss?
Ping loss can result from congestion, faults or ICMP rate limiting and filtering. Compare destination results over repeated probes. A missing intermediate-hop response alone does not establish forwarding loss there.
Why do nodes show very different latency?
Because each node reaches the target over a different physical distance and set of network carriers. That is exactly the value of multi-location ping: it surfaces regions where access quality is noticeably worse.
References and result limitations
Online results reflect the queried source or probe state at that time. Record the target, time, nodes or data source, and parameters when citing them. A single result does not establish continuous availability everywhere.
These references explain protocol or format rules; they do not endorse results produced by this site.