Confirmation gives failures context
A failed check enters the monitor’s confirmation flow before becoming confirmed downtime. Review the resulting incident instead of treating every isolated observation as a separate outage.
Follow the path from failed check to confirmed incident, email alert and recovery. Keep the record after the immediate problem is over.
Fictional sequence. Animation timing is not check cadence or a performance promise.
A failed check enters the monitor’s confirmation flow before becoming confirmed downtime. Review the resulting incident instead of treating every isolated observation as a separate outage.
Configured email notifications report confirmed downtime and recovery. Failed send attempts are retried. Email is the supported notification channel; delivery time is not guaranteed.
Review when the incident began, how long it lasted and when the service recovered. Pair that timeline with response-time statistics to investigate the period around the failure.
In practice
Email notifications are supported for downtime and recovery. No Slack, SMS, Teams, Discord or PagerDuty integration is advertised or required.
Failed delivery attempts are retried. The incident history remains available independently of whether an email has reached your inbox.
Connect the context
Monitor availability, response time and downtime.
02Know when scheduled tasks stop checking in.
03Review uptime, response time, MTBF and MTTR.
Start monitoring
Add your first monitor and keep website availability, performance and incident history in one clear place.
7-day Starter trial · No credit card required · Starts with your first monitor