features · icmp
Ping monitoring tool for hosts that speak ICMP, not HTTP
A ping monitoring tool sends ICMP echo requests to a host and alerts you when replies stop. AlertPing pings your servers every 30 seconds from three regions and tracks latency, packet loss and reachability over time.
interval
every 30 s
probe regions
FRA · IAD · SIN
tracked per probe
rtt · loss · reach
alert after
3/3 confirm · <10 s
the readout
Latency and packet loss, per region, every 30 seconds
Reachable is not the same as healthy. A database host answering pings at 400 ms with 6% loss is a problem HTTP checks never see. Ping checks catch degradation early, the same way our server monitoring tool watches whole machines from the outside, no agent installed.
If ICMP is blocked on your network edge, point a port monitoring check at the same host instead; both live in one dashboard.
alertping ▸ ping db-eu.acme.net
live
FRA Frankfurt icmp_seq=1–4 4/4 reply rtt 11.8 ms
IAD Virginia icmp_seq=1–4 4/4 reply rtt 88.4 ms
SIN Singapore icmp_seq=1–4 4/4 reply rtt 171.2 ms
packet loss 0% · worst rtt 171.2 ms · verdict UP
next probe in 30 s▌
what a ping check watches
Three signals, one verdict
When replies stop, downtime alerts go out by SMS, email, Slack and webhook after 3-of-3 confirmation.
rtt
Latency, charted per region
Round-trip time from Frankfurt, Virginia and Singapore on every probe. A slow creep from 12 ms to 90 ms is visible days before users complain.
loss
Packet loss detection
Each check sends multiple echoes and records the drop rate. Sustained loss above your threshold raises an alert even while the host still technically answers.
reach
Reachability from 3 regions
One region timing out could be a bad route. All three timing out is an outage. You only get paged for the second one, so a flapping transit link never wakes you.
ping questions
Quick answers
What can I monitor with ping checks?
Anything with a public IP that answers ICMP: servers, routers, firewalls, VPN gateways, load balancers, NAS boxes. If it replies to ping, AlertPing can watch it every 30 seconds.
What if my host blocks ICMP?
Use a TCP port check against the same host instead: SSH on 22, HTTPS on 443, or any custom port. It measures connect time rather than ICMP round-trip, and alerting works identically.
How is packet loss measured?
Every 30-second check sends a burst of echo requests from each region and records how many replies come back. Loss is tracked per region over time, so you can tell a bad transit route from a struggling host.
Know when a host stops answering
ICMP checks every 30 seconds from 3 regions, with latency and packet loss history and SMS alerts in every plan.