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 websites and powers a significant portion of the world’s most visited ones.

Release Released Security Support Latest
2.8 (LTS) 1 year ago
(31 May 2023)
Ends in 3 years and 9 months
(01 Apr 2028)
(07 Sep 2023)
2.7 1 year and 7 months ago
(01 Dec 2022)
Ended 6 months ago
(01 Jan 2024)
(09 Aug 2023)
2.6 (LTS) 2 years ago
(31 May 2022)
Ends in 2 years and 8 months
(01 Apr 2027)
(09 Aug 2023)
2.5 2 years and 7 months ago
(23 Nov 2021)
Ended 1 year and 4 months ago
(14 Feb 2023)
(02 May 2023)
2.4 (LTS) 3 years ago
(14 May 2021)
Ends in 1 year and 8 months
(01 Apr 2026)
(19 Aug 2023)
2.3 3 years and 8 months ago
(05 Nov 2020)
Ended 2 years and 6 months ago
(01 Jan 2022)
(27 Jul 2022)
2.2 (LTS) 4 years ago
(07 Jul 2020)
Ends in 8 months and 4 weeks
(01 Apr 2025)
(19 Aug 2023)
2.1 4 years and 7 months ago
(25 Nov 2019)
Ended 3 years ago
(18 Mar 2021)
(18 Mar 2021)
2.0 5 years ago
(16 Jun 2019)
Ended 3 months ago
(01 Apr 2024)
(19 Aug 2023)
1.9 5 years ago
(19 Dec 2018)
Ended 3 years and 11 months ago
(31 Jul 2020)
(31 Jul 2020)
1.8 6 years ago
(26 Nov 2017)
Ended 1 year and 9 months ago
(01 Oct 2022)
(09 Dec 2022)
1.7 7 years ago
(25 Nov 2016)
Ended 2 years and 9 months ago
(01 Oct 2021)
(31 Mar 2021)

Release Cadence and Versioning

The HAProxy core team maintains multiple versions in parallel. Two major versions 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.

Fixes are backported to older releases with extreme care not to break anything. For this reason, it is highly recommended to stay on the latest version within a release cycle.

Support Policy

LTS: Branches with an even number are designated as “LTS” and are maintained for 5 years after their release. During this time they 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 perform upgrades too often but still want to receive fixes.

Stable: Branches with an odd number are only called “stable” and they are 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 problems. 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.

EOL dates on HAProxy website are formatted as YYYY-Qn, with YYYY being the year, and Qn the quarter of that year. This is intentional and more can be read about it on the HAProxy mailing list. This page takes a conservative approach, using the start of quarter as the EOL date (YYYY-01-01 for Q1, YYYY-04-01 for Q2, YYYY-07-01 for Q3, YYYY-10-01 for Q4). The EOL date will then be adjusted if a new version is released after that initial date.

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 :octocat: . 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 information. You can subscribe to the iCalendar feed at /calendar/haproxy.ics.