DOCS

Ping monitoring

Monitor network-level reachability of any server or IP address with ICMP echo requests (ping) — no HTTP required.

Ping (ICMP) monitors check network-level reachability of any server or IP address using ICMP echo requests. Unlike HTTP monitors, they work at the network layer and require no HTTP server on the target.

How it works

HowlOps probers send ICMP echo requests to the target IP or hostname at the configured interval. If the host doesn't respond within the timeout, it is marked down and an alert is triggered.

Configuration

FieldDescription
Host / IPHostname or IP address to ping, e.g. 192.168.1.1 or db.example.com
Check intervalHow often to send the ping. Minimum: 120s on Free, 60s on S, 30s on M, 15s on L
TimeoutMax wait time for an ICMP reply. Default: 5 seconds
Packet countNumber of ICMP packets per check. Default: 3
Alert thresholdConsecutive failures before triggering an alert. Default: 2

Use cases

  • Database servers — verify network-level availability even when no HTTP endpoint exists.
  • VPN gateways and routers — monitor network infrastructure from an external perspective.
  • CDN edge nodes — ping specific IPs to verify anycast routing.

Plan availability

FeatureFreeSML
Ping monitors50 total100 total500 total2000 total
Minimum check interval120s60s30s15s
Multi-region pingSingle region

For current limits and pricing, see the pricing page.

FAQ

Can I ping a private IP address? No. HowlOps probers run from cloud infrastructure and can only reach publicly routable IPs. Private/internal addresses are not reachable from external probers.

Why does ping fail but HTTP works? Most likely ICMP is blocked by a firewall — common on cloud VMs. Use an HTTP monitor instead.

Does ping check SSL certificates? No. Ping is network-layer only. Use an HTTP monitor for SSL monitoring.

Was this page helpful?