Liveness Monitoring

Liveness monitoring sends periodic HTTP probes to your endpoints and tracks uptime, response times, and failure streaks — alerting you the moment something goes down.

Enabling liveness

Open an endpoint's detail page and toggle Enable Liveness Monitoring. Once enabled, probes begin immediately.

How it works

The liveness worker sends an HTTP GET request to the endpoint's full URL at regular intervals. A probe is considered successful if the server responds with a 2xx HTTP status code within the configured timeout (default 30 seconds). Non-2xx responses and timeouts are recorded as failures.

Uptime statistics

DomainOps calculates uptime percentages over two rolling windows:

24hUptime over the last 24 hours, expressed as a percentage of successful probes.
7dUptime over the last 7 days. Useful for spotting recurring issues.

The consecutive failures counter shows how many probes in a row have failed right now — a non-zero value means the endpoint is currently down.

Response times

Every probe records the round-trip response time in milliseconds. DomainOps stores daily aggregates (average response time, total tests, success rate) so you can spot performance trends over time.

Alerts

When liveness monitoring detects a failure, a liveness notification is triggered. By default, liveness notifications use the instant delivery class — meaning they are sent immediately rather than batched into a digest. Configure your delivery channels in Notifications settings.