Free calculator · Engineering

Benchmark your delivery against DORA's published performance levels

Answer the four software delivery questions from the DORA survey: deployment frequency, change lead time, change fail rate and recovery time. See which of DORA's four performance levels each answer is nearest, how 2025 respondents answered, and which metric to start with.

How this is calculated Related service: Cloud & DevOps

DORA metrics benchmark

Answer the four software delivery questions from the DORA survey for the main application or service your team works on. Each answer is matched to the nearest of DORA's four performance levels, and compared with how 2025 survey respondents answered.

01Deployment frequency

How often does your organisation deploy code to production or release it to users?

Fewer than once per six monthsBetween once per month and once every six monthsBetween once per week and once per monthBetween once per day and once per weekBetween once per hour and once per dayOn demand (multiple deploys per day)

02Change lead time

How long does a change take to go from committed code to running successfully in production?

03Change fail rate

Roughly what share of changes to production degrade service and need remediation, such as a hotfix, rollback, fix forward or patch?

04Failed deployment recovery time

When a change to production degrades service, how long does it usually take to restore it?

Your benchmark

Closest DORA performance level (2024 report)

Medium

3 of 4 metrics are nearest the medium level. The 2024 report put 35% of respondents at this level.

Medium performance level

Your answers. The last column is the share of 2025 survey respondents who gave the same answer or a better one (2025 report: State of AI-assisted Software Development 2025).
Metric	Your answer	Nearest level	Same or better (2025)
Deployment frequency	Between once per week and once per month	MediumTypical: Between once per week and once per month	76.1%
Change lead time	Between one day and one week	HighTypical: Between one day and one week	56.4%
Change fail rate	8% to 16%	MediumTypical: 10%	62.2%
Failed deployment recovery time	Less than one day	MediumTypical: Less than one day	56.5%

Start with deployment frequency

Your answer, “Between once per week and once per month”, sits furthest back: 76.1% of 2025 respondents gave the same answer or a better one. DORA's guides to start from: Continuous delivery, Deployment automation and Working in small batches.

Typical values by level (2024)

From the performance levels table in the Accelerate State of DevOps Report 2024: Accelerate State of DevOps Report 2024.
Level	Deployment frequency	Change lead time	Change fail rate	Recovery time	Respondents
Elite	On demand (multiple deploys per day)	Less than one day	5%	Less than one hour	19%
High	Between once per day and once per week	Between one day and one week	20%	Less than one day	22%
Medium	Between once per week and once per month	Between one week and one month	10%	Less than one day	35%
Low	Between once per month and once every six months	Between one month and six months	40%	Between one week and one month	25%

How this is calculated

You answer four questions from the DORA survey using its own answer options. Each answer is placed against the typical values in DORA's 2024 performance levels table and against the distribution of answers in its 2025 survey. No score or percentile is made up: every number shown comes from those two reports.

Step by step

Order each question's answers from worst to best. Deployment frequency, lead time and recovery time use the survey's six buckets; change fail rate uses the seven buckets the 2025 report publishes.
Place each performance level on the same scale. For the time-based metrics its typical value is one of the answers; for change fail rate it is the bucket that contains the 2024 typical percentage (5% elite, 20% high, 10% medium, 40% low).
Map each of your answers to the nearest level on that scale. When two levels are equally near, the lower one is used. Recovery in less than one day is typical of both high and medium, so it maps to medium.
Overall level: the level most of your four answers map to; ties go to the lower level.
For each answer, read the share of 2025 respondents who gave the same answer or a better one, as the report prints it.
Weakest metric: the answer with the largest share of respondents at the same level or better, which is the furthest from the front. The tool links DORA's capability guides for that metric.

Default assumptions

Assumptions marked adjustable can be changed in the calculator; the others are fixed parts of the model.

Default assumptions and their sources
Assumption	Default	Sources
Starting answer: deployment frequencyadjustable	Between once per week and once per month	[2]
Starting answer: change lead timeadjustable	Between one day and one week	[2]
Starting answer: change fail rateadjustable	8% to 16%	[2]
Starting answer: failed deployment recovery timeadjustable	Less than one day	[2]
Report the performance levels come from	2024	[1] [2]
Report the answer distributions come from	2025	[2]
Typical change fail rate, elite level	5%	[1]
Typical change fail rate, high level	20%	[1]
Typical change fail rate, medium level	10%	[1]
Typical change fail rate, low level	40%	[1]
Respondents at the elite level (2024)	19%	[1]
Respondents at the high level (2024)	22%	[1]
Respondents at the medium level (2024)	35%	[1]
Respondents at the low level (2024)	25%	[1]

What this doesn’t model

It is a self-assessment: the result is only as accurate as your answers, and it measures one application or service at a time.
The four levels come from the 2024 report, the most recent to publish them. DORA recalculates its clusters every year, so later data may place the same answers differently.
Deployment rework rate, the fifth DORA metric, isn't asked because no performance level was published for it.
The overall level counts metrics equally; it doesn't weigh throughput against stability for your product, which DORA says depends on what your users expect.
Nothing here estimates cost, hours or revenue.

Sources

DORA (Google Cloud), Accelerate State of DevOps Report 2024 (2024, version 2024.3). Accessed 9 Oct 2026. Performance levels table (report v. 2024.3, pp. 12–13): elite, high, medium and low clusters with typical change lead time, deployment frequency, change fail rate (5%, 20%, 10%, 40%) and failed deployment recovery time, and the share of respondents in each (19%, 22%, 35%, 25%).
DORA (Google Cloud), State of AI-assisted Software Development 2025 (2025, version 2025.2). Accessed 9 Oct 2026. Figures 11–14 (report v. 2025.2, pp. 19–20): the distribution of answers to the lead time, deployment frequency, failed deployment recovery time and change failure rate questions. The 2025 report groups teams into seven archetypes instead of four performance levels.
DORA, DORA Research Questions (2024). Accessed 9 Oct 2026. The survey wording of each software delivery performance question and its answer options.
DORA, DORA's software delivery performance metrics. Accessed 9 Oct 2026. Definitions of change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate.
IT Revolution (Forsgren, Humble and Kim), Accelerate: The Science of Lean Software and DevOps (27 March 2018). Accessed 9 Oct 2026. The book that introduced these delivery measures from the State of DevOps research.
DORA, Capabilities: Continuous delivery. Accessed 9 Oct 2026.
DORA, Capabilities: Deployment automation. Accessed 9 Oct 2026.
DORA, Capabilities: Working in small batches. Accessed 9 Oct 2026.
DORA, Capabilities: Trunk-based development. Accessed 9 Oct 2026.
DORA, Capabilities: Streamlining change approval. Accessed 9 Oct 2026.
DORA, Capabilities: Continuous integration. Accessed 9 Oct 2026.
DORA, Capabilities: Test automation. Accessed 9 Oct 2026.
DORA, Capabilities: Monitoring and observability. Accessed 9 Oct 2026.
DORA, Capabilities: Proactive failure notification. Accessed 9 Oct 2026.

Last reviewed 9 Oct 2026 by the QuantmHill engineering team. Found an error?

Link to or cite this tool

Writing about this topic? Link to the calculator or cite it. Its method, defaults and sources are all on this page, so readers can check the numbers.

Page link

Citation

QuantmHill. (2026). DORA metrics benchmark [Online calculator]. Last reviewed 9 Oct 2026. https://quantmhill.com/tools/engineering-velocity-and-dora-metrics-benchmark

Embed this calculator

You can put this calculator on your own site for free. Paste the code below where it should appear. It loads the same calculator in a frame, with a link back to this page for the full method and sources.

Embed code

<iframe src="https://quantmhill.com/embed/tools/engineering-velocity-and-dora-metrics-benchmark" title="DORA metrics benchmark by QuantmHill" width="100%" height="1650" loading="lazy" style="border:0;max-width:960px"></iframe>
<p>Calculator by <a href="https://quantmhill.com/tools/engineering-velocity-and-dora-metrics-benchmark">QuantmHill</a></p>

The credit line links to this page with the anchor text “QuantmHill”. You may edit it, add rel="nofollow" or remove it — the calculator works the same either way. Add ?theme=light or ?theme=dark to the iframe address to fix its colour scheme; otherwise it follows the visitor's system setting.

Optional auto-height script

<script>
window.addEventListener("message", function (e) {
  if (e.origin !== "https://quantmhill.com") return;
  var d = e.data;
  if (!d || d.source !== "quantmhill-embed" || typeof d.height !== "number") return;
  var frames = document.querySelectorAll('iframe[src^="https://quantmhill.com/embed/"]');
  for (var i = 0; i < frames.length; i++) {
    if (frames[i].contentWindow === e.source) {
      frames[i].style.height = Math.min(4000, Math.max(200, Math.ceil(d.height))) + "px";
    }
  }
});
</script>

Add this once per page, after the iframe, if you want the frame to grow and shrink with the calculator instead of using the fixed height above. It accepts messages from quantmhill.com only and resizes only the frame that sent them.

Frequently asked questions

DORA's software delivery performance metrics measure throughput (change lead time, deployment frequency and failed deployment recovery time) and instability (change fail rate and deployment rework rate). This benchmark uses the four that DORA's performance levels were built from; rework rate was added later and has no level to compare against.

From the performance levels table in DORA's Accelerate State of DevOps Report 2024. DORA finds the levels each year by cluster analysis of survey answers rather than setting them in advance. That report put 19% of respondents at elite, 22% at high, 35% at medium and 25% at low.

The 2025 DORA report replaced the four levels with seven team archetypes, built from delivery metrics together with measures such as burnout and product performance that four questions can't capture. The tool uses the 2025 report for what it does publish on delivery: how respondents answered each question.

Each answer maps to the level whose typical value is nearest on that question's answer scale. The overall level is the one most of your four answers map to. Ties go to the lower level, so a split result never overstates performance.

Because that's what DORA's 2024 data shows: the typical change fail rate was 10% for the medium level and 20% for the high level. The report notes that medium teams deployed less often but failed less, and that the best teams aim for steady improvement rather than a particular level.

For one application or service, take lead time from commit to running in production, count deployments over a few weeks, and count the deployments that needed a hotfix, rollback or patch. DORA's 2025 report says the most useful comparison is the same application over time, aiming for improvement rather than a particular level.

Want an engineer to check your numbers?

Send us your inputs and the decision you're weighing. We'll reply within one business day with an honest read on whether we can help.

Talk to an engineer

Your benchmark

Typical values by level (2024)

How this is calculated

Step by step

Default assumptions

What this doesn’t model

Sources

Link to or cite this tool

Embed this calculator

Frequently asked questions

What are the DORA metrics?

Where do the elite, high, medium and low levels come from?

Why not use the 2025 DORA report's levels?

How is my overall level chosen?

Why is a change fail rate of 8% to 16% shown as medium rather than high?

How should I measure my own answers?

Want an engineer to check your numbers?

Your benchmark

Typical values by level (2024)