Load Balancer

HAProxy Releases

Track HAProxy releases and LTS version lifecycle. Version feature comparison, upgrade paths between LTS branches, performance context, and production hardening guidance.

Official Site Documentation

—

Total Versions

—

Supported

—

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

2.2 LTS

2.4 LTS

2.6 LTS

2.8 LTS

2.9 dev

3.0 LTS

3.1 dev

2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active / LTS

Maintenance

Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

2.4 LTS 2.8 LTS Low-Medium Difficulty

Est. 1-2 hours

Breaking Changes

Stick table replication protocol updated
Some deprecated keywords removed
Default SSL/TLS settings tightened (TLS 1.2 minimum)
Stats socket command output format changes
New thread model (improved but may affect custom Lua scripts)

Migration Notes

LTS-to-LTS upgrades within the 2.x series are manageable. Review the CHANGELOG for removed keywords, test your config with haproxy -c, and check any Lua scripts or Data Plane API integrations. The upgraded SSL defaults are the most common surprise.

2.8 LTS 3.0 LTS Medium Difficulty

Est. 2-4 hours

Breaking Changes

Major version bump: stricter config validation
Removed long-deprecated keywords
Thread model changes (fully threaded by default)
Updated QUIC implementation (may require config adjustments)
New logging subsystem with structured logging support
Stats page UI redesigned

Migration Notes

The 2.x to 3.0 jump is the biggest upgrade in years. The config language is backward compatible for most setups, but the stricter parser will reject configs that previously worked with warnings. Run haproxy -c on your config against the 3.0 binary first. If you use QUIC, review the updated directives.

2.x (any) 3.0 LTS Medium-High Difficulty

Est. 4-8 hours

Breaking Changes

All breaking changes from intermediate versions accumulate
Multiple deprecated keywords removed at once
Thread model, SSL, and logging all changed

Migration Notes

If jumping multiple LTS versions, do it in one step to 3.0 but budget extra testing time. Read the full migration notes for every version you skip. Use a staging environment with production traffic replay (HAProxy can tee traffic) to validate.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version	EOL Risk	CVE Risk	Ecosystem	Cloud Support	Overall	Recommended Action
HAProxy 2.2 LTS	Critical	High	EOL	Degrading	Critical	EOL Apr 2025 — upgrade to 2.8 or 3.0 LTS
HAProxy 2.4 LTS	High	Medium	Maintenance	Full	High	Nearing EOL (Apr 2026) — plan upgrade
HAProxy 2.6 LTS	Medium	Low	Supported	Full	Medium	Supported until Apr 2027 — upgrade when convenient
HAProxy 2.8 LTS	Low	Low	Active	Full	Low	Actively maintained — safe for production
HAProxy 3.0 LTS	None	Low	Active	Full	Low	Current LTS — recommended for new deployments
HAProxy 3.1 dev	Medium	Low	Active	Partial	Medium	Development branch — do not use in production

HAProxy LTS branches receive 5 years of critical fixes. Non-LTS branches are short-lived. Risk assessed March 2026.

HAProxy LTS Feature Comparison

Side-by-side feature differences across major versions.

Feature	2.4 LTS	2.6 LTS	2.8 LTS	3.0 LTS
HTTP/3 (QUIC)	No	Experimental	Improved	Production-ready
Fully threaded model	Partial	Partial	Improved	Default
Structured logging	No	No	No	Native
OpenTelemetry tracing	No	No	Experimental	Stable
SSL/TLS default minimum	TLS 1.0	TLS 1.2	TLS 1.2	TLS 1.2
Prometheus metrics export	Basic	Improved	Enhanced	Enhanced
Stick table enhancements	Basic	Improved	Improved	Enhanced
Data Plane API compat	2.x	2.x	2.x	3.x
Lua 5.4 support	5.3	5.3	5.4	5.4
Max concurrent connections	~200K	~300K	~500K	~1M (tuned)

Embed Badges

Add live HAProxy status badges to your README, docs, or dashboard.

Health Status

Overall support health

![HAProxy Health Status](https://img.releaserun.com/badge/health/haproxy.svg)

EOL Countdown

Next end-of-life date

![HAProxy EOL Countdown](https://img.releaserun.com/badge/eol/haproxy.svg)

Latest Version

Current stable release

![HAProxy Latest Version](https://img.releaserun.com/badge/v/haproxy.svg)

CVE Status

Known vulnerabilities

![HAProxy CVE Status](https://img.releaserun.com/badge/cve/haproxy.svg)

Frequently Asked Questions

Common questions about HAProxy releases and lifecycle.

What is HAProxy's LTS support model?

HAProxy releases a new LTS branch roughly every 2 years. Each LTS gets 5 years of critical bug fixes and security patches from HAProxy Technologies. Non-LTS (development) branches get about 1 year of active maintenance. Always run an LTS branch in production.

What is the difference between HAProxy Community and Enterprise?

HAProxy Community is the open-source load balancer. HAProxy Enterprise (from HAProxy Technologies) adds a management console, advanced WAF, bot protection, real-time dashboards, and commercial support. Enterprise licensing is per-instance. For straightforward L4/L7 load balancing, Community is more than capable.

How does HAProxy compare to Nginx for load balancing?

HAProxy was purpose-built for load balancing and proxying. It consistently outperforms Nginx at high connection counts (100K+) and has more granular health check options, stick tables for session affinity, and detailed statistics. Nginx is a web server that also does proxying. If your primary need is load balancing, HAProxy is the better fit. If you also need to serve static files, Nginx might be simpler.

Does HAProxy support HTTP/3?

HAProxy 2.6+ includes experimental QUIC/HTTP3 support, and it matured significantly in 2.8 and 3.0. As of 3.0, QUIC frontend listeners are considered production-ready for most use cases. You need to compile with QUIC support enabled (USE_QUIC=1) or use the quic-enabled packages from haproxy.org.

How do I perform a zero-downtime HAProxy upgrade?

HAProxy supports seamless reloads: send SIGUSR2 or use systemctl reload. The new process takes over the listening sockets while the old one finishes existing connections. For major version upgrades, test your config with haproxy -c -f /etc/haproxy/haproxy.cfg first, then do a rolling upgrade if running multiple instances behind a VIP.

What is the HAProxy Data Plane API?

The Data Plane API is a REST API for dynamic HAProxy configuration without reloads. It can add/remove backends, servers, and ACLs at runtime. It ships as a sidecar process alongside HAProxy. Useful for service discovery integration and auto-scaling scenarios.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.