> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/using-hivel/cockpit/metrics-and-definitions/quality/hotfix-resolution-time.md).

# Hotfix Resolution Time

<div data-with-frame="true"><figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FBrQn6Tg6eYJv8YTvy08c%2FScreenshot%202025-11-28%20at%2012.24.15%E2%80%AFPM.png?alt=media&amp;token=be433cac-7047-4ab3-a95b-0a59d494a7b0" alt="" width="563"><figcaption></figcaption></figure></div>

**Hotfix Resolution Time** is the average time taken to recover from a failure in production.

On Hivel, it is measured as the **average cycle time of a Pull Request (PR) labeled as a hotfix**. In other words, the time taken for a hotfix PR from the first commit to when it is merged to the release branch.

#### Industry Benchmarking

<div data-with-frame="true"><figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FXnQeU2Fzr1DLaskWeiyO%2Fimage.png?alt=media&amp;token=0a9daee2-2c69-4e8a-8e27-760527be8c33" alt="" width="563"><figcaption></figcaption></figure></div>

#### Related article

{% content-ref url="/pages/zyXjINVbAvIleOyOMoP5" %}
[Strategies to Reduce Hotfix Resolution Time](/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time.md)
{% endcontent-ref %}

{% content-ref url="/pages/qvT5Y70xU01sAD0knK62" %}
[Building a feedback loop for continuous code improvement](/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement.md)
{% endcontent-ref %}