PING MONITORING
See public endpoint reachability and latency
Follow public host reachability, round-trip latency and packet loss. Use these network signals alongside application checks to understand an outage.
Public destinations only
Private, local, metadata and reserved destinations are rejected centrally.
Useful trends
Recent measurements and daily uptime summaries keep longer dashboards efficient.
Understand an ICMP result
Ping observes ICMP echo responses from a public host. The bounded sample reports round-trip latency and packet loss. Firewalls can block ICMP while the website remains healthy, so a failed Ping result is not proof that an HTTP service has stopped responding.
Select a meaningful host
Use a stable public hostname or IP that permits ICMP. Check a sample result before enabling incident alerts. Hostnames can resolve to several addresses; this check selects a validated address and is not a claim that every address or geographic route has been tested.
Diagnose lost responses
Compare the failure time with network changes and firewall rules. Use an HTTP check for the website and a TCP check for the service port to distinguish protocol-specific blocking from a broader outage. A small successful sample cannot establish the quality of every network path.
Reduce secondary alert noise
A gateway or upstream host can be a dependency of related monitors. When it is down, child checks keep recording their actual results while secondary DOWN notifications can be suppressed. Bounded escalation and recovery notification provide a clear response path without unlimited repeat alerts.
Common questions
Does Ping measure website page-load speed?
No. It measures ICMP reachability and round-trip latency, not an HTTP response or browser rendering.
Can I use it for a private server?
Private, loopback, metadata and reserved destinations are outside the supported public monitoring policy.