DORA Metrics Calculator
Calculate DORA metrics (deployment frequency, lead time, change failure rate, MTTR) and benchmark your DevOps performance against the 2024 DORA bands.
Deployments to production
Failed deployments needed a fix or rollback
Lead time commit to production
Recovery time after a failed deploy
Overall DORA level · 2024 bands
High
Lead time and recovery time hold you at High; deploy frequency and change fail rate are higher.
- Deploy frequency23/wk · Elite
- Lead time24 h · High
- Change fail rate5% · Elite
- Recovery time4 h · High
Your overall level is the lowest band any metric reaches.
Performance bands (DORA 2024)Where each metric sits, and what each band needs
Change fail rate and recovery time don’t separate High from Medium in the report; the Medium cut-offs here (30%, 1 week) fill that gap.
Deploy frequency
- Elite: On demand (multiple per day)
- High: Daily to weekly
- Medium: Weekly to monthly
- Low: Less than monthly
Lead time
- Elite: Less than 1 day
- High: 1 day – 1 week
- Medium: 1 week – 1 month
- Low: More than 1 month
Change fail rate
- Elite: ≤ 5%
- High: ≤ 20%
- Medium: ≤ 30%
- Low: More than 30%
Recovery time
- Elite: Less than 1 hour
- High: Less than 1 day
- Medium: Less than 1 week
- Low: 1 week or more
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| Deploy frequency | On demand (multiple per day) | Daily to weekly | Weekly to monthly | Less than monthly |
| Lead time | Less than 1 day | 1 day – 1 week | 1 week – 1 month | More than 1 month |
| Change fail rate | ≤ 5% | ≤ 20% | ≤ 30% | More than 30% |
| Recovery time | Less than 1 hour | Less than 1 day | Less than 1 week | 1 week or more |
Team scorecard imageA picture to drop into a retro or a team channel
Share your result
send it as a pictureDownload the card as an image, or copy the link — it opens with this card as a preview.
How it’s worked outOverall = your lowest metric band
- Deploy frequency = deployments ÷ (days ÷ 7). Change fail rate = failed ÷ total deployments.
- Each metric is placed in its band from the 2024 Accelerate State of DevOps Report, the most recent DORA report with Elite/High/Medium/Low bands.
- Overall is the lowest band any metric reaches, since DORA’s performance clusters need all four metrics together.
How this works: Method, 1 source,
How this works
Method
Deploy frequency is deployments ÷ (days ÷ 7) and change fail rate is failed ÷ total deployments; each of the four metrics is placed in its Elite, High, Medium or Low band from the 2024 DORA report, and the overall level is the lowest band any metric reaches. The report doesn’t separate High from Medium for change fail rate and recovery time, so the tool sets Medium at 30% or less and under 1 week.
Sources
- 2024 Accelerate State of DevOps Report (DORA, 2024)
Changes
- Added a printable report with the band ladder for each metric and what moves you up a band.
- Bands updated to the 2024 DORA report and the overall level is now your lowest band, with a band ladder per metric, what the next band needs and a shareable image.
- Results now update as you type, starting from a filled-in example.
- First published.
Frequently Asked Questions
What are DORA metrics?
DORA (DevOps Research and Assessment) metrics are key indicators of software delivery performance: Deployment Frequency, Change Lead Time (lead time for changes), Change Fail Rate, and Failed Deployment Recovery Time (formerly Mean Time to Restore, MTTR). The 2024 report added a fifth, Rework Rate, which has no performance bands yet. These metrics help organizations benchmark their delivery performance and identify areas for improvement.
Why are DORA metrics important?
DORA metrics provide objective measurements of DevOps effectiveness. Research shows that high-performing teams using these metrics ship faster, have lower failure rates, and recover more quickly. They enable data-driven decisions and help teams focus on what truly matters for software delivery.
How do I measure deployment frequency?
Count the number of successful deployments to production over a time period (daily, weekly, or monthly). Elite performers deploy multiple times per day, while low performers may deploy less than once per month. Track this in your CI/CD system or deployment platform.
What is a good lead time for changes?
In the 2024 DORA report, elite teams have change lead times under 1 day, high performers between 1 day and 1 week, medium between 1 week and 1 month, and low performers between 1 month and 6 months. Aim to reduce lead time by automating testing, improving build processes, and implementing trunk-based development.
How do I reduce change failure rate?
Focus on quality: implement comprehensive testing (unit, integration, E2E), use feature flags for gradual rollouts, improve monitoring and alerting, and establish rollback procedures. In the 2024 DORA report, elite teams had a change fail rate of about 5%.
How do I improve MTTR?
DORA now calls this metric failed deployment recovery time. Implement robust monitoring, create runbooks for common failures, establish clear incident response procedures, and conduct post-mortems to prevent recurrence. Elite teams recover from a failed deployment in under 1 hour.
What tools can help track DORA metrics?
CI/CD platforms (GitHub Actions, GitLab CI, Jenkins), deployment tools (Spinnaker, Argo CD), monitoring systems (Prometheus, Datadog, New Relic), and incident management tools (PagerDuty, Opsgenie) can all help track DORA metrics automatically.