> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/definitions/dora-metrics/change-failure-rate.md).

# Change failure rate

Change failure rate is the ratio of failed deployments to all deployments.

## Summary

Change failure rate is one of the DORA metrics and a key deployment health metric in Swarmia. The exact definition of a *change failure* is up to you. As a rule of thumb, it should be an incident that must be **remedied immediately** instead of waiting until the next regular deployment. If a deployment introduces a bug that doesn't need an immediate reaction, it probably shouldn't be defined as a change failure. Failed deployments (ie, when a deployment doesn't reach production) are not change failures either, at least as long as they don't cause a production incident.

Swarmia uses deployments as the basis for change failures. Deploys that fix other deploys (eg, [revert, rollback, hotfix](/features/metrics/track-dora-metrics/automatic-change-failure-detection.md)) mark the original deployment as a failure.

Change failure rate = change failures / total number of deployments

## Example

If you completed 20 deploys in a week, but 5 of those led to a change failure, you would have a change failure rate of 25%.

## Why it matters

A high change failure rate can indicate either an issue in your quality or deployment systems that needs to be improved.

## Benchmarks

* **Great:** < 5%
* **Good:** < 15%
* **Needs attention:** ≥ 15%

## How to use it

If you see an increase in your change failure rate, you might want to dig into the root cause with your team to help alleviate any issues in delivery.

## Where to find it

You can find the change failure rate (as well as the other DORA metrics) under [Metrics / DORA](https://app.swarmia.com/metrics/dora) or [Infrastructure / Deployments](https://app.swarmia.com/infrastructure/deployments).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/definitions/dora-metrics/change-failure-rate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.