Link Search Menu Expand Document
Release Released Security Support Latest
2.6 (LTS) 4 months ago
(31 May 2022)
Ends in 4 years and 5 months
(01 Apr 2027)
2.6.6
2.5 10 months ago
(23 Nov 2021)
Ends in 2 months and 4 weeks
(01 Jan 2023)
2.5.9
2.4 (LTS) 1 year and 4 months ago
(14 May 2021)
Ends in 3 years and 5 months
(01 Apr 2026)
2.4.19
2.3 1 year and 11 months ago
(05 Nov 2020)
Ended 9 months ago
(01 Jan 2022)
2.3.21
2.2 (LTS) 2 years and 3 months ago
(07 Jul 2020)
Ends in 2 years and 5 months
(01 Apr 2025)
2.2.25
2.1 2 years and 10 months ago
(25 Nov 2019)
Ended 1 year and 6 months ago
(18 Mar 2021)
2.1.12
2.0 3 years ago
(16 Jun 2019)
Ends in 1 year and 5 months
(01 Apr 2024)
2.0.29
1.9 3 years and 9 months ago
(19 Dec 2018)
Ended 2 years ago
(31 Jul 2020)
1.9.16
1.8 4 years and 10 months ago
(26 Nov 2017)
Ended 4 days ago
(01 Oct 2022)
1.8.30
1.7 5 years and 10 months ago
(25 Nov 2016)
Ended 1 year ago
(01 Oct 2021)
1.7.14

HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic web sites and powers a significant portion of the world’s most visited ones.

The HAProxy core team maintains multiple versions in parallel. Since version 1.8, two major version are released every year. The first digit usually indicates a breaking change (config format etc) but in practice rarely changes. The second digit indicates new features. Both constitute a branch. One extra number appears after these digits to indicate the bug fix release.

The core team deploys a lot of efforts backporting fixes to older releases while being extremely careful not to break anything. For this reason, it is really important to stay up to date within one branch, i.e. having the highest possible number on the last digits.

Branches with an even number are called “LTS” (for “long term support”) and are maintained for 5 years after their release. During this time they will receive fixes for bugs that are discovered after the release. These branches are aimed at general users who seek extreme stability and do not want to qualify a new version too often but still want to receive fixes.

Branches with an odd number are only called “stable”, they’re aimed at highly skilled users who prefer to upgrade often to benefit from modern features, and who are also able to roll back in case of problem. These versions are maintained between 12 and 18 months. The duration is short and purposely not strict so that the maintenance cycle is decided with users based on feedback, and so that these versions do not end up in embedded products. It may happen that a few features are backported to these version if there is some reasonable demand and the operation is considered riskless enough.

More information is available on the HAProxy website.

You should be running one of the supported release numbers listed above in the rightmost column.

You can check the version that you are currently using by running:
haproxy -v

You can submit an improvement to this page on GitHub. This page has a corresponding Talk Page.

A JSON version of this page is available at /api/haproxy.json. See the API Documentation for more.

Latest releases on this page are automatically updated