Uptime monitoring
How FleetWP probes your sites, debounces flapping, and detects a silent agent.
FleetWP checks that each site is reachable and alerts you when it goes down or comes back.
How probing works
A cron worker runs HTTP checks against every monitored site and records each result. To avoid noisy alerts from a single blip, status transitions are debounced — a site has to stay in the new state across consecutive probes before FleetWP records it as down or recovered. The probe owns the uptime status; the heartbeat never overwrites it, which prevents a late heartbeat from swallowing a recovery.
Down and recovery alerts
When a site transitions down or recovers, FleetWP emits an uptime
alert to every channel you've enabled (see Notifications).
Silent-agent detection
Sometimes the website itself responds fine over HTTP, but the connector has gone
quiet (for example, wp-cron is starved). FleetWP catches this separately: the
uptime cron pulls a signed ping from the connector. If the site is up but
the agent doesn't answer, FleetWP raises an offline alert — once per episode —
and re-arms itself automatically on the next successful ping.
This is a pull, not a check of heartbeat age, so low-traffic or cron-starved sites don't produce false alarms.