Global multi-node ICMP ping from multiple regions — measure latency and packet loss
Monitor continuously
Create a scheduled monitor — automatically probe from multiple global nodes and get alerted on failures.
• 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
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.
It is commonly used to confirm a server is reachable from each region, compare latency across regions, and investigate intermittent packet loss. If the target blocks ICMP, use TCPing or an HTTP check to verify connectivity at the application layer instead.
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.
Within the same region it is usually tens of milliseconds; across continents it is typically one to two hundred milliseconds. It depends on physical distance and link quality — sustained high latency or jitter is what matters most.
Possible causes include link congestion, rate limiting at an intermediate hop, ICMP rate limiting at the target, or poor local network quality. Use traceroute to pinpoint which hop is dropping packets.
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.