Apache HTTP Server End of Life Dates
Release, end of support and end of life dates for every tracked Apache HTTP Server version, with current status.
All products | Vendor lifecycle page | Source entry
Coverage note: some values are retained from earlier reviews. Unresolved releases or dates may be omitted; feed retrieval is not verification of every displayed value.
Status calculated for 2026-11-04: 4 versions tracked; 1 supported, 0 security fixes only, 0 ending within 90 days, 3 end of life. Calculated from the dates stored here, not a vendor verification date. With JavaScript on, the calculation uses today's date.
Swipe the table sideways to see all columns ->
| Version | Status | Released | Support ends | Latest |
|---|---|---|---|---|
| 2.4 | Supported | 2012-02-21 | Not announced | 2.4.70 |
| 2.2 | End of life | 2005-12-01 | 2017-07-11 | 2.2.34 |
| 2.0 | End of life | 2002-04-05 | 2013-07-10 | 2.0.65 |
| 1.3 | End of life | 1998-06-01 | 2010-02-03 | 1.3.42 |
Frequently asked questions
Which Apache HTTP Server versions are still supported?
Using the dates stored here, status calculated for 2026-11-04 shows 1 of 4 tracked Apache HTTP Server versions are still in support (2.4). The table above shows the calculated status of every tracked version; retained values may still need vendor confirmation.
What is the newest Apache HTTP Server version tracked here?
2.4 (latest update 2.4.70), released 2012-02-21. This is the newest release included here, not necessarily the newest vendor release. Unresolved releases may be omitted while their dates or support status are checked. See the linked vendor source for current releases.
Where do these Apache HTTP Server dates come from?
From the vendor sources linked at the top of this page (vendor lifecycle page) and the source entry. Vendors can revise dates, so confirm there before you schedule a migration.
Related tools
Planning notes
The Apache HTTP Server project develops one stable branch at a time, today the 2.4 line. Fixes and security patches arrive as new releases on that branch, so running the latest 2.4.x release is the way to have every fix the project has published.
The project no longer makes releases from older branches such as 2.2 and 2.0. If you run one of those, the only safe move is to the current 2.4 release.
Linux distributions (RHEL, Ubuntu, Debian) often ship an older-looking 2.4.x version with security fixes backported by the distribution. On those systems the version number alone does not tell you the patch level; check your distribution's security tracker.
Sources: Apache HTTP Server release policy.
Note: "Not announced" means no confirmed date is shown here; check the linked vendor source. "Ended (no date published)" means the source marks it ended without a date. Dates are compared as calendar days in your own time zone. A published end date counts as the last day of support.
Data: endoflife.date (MIT license), feed retrieved 2026-11-04. Retrieval does not mean every displayed value was verified that day. Some values are retained from earlier reviews, and unresolved releases or dates may be omitted. Confirm with the linked vendor source before a purchase or migration decision.