# Recovery Time Objective \(RTO\)

A recovery time objective sets the maximum acceptable interval between a service disruption and restoration of an agreed usable service.

- Type: metric
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/recovery-time-objective/>)

## What it means

Recovery time objective, or RTO, is a target for how quickly service must be restored after disruption. It defines acceptable downtime for a specified workload and recovery scope. Unlike recovery point objective, which concerns recoverable data age, RTO concerns elapsed recovery time. A target is distinct from the capability demonstrated in an exercise.

## Why it matters

Clear recovery timing connects infrastructure choices to the consequences of an outage. It helps teams decide how much standby capacity, automation, staffing, and dependency preparation a service actually needs.

## When to use it

Define RTO for important workloads as part of business-impact and disaster-recovery planning. State what restored service means, including any acceptable degraded mode. Do not use a vendor’s component recovery claim as the end-to-end product target.

## How it works

1. Identify the tasks interrupted and how impact grows with downtime.
2. Agree on the recovery scope and maximum acceptable interval.
3. Budget time for detection, decisions, access, restoration, and validation.
4. Choose a recovery approach and align dependent systems’ objectives.
5. Exercise the full sequence, compare measured time with RTO, and address gaps.

## A practical example

A hypothetical subscription service targets restoration within two hours. An exercise restores servers in forty minutes but takes another ninety minutes to regain identity access and validate data. The team records that its end-to-end capability misses RTO and fixes those dependencies.

## Where it breaks

A lower RTO typically adds cost and operational complexity. Different incident types may need different strategies, and an exercise cannot reproduce every disaster. Annual availability percentages do not imply a specific maximum recovery time.

## Common mistakes

- Starting the clock only after responders begin restoring servers.
- Declaring success before customers can complete the agreed task.
- Promising a target that dependencies or staffing cannot support.

## Sources

1. [REL13-BP01 Define recovery objectives for downtime and data loss](<https://docs.aws.amazon.com/wellarchitected/latest/framework/rel_planning_for_recovery_objective_defined_recovery.html>) — Amazon Web Services · Official documentation
2. [Contingency Planning Guide for Federal Information Systems](<https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf>) — National Institute of Standards and Technology · Government guidance

## Related topics

- [Disaster Recovery](<https://wiki.soroush.uk/topic/disaster-recovery/>)
- [Recovery Point Objective \(RPO\)](<https://wiki.soroush.uk/topic/recovery-point-objective/>)
- [Runbook](<https://wiki.soroush.uk/topic/runbook/>)
