Types
ICMP
Basic network reachability (ping) monitor for hosts when application-level checks aren’t required.
ICMP monitors (ping) test basic network reachability and latency by sending echo requests to a host (domain or IP). Use this when you only need to know if a host is up—not whether an application endpoint is healthy.
When To Use
- Edge servers / load balancers
- Network devices (gateways, routers)
- Lightweight availability signal before deeper checks
When Not To Use
- HTTP APIs (use HTTP monitor)
- Port‑specific services (use TCP/UDP monitor)
- Job heartbeat tracking (use Heartbeat monitor)
Settings
| Field | Description | Example |
|---|---|---|
| host | FQDN or IPv4/IPv6 to ping | api.example.com |
| ttl (interval) | Seconds between checks (plan minimum enforced) | 60 |
| retries | Number of retry attempts before marking offline | 3 |
| region | Probe region | eu-central |
Latency data can later feed uptime / response graphs. Large ICMP packet customization is currently not exposed.
Status Labels
- Reachable (good)
- Unreachable (bad)
Tips
- Pair ICMP with a TCP or HTTP monitor for layered visibility.
- If a host blocks ICMP (common in hardened environments) use a TCP or HTTP alternative instead.