---
title: Ping (ICMP) monitoring
description: For a host that speaks no HTTP, a plain ping is often the right check to run. Ping (ICMP) monitors are here, with round-trip time and packet-loss stats, and…
canonical: https://watchfor.io/changelog/2026-05-09-ping-icmp-monitoring
---

[All updates](/changelog/page/9#2026-05-09-ping-icmp-monitoring) ✨ New May 9, 2026 · v 1.1.9

# Ping (ICMP) monitoring

For a host that speaks no HTTP, a plain ping is often the right check to run. Ping (ICMP) monitors are here, with round-trip time and packet-loss stats, and their incident insight is tuned for latency and loss rather than a check duration that told you very little.

Round-trip time, jitter and packet loss over the day.

## What you see

- Round-trip time, jitter and packet loss for every check.

- Charts and incidents built around latency and loss. A ping has no useful "duration", so the view doesn't lead with one.

## Settings

- Ping Count : packets per check, 1 by default and up to 10. Send more to get a meaningful loss percentage.

- Packet Size , Timeout , and IPv4 or IPv6.

## Alerts

Probe Status is on and fires when the host doesn't answer at all. Packet Loss (above 50 %) and Ping Latency (above 200 ms) are optional warnings, one toggle away.

## Example

Your VPN gateway has no web page to check. A ping monitor sending 10 packets a minute shows 0 % loss and 12 ms for most of the day. When loss climbs to 60 % during the evening backup, the Packet Loss rule opens an incident, and the chart shows when it started and how long it lasted.

## Add one

Create a Ping (ICMP) monitor with a host name or IP address. See [Ping (ICMP)](/docs/monitors/network#ping-icmp). Today you can also run a one-off [ping test](/ping-test) first.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-05-09-ping-icmp-monitoring · Site guide: https://watchfor.io/llms.txt