Skip to main content
ICMP monitors require a target host. Additional options control packet count, timeout, and latency thresholds.
Define this in code. YAML format · Terraform

​
Config fields

FieldTypeRequiredDefaultDescription
config.hoststringYes—Hostname or IP address to ping
config.packetCountintegerNo3Number of ICMP packets to send (1–20)
config.timeoutMsintegerNo10000Ping timeout in milliseconds

​
Assertions

AssertionFieldsDescription
icmp_reachable(none)Passes if the host responds to at least one ping
icmp_response_timemaxMs (integer)Fails if average response time exceeds threshold
icmp_response_time_warnwarnMs (integer)Records degraded hint for elevated latency
icmp_packet_lossmaxPercent (number, 0–100)Fails if packet loss percentage exceeds threshold

​
Examples

​
Basic reachability

monitors:
  - name: Server ping
    type: ICMP
    config:
      host: server.example.com
    assertions:
      - type: icmp_reachable
        severity: fail

​
With latency and packet loss thresholds

monitors:
  - name: Core router
    type: ICMP
    config:
      host: 10.0.0.1
      packetCount: 10
      timeoutMs: 5000
    frequencySeconds: 30
    regions: [us-east, eu-west]
    assertions:
      - type: icmp_reachable
        severity: fail
      - type: icmp_response_time
        maxMs: 100
        severity: fail
      - type: icmp_response_time_warn
        warnMs: 50
        severity: warn
      - type: icmp_packet_loss
        maxPercent: 10
        severity: fail

​
Next steps

ICMP overview

When to use ICMP monitors.

Multi-region monitoring

Reduce false positives with multi-region checks.