Ping monitor
The ping monitor sends ICMP echo requests to a host and measures round-trip time.
Configuration
| Field | Type | Default | Notes |
|---|---|---|---|
| Host | hostname | — | Hostname or IP. Protocol/port/path are auto-stripped. |
| Packet count | integer | 4 | 1–10 pings per check. |
| Timeout | seconds | 10 | 5–30. |
| Degraded threshold | ms | — | Optional. Slow round-trips return degraded. |
| IP versions | array | ["ipv4", "ipv6"] | Which families to test. Cloud runners are IPv4-only. |
Status mapping
| Outcome | Status |
|---|---|
| All packets answered, mean RTT under the degraded threshold | up |
All packets answered, mean RTT over degraded_threshold_ms | degraded |
| Any packet loss, or total timeout | down |
Private & internal targets
Cloud checkers block pings to private or reserved addresses
(RFC 1918 ranges, localhost, link-local / cloud-metadata, CGNAT
and similar). A check against a blocked or unresolvable target
records an explicit down result with the block or DNS-failure
reason in the error message. To ping internal hosts, use a
self-hosted runner.
Cloud vs self-hosted
Both cloud and self-hosted runners send ICMP echo requests — but cloud checkers are IPv4-only, so ICMPv6 ping (like all IPv6 monitoring) requires a self-hosted runner. Some upstream networks silently drop ICMP from cloud compute, so if a cloud region consistently fails ping checks against a target that self-hosted runners reach without issue, the cloud network path is the most likely cause. For those targets switch to a TCP port check, or run the monitor from a self-hosted runner closer to the target.