Global Ping Test

Measure public-host reachability, round-trip latency, and packet loss from global probe locations.

Ping a public host

The target is resolved and checked before dispatch, then checked again by every Agent.

What this Global Ping test does

The test sends a bounded ICMP task to independent NetOpsKit Agents. Results appear separately, so one timeout does not hide successful measurements from other regions.

Understanding the result

Latency is round-trip time in milliseconds. Packet loss is the percentage of probes without a reply. Physical distance, peering, congestion, and filtering can all affect both values.

Common issues

Some hosts intentionally block or rate-limit ICMP while continuing to serve web traffic. Compare the result with the Global Network Test's HTTP mode when troubleshooting a website.

Frequently asked questions

Why can a website work when Ping fails?

A firewall may block ICMP echo requests while still allowing HTTP and HTTPS traffic.

What is a good Ping latency?

It depends on distance. Under 50 ms often feels responsive, while intercontinental routes commonly exceed 100 ms.

What causes packet loss?

Congestion, wireless interference, rate limiting, routing faults, or remote filtering can all cause missing replies.

Is the test really run from multiple regions?

Yes. Each displayed result is submitted by the named Agent in that location.