← Kris's Lab
Redline

Redline · Free tool by Kris McCabe

What does your downtime actually cost?

Most Disaster Recovery plans promise an RTO and RPO on paper. Few are ever tested against what a real incident takes, how much data it actually affects, or how far it runs past what the business can tolerate. Pick a scenario, or build your own.

Start from a scenario

Loads realistic phase timings, data volumes, and tolerance thresholds for that incident type. Everything stays fully editable.

Recovery Time Objective (RTO)

How long you've promised systems will be down, broken into the phases a real incident actually goes through.

/ hr
Lost revenue, idle staff, SLA penalties — per hour of outage
hrs
What's written in the DR plan or SLA
Sum of the phases below

Incident timeline phases

hrs
hrs
hrs
hrs
hrs

Business continuity tolerance

The point beyond a promised RTO where disruption stops being an SLA miss and becomes genuinely severe for the business — reputational, contractual, sometimes existential.

hrs
Beyond this, the business itself said it can't cope — from your BIA, if you have one

0 hrs 24 hrs
Within promise Over promise, within tolerance Beyond max tolerable

Gap beyond promise

0 hrs

Exposure cost

£0

Regulatory notification clock

Depends on where the data resides, what type it is, and your sector — not every organisation has one, and this isn't legal advice.
0%

Recovery Point Objective (RPO)

How much data you've promised you could lose, versus how much a real recovery in this scenario actually loses — priced by the volume of data actually at risk, not just elapsed time.

hrs
Maximum acceptable data loss, on paper
hrs
How far back the last clean recovery point really is
Whichever makes more sense for this system
records
How much data this incident actually affects, in total — not a rate, the real figure
/ record
Rework, lost transactions, compliance exposure per unit lost

Feeds into recovery time

More data to restore takes longer at any given throughput — this can push the Restore Execution step in the RTO section above higher than a manual guess would.

records / hr
How fast your tooling can actually restore this volume
Total data lost ÷ throughput
0 hrs 12 hrs

Gap beyond promise

0 hrs

Exposure cost

£0

Combined incident exposure

£0

What one real incident could cost you beyond what your DR plan says it should — based on the gap between promise and reality, weighted by data volume, above.

Know your numbers — now find out how ready you actually are to hit them.

Take the full readiness assessment in Recoverly →