Skip to content
ENExplore Calculators

Change Failure Rate Calculator

Calculate the DORA change failure rate from deployments that caused incidents.

About Change Failure Rate Calculator

Change Failure Rate (CFR) is one of the four key DORA metrics, measuring the percentage of deployments to production that result in a degraded service and require remediation (rollback, hotfix, patch). Formula: CFR = failed_deployments / total_deployments × 100. DORA's research-backed benchmarks classify teams as Elite (<5%), High (<10%), Medium (<15%) or Low (≥15%) performers based on this rate.

Formula

change_failure_rate = (failed_deployments / total_deployments) × 100

failed_deployments
Deployments that caused a failure requiring remediation
total_deployments
Total production deployments in the period

Worked example

With the default values below, Change Failure Rate Calculator returns Change Failure Rate of 6.67%. Change any input above and every figure here is recalculated in your browser.

Inputs used

Total Deploymentsaccepts 1–1,000,000 deployments
120 deployments
Failed Deploymentsaccepts 0–1,000,000 deployments
8 deployments

Results

Change Failure Rate
6.67%
DORA Performance Tier
High
Successful Deployments
112
Tier Threshold
High: 5% – <10%

Step by step

  1. 1Change Failure Rate: failed / total × 100= 6.67%
  2. 2Successful deployments= 112
  3. 3DORA performance tier= High

Assumptions and limits

  • The result is derived only from the 2 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax or fees or charges into account.
  • Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

What counts as a 'failed' deployment for CFR?

Any deployment that causes a service degradation requiring remediation — this includes rollbacks, hotfixes, patches, or incidents directly attributable to the change, not just deployments that technically failed to complete.

Why is a lower CFR better even at the cost of shipping less often?

DORA's research shows elite performers achieve both high deployment frequency AND low change failure rate simultaneously — the two aren't a tradeoff for high-performing teams, since better automated testing, smaller batch sizes and progressive delivery reduce failures while increasing speed.

How is CFR different from a bug count or defect rate?

CFR is scoped specifically to changes deployed to production that cause a production incident or require remediation, not all bugs found in QA or all defects reported by users — it's a delivery-pipeline health metric, not a general quality metric.

What's a good sample size for measuring CFR?

DORA benchmarks are typically measured over a rolling window of weeks to months with enough deployments (dozens or more) to avoid a single incident skewing the percentage disproportionately.

Related Calculators

Change Failure Rate Calculator | Calcrivo