Alerts

After a check runs, evaluation rules decide whether to open, touch, or resolve an alert for that monitor kind (HTTP 5xx / timeout / network, SSL expiry, missing DNS records, and related cases). Alerts are an ops signal on top of checks — not a second probe engine.

• Open — failure matches an alert rule; at most one active alert per continuing failure window (touches do not re-notify).
• Acknowledge / resolve — operators can clear open alerts in the product; recovery on a later successful check can also resolve.
• Incidents — Pro+ can escalate into the incident desk; monitoring alerts and incidents are related but not identical.

Opened alerts can notify via email (and other channels when integrations are configured). Delivery is idempotent per alert recipient — retries use Trigger-backed notification workers. See Integrations.

Alerting and email notifications require Pro+. Free can run HTTP checks but does not get the full alert / notify surface. Continuous check → alert flow still depends on Trigger workers for scheduling and retries.

• Monitoring overview
• Health & Checks
• Incidents
• Status Pages