What is change failure rate?
Change failure rate (CFR) is the percentage of deployments to production that result in a failure requiring remediation — a rollback, hotfix, or patch. It is one of the four DORA metrics and measures deployment quality rather than deployment frequency.
CFR = (Failed deployments ÷ Total deployments) × 100
A "failure" is any deployment that causes a degraded service experience requiring corrective action. This includes rollbacks, emergency patches, and hotfixes — but not planned feature flags or A/B tests.
DORA performance bands
| Band | Change failure rate | What it means |
|---|---|---|
| Elite | 0–15% | Strong testing and deployment practices |
| High | 16–30% | Good practices with room to improve |
| Medium | 31–45% | Significant quality gaps |
| Low | >45% | High deployment risk, unstable pipeline |
How to reduce change failure rate
The most effective levers are: comprehensive automated testing (unit, integration, and end-to-end), feature flags to decouple deployment from release, smaller and more frequent deployments (smaller changes have lower blast radius), and automated rollback on failed health checks.
Counterintuitively, increasing deployment frequency often reduces CFR over time — smaller deployments are easier to test and easier to diagnose when they fail.
CFR vs error budget
CFR measures deployment quality. Error budget measures service reliability. They are related but distinct: a low CFR means your deployments rarely cause incidents, but your service could still have reliability issues from infrastructure failures, traffic spikes, or third-party dependencies. Use both together for a complete reliability picture. See the Error Budget Calculator for the other side of this equation.