Statistics · 2026

Open source end-of-life statistics, 2026

endoflife.date tracks 9,234 release lines across 486 software products, and 79% of them are already end of life. 873 lines reached end of life in 2026 up to 28 October, and 568 more end in the next 12 months. Every figure below links to its source.

endoflife.date counts computed and support policies read on 28 Oct 2026; prices read on vendor pages on 26 Oct 2026. Compiled by OSSeva, which sells extended support for end-of-life open source.

Key statistics

  • endoflife.date tracks 9,234 release lines across 486 software products (endoflife.date API, 28 Oct 2026).
  • 7,301 of those 9,234 release lines (79%) are already end of life (endoflife.date API).
  • 873 release lines across 295 products reached end of life in 2026 up to 28 October (endoflife.date API).
  • 568 more release lines across 214 products reach end of life by 28 October 2027, 151 of them before the end of 2026 (endoflife.date API).
  • 1,267 release lines (14%) have no end-of-life date published at all (endoflife.date API).
  • The median release line that has ended was supported for 14.1 months from release to end of life (endoflife.date API).
  • 73 of 486 products (15%) list an extended or commercial support phase after standard end of life (endoflife.date API).
  • PostgreSQL supports each major version for 5 years (PostgreSQL versioning policy); Node.js LTS lines get 30 months (Node.js releases).
  • PostgreSQL 14 reaches end of life on 12 November 2026, and .NET 8 and 9 on 10 November 2026 (endoflife.date PostgreSQL, .NET).
  • AWS charges $0.100 per vCPU-hour for RDS Extended Support in years 1 and 2, $876 per vCPU a year, and $0.200 in year 3 (AWS, 26 Oct 2026).
  • OSSeva's EOL tracker lists 45 release lines across 12 technologies; 42 are past community end of life (EOL tracker).
  • OSSeva's CVE directory lists 481 verified CVEs; for 219 of them (46%), an affected line gets no upstream fix (CVE report).

How many software versions are end of life?

79% of the release lines on endoflife.date are past end of life. The site is a community-maintained lifecycle database covering open source and commercial software, so these figures describe software in general, not open source alone.

endoflife.date release lines, 28 Oct 2026
MeasureValueSource
Products tracked486endoflife.date API
Release lines tracked9,234endoflife.date API
Release lines end of life7,301 (79%)endoflife.date API
Lines that reached end of life in 2026, to 28 October873 across 295 productsendoflife.date API
Lines reaching end of life by 28 October 2027568 across 214 productsendoflife.date API
Lines with no end-of-life date published1,267 (14%)endoflife.date API
Median support window of ended lines14.1 monthsendoflife.date API
Products with an extended or commercial support phase73 (15%)endoflife.date API

By category

endoflife.date release lines by category, 28 Oct 2026
CategoryProductsRelease linesEnd of lifeMedian window (months)Ending by Oct 2027
Server applications1753,43086%12200
Operating systems681,20084%18.945
Devices211,20558%4369
Applications611,06286%7.748
Frameworks7394283%1349
Languages and runtimes3449077%6.622
Cloud and hosted services2545648%23.1111
Databases2744080%1824
Standards2967%520

Categories are endoflife.date's own. Median window is months from a line's release date to its end-of-life date, over lines that had ended by 28 October 2026. Source: endoflife.date API.

End-of-life statistics for widely deployed open source

PostgreSQL lines last longest among the databases here, at a median of about five years from release to end of life. Apache Kafka and Elasticsearch lines end fastest, at a median of about six months. endoflife.date lists no future end-of-life date for Kafka, ActiveMQ Classic or ZooKeeper.

Open source products on endoflife.date, 28 Oct 2026
ProductRelease linesEnd of lifeMedian window (months)Next line to reach end of life
PostgreSQL292460.714 on 12 Nov 2026 (source)
Microsoft .NET131024.78 and 9 on 10 Nov 2026 (source)
Redis12327.18.0 on 1 Dec 2026 (source)
MariaDB302512.213.0 on 31 Dec 2026 (source)
Spring Boot1715134.0 on 31 Dec 2026 (source)
PHP181436.58.2 on 31 Dec 2026 (source)
RabbitMQ1917124.3 on 31 Jan 2027 (source)
Kubernetes221914.61.35 on 28 Feb 2027 (source)
Apache Tomcat96102.69.0 on 31 Mar 2027 (source)
Node.js26238.222 on 30 Apr 2027 (source)
Django232016.16.0 on 30 Apr 2027 (source)
Erlang/OTP131036.227 on 20 May 2027 (source)
etcd8544.43.5 on 8 Jul 2027 (source)
Elasticsearch1296.38.19 on 15 Jul 2027 (source)
Spring Framework109277.0 on 31 Jul 2027 (source)
MongoDB Server332918.57.0 on 31 Aug 2027 (source)
Valkey50None ended yet8.0 on 15 Sep 2027 (source)
Python1813603.11 on 31 Oct 2027 (source)
Apache Kafka30255.7No date published (source)
Apache ActiveMQ Classic242110.8No date published (source)
Apache ZooKeeper6435.5No date published (source)

Ordered by the next end-of-life date. Each row is from that product's endoflife.date page; a product name links to OSSeva's support page where one exists. Check a single version on the EOL tracker.

Published support windows

Community support windows range from about 14 months for a Kubernetes minor release to 5 years for a PostgreSQL or Python release. Each is quoted from the project's own policy page.

Community support windows, read 28 Oct 2026
ProjectSupport windowWhat the policy saysSource
PostgreSQL5 years per major version"supports a major version for 5 years after its initial release"policy page
Python5 years per feature releaseBug fixes for 2 years, then security fixes only; "Five years after a release, support ends."policy page
.NETLTS 3 years, STS 2 years"LTS releases get free support and patches for three years." STS releases get two years.policy page
Node.js30 months for LTS linesLTS "typically guarantees that critical bugs will be fixed for a total of 30 months". From Node.js 27, every major line becomes LTS.policy page
KubernetesAbout 14 months per minor release12 months of standard support, then 2 months of maintenance mode, then end of life.policy page
Spring BootAt least 13 months per minor releaseMinor releases at least 13 months, or 25 months under a commercial subscription; major releases up to 3 years.policy page

What extended support costs

Four of the six extended-support offers below publish a price; two publish none. The full comparison, including how an OSSeva quote is built, is on the extended support pricing page.

Published extended support prices, read on vendor pages 26 Oct 2026
OfferWhat it extendsPublished pricePer year, full useSource
AWS RDS and Aurora Extended SupportRDS for PostgreSQL and MySQL past standard support$0.100 per vCPU-hour in years 1 and 2, $0.200 in year 3 (US East, Ohio)$876 per vCPU a year, then $1,752vendor page
Azure Database for PostgreSQLPostgreSQL 11 to 13 on Flexible Server; 14 from 1 Feb 2027$0.070 per vCore-hour (East US); billing for 11 to 13 started 1 Sep 2026$613.20 per vCore a yearvendor page
Canonical Ubuntu ProUbuntu LTS and the packages in the Ubuntu archive$500 per server (unlimited VMs) or $25 per workstation, per year$500 per physical servervendor page
TuxCare Extended Lifecycle SupportLinux distributions and six runtimes, including .NET and Node.jsUp to 10 systems $5,000, up to 100 $9,750, up to 250 $23,750 a year$95 to $500 per system when the band is fullvendor page
HeroDevs Never-Ending SupportNamed end-of-life application versionsNot published (custom pricing)Not publishedvendor page
OpenLogicSupport and long-term support for open sourceNot published (quote request only)Not publishedvendor page

The "per year" column is arithmetic on the published rate (8,760 hours or 12 months), not a vendor quote. Prices change; confirm with the vendor before you budget.

OSSeva's own counts

OSSeva's EOL tracker lists 45 release lines, and 93% of them are past community end of life. These counts are read from OSSeva's tracker and CVE directory each time this page is built.

OSSeva tracker and directory counts
MeasureValueSource
Release lines on OSSeva's EOL tracker45EOL tracker
Technologies those lines cover12EOL tracker
Tracker lines already past community end of life42 (93%)EOL tracker
Tracker lines reaching end of life within six months3EOL tracker
Version-level end-of-life pages87EOL pages, via the tracker
Open source technologies with an OSSeva support page34Technologies
CVEs in OSSeva's CVE directory, verified against the CVE API481CVE report
Of those, CVEs where an affected line gets no upstream fix219 (46%)CVE report

Method and sources

  • endoflife.date figures come from one download of its full product API on 28 Oct 2026. A line counts as end of life when endoflife.date marks it so. No third-party survey figures are used, because none could be checked against its data.
  • Support windows are quoted from each project's policy page, read on 28 Oct 2026.
  • Prices are the published list prices on OSSeva's extended support pricing page, read on each vendor's page on 26 Oct 2026. OSSeva publishes no price.

Questions

Frequently asked questions

Book a 15-minute call

What share of software release lines are end of life?

79%. Of the 9,234 release lines endoflife.date tracked on 28 Oct 2026, 7,301 were marked end of life. The share is high because every product keeps its old lines on record while only the newest few are supported.

How many software versions reach end of life in the next 12 months?

568 release lines across 214 products on endoflife.date reach end of life between 28 October 2026 and 28 October 2027, 151 of them before the end of 2026. PostgreSQL 14 (12 November 2026) and .NET 8 and 9 (10 November 2026) are among the first.

How long are open source versions supported?

It depends on the project. PostgreSQL and Python support each release for 5 years, .NET LTS for 3 years, Node.js LTS for 30 months, and Kubernetes for about 14 months. Across every release line on endoflife.date that has ended, the median support window was 14.1 months.

What does extended support for end-of-life software cost?

Where it is published: AWS RDS Extended Support costs $0.100 per vCPU-hour in years 1 and 2 ($876 per vCPU a year) and $0.200 in year 3; Azure Database for PostgreSQL charges $0.070 per vCore-hour; Ubuntu Pro is $500 per server a year. HeroDevs and OpenLogic publish no price. Prices were read on 26 Oct 2026.

Can I quote these statistics?

Yes. Cite the original source linked beside each figure, or cite this page as "OSSeva, Open source end-of-life statistics 2026". The endoflife.date figures were computed on 28 Oct 2026; OSSeva's own counts update when its tracker and CVE directory do.

Get a quote

Running a version on this list past its end-of-life date?

A 15-minute call establishes which of your versions still receive fixes and what covering the rest would involve.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call