Explore documentation
  1. Welcome to Uptime 👋
  2. Frequently Asked Questions
  3. Monitoring
    1. Get started with monitoring
    2. Working with monitors
    3. Customizing monitors
      1. Naming monitors
      2. Check frequency
      3. Request timeout
      4. Confirmation and recovery period
      5. Domain expiration checks
      6. SSL certificate checks
      7. Locations and regions
      8. Request parameters, headers and HTTP authentication
      9. Github badge
    4. Monitor types
  4. On-call scheduling and alerting
    1. Get started with on-call
    2. Sending alerts to Slack ↗
    3. Connecting external calendars
    4. Advanced on-call setup
  5. Incidents
    1. Working with incidents
    2. Create incidents manually
    3. Post mortems
    4. Incident silencing
    5. Incident metadata
  6. Status pages
    1. Get started with status pages
    2. Working with status pages
  7. Integrations
    1. Integrating with Better Stack
  8. Team and account management
    1. Team management
    2. Account settings
    3. Audit logs
  9. API
    1. Get started with API
  10. Monitors API
    1. Monitors
    2. Monitor groups
    3. Heartbeats
    4. Heartbeat groups
  11. On-call & Incidents API
    1. On-call calendar
    2. Escalation policies
    3. Severities
    4. Incidents
    5. Comments
  12. Integrations API
    1. New Relic Integrations
    2. Datadog Integrations
    3. AWS CloudWatch Integrations
    4. Azure Integrations
    5. Google Monitoring Integrations
    6. Grafana Integrations
    7. Prometheus Integrations
    8. Email integrations
    9. Incoming webhooks
    10. Splunk On-Call integrations
    11. PagerDuty Integrations
  13. Status pages API
    1. Status pages
    2. Status page sections
    3. Status page resources
    4. Status page reports
    5. Status page report updates
  14. Other API
    1. Metadata

Confirmation and recovery period

The confirmation period states how long we wait after observing a failure before we start a new incident.

The recovery period states how long a monitor has to be up before we automatically mark it as recovered, and the related incident as resolved.

Example

To better understand how this works, let's take a monitor with a 30-second check frequency, immediate confirmation period, and 1-minute recovery period.

When this monitor observers a downtime, it will create an incident immediately, as the confirmation period is set to an immediate start. If the next check that comes after 30 seconds shows the monitor as available (up and working), it will start the confirmation period countdown. This will take 60 seconds, during which 2 additional checks are performed, and both need to be valid in order for the incident to resolve automatically.

If any of the checks fails during the recovery period, the counter is reset and the monitor is waiting once more for a valid check to start the recovery period again.

To change the confirmation or recovery period, go to Monitors → Select a monitor → Configure → Advanced settings and set the dropdown to your preferred period.

Previous article

Request timeout

Next article

Domain expiration checks