Ping Monitor
Ping monitors verify that a host responds to ICMP ping. They are useful for basic network reachability checks and for detecting when a host, router, or network path becomes unavailable.
Configuration
- IP or Host - Enter a hostname or IP address without a protocol.
- Request Timeout - The number of seconds to wait before a check fails.
- Schedule - How often checks run.
- Regions - One or more Testable-hosted or self-hosted runner regions.
Incident Detection
Ping monitors can require consecutive failures before opening an incident, consecutive successes before resolving it, and additional confirmation checks on different runners when possible.
Results
Check history shows timestamps, outcomes, and errors. Incident details include root cause, timing, affected regions, assertions, and traceroute details when execution data is available.
When to Use Ping
- Confirm that a host or network device is reachable.
- Check basic network path health before testing higher-level protocols.
- Monitor internal hosts from self-hosted runners.
Limitations
- Some hosts block ICMP even when services are healthy.
- A successful ping does not prove that a web app, API, database, or TCP service is working.
- Use HTTP or Port monitors when application or service behavior matters.
Examples
Host: example.com
Timeout: 30 seconds
Schedule: Every 5 minutes
Regions: AWS N. Virginia, AWS Oregon