Database · Lifecycle Status

Databases End of Life Dates

Database end-of-life is among the highest-risk EOL scenarios in any environment. Databases hold the most sensitive data, are often the most difficult to migrate, and are frequently overlooked in lifecycle audits because they remain stable and functional long after support ends.

Generated from our lifecycle dataset at every build · How we source data →

54
Total Products
553
End of Life
43
Warning
212
Active
amazon-aurora-mysql
Active
Amazon Aurora MySQL
4 versions tracked
Next EOL: 3 (MySQL 8.0) — Apr 30, 2028
amazon-aurora-postgresql
Mixed
Amazon Aurora PostgreSQL
8 versions tracked
Next EOL: 14 — Feb 28, 2027
amazon-documentdb
Active
Amazon DocumentDB
4 versions tracked
3 active versions
amazon-elasticache-redis
Mixed
Amazon ElastiCache for Redis
4 versions tracked
Next EOL: 6 — Jan 31, 2027
amazon-elasticsearch
Active
Amazon Elasticsearch Service
19 versions tracked
Next EOL: 7.10 — Nov 7, 2027
amazon-neptune
Mixed
Amazon Neptune
39 versions tracked
Next EOL: 1.2.1.2 — Dec 4, 2026
amazon-opensearch
Active
Amazon OpenSearch
17 versions tracked
Next EOL: 2.19 — Nov 7, 2027
amazon-rds-mariadb
Mixed
Amazon RDS for MariaDB
8 versions tracked
Next EOL: 10.6 — Dec 31, 2026
amazon-rds-mysql
Active
Amazon RDS for MySQL
20 versions tracked
Next EOL: 8.4.11 — Jul 31, 2029
amazon-rds-postgresql
Mixed
Amazon RDS for PostgreSQL
10 versions tracked
Next EOL: 14 — Feb 28, 2027
apache-cassandra
Active
Apache Cassandra
5 versions tracked
3 active versions
apache-couchdb
Active
Apache CouchDB
4 versions tracked
2 active versions
derby
All EOL
Apache Derby
3 versions tracked
All 3 versions past EOL
hbase
Active
Apache HBase
7 versions tracked
3 active versions
apache-lucene
Active
Apache Lucene
4 versions tracked
2 active versions
solr
Active
Apache Solr
9 versions tracked
2 active versions
arangodb
Active
ArangoDB
14 versions tracked
1 active version
azure-database-for-mysql
Mixed
Azure Database for MySQL
3 versions tracked
Next EOL: 8.0 — Jan 31, 2027
azure-database-for-postgresql
Mixed
Azure Database for PostgreSQL
8 versions tracked
Next EOL: 14 — Jan 31, 2027
clickhouse
Mixed
ClickHouse
22 versions tracked
Next EOL: 26.3 — Mar 26, 2027
cockroachdb
Mixed
CockroachDB
25 versions tracked
Next EOL: 26.3 — Feb 19, 2027
couchbase-server
Mixed
Couchbase Server
22 versions tracked
Next EOL: 7.6 — Mar 2027
duckdb
Mixed
DuckDB
7 versions tracked
Next EOL: 1.5 — Mar 1, 2027
elasticsearch
Active
Elasticsearch
12 versions tracked
Next EOL: 8.19 — Jul 15, 2027
foundationdb
Active
FoundationDB
3 versions tracked
2 active versions
h2
Active
H2 Database
2 versions tracked
1 active version
hazelcast
Active
Hazelcast Platform
11 versions tracked
Next EOL: 5.6 — Oct 15, 2027
heroku-postgres
Mixed
Heroku Postgres
8 versions tracked
Next EOL: 15 — Feb 28, 2027
hsqldb
Active
HSQLDB
3 versions tracked
3 active versions
ibm-db2
Mixed
IBM Db2
8 versions tracked
Next EOL: 11.5 — Apr 30, 2027
ibm-netezza
Active
IBM Netezza
13 versions tracked
5 active versions
influxdb
Active
InfluxDB
15 versions tracked
5 active versions
mariadb
Active
MariaDB
30 versions tracked
Next EOL: 10.11 — Feb 16, 2028
mariadb-connector-j
Active
MariaDB Connector/J
14 versions tracked
Next EOL: 3.5 — Sep 2031
meilisearch
Active
Meilisearch
57 versions tracked
1 active version
memcached
Active
Memcached
3 versions tracked
1 active version
mssql-jdbc
Mixed
Microsoft JDBC Driver for SQL Server
23 versions tracked
Next EOL: 10.2 — Jan 31, 2027
mssqlserver
Active
Microsoft SQL Server
36 versions tracked
Next EOL: 2017 'Helsinki' — Oct 12, 2027
mongodb
Active
MongoDB
33 versions tracked
Next EOL: 7.0 — Aug 31, 2027
mysql
Active
MySQL
23 versions tracked
Next EOL: 8.4 — Apr 2032
mysql-connector-j
Active
MySQL Connector/J
3 versions tracked
1 active version
neo4j
Active
Neo4j
73 versions tracked
Next EOL: 5.26 — Jun 6, 2028
opensearch
Active
OpenSearch
3 versions tracked
2 active versions
oracle-apex
Mixed
Oracle APEX
16 versions tracked
Next EOL: 24.1 — Dec 2026
oracle-database
Active
Oracle Database
12 versions tracked
Next EOL: 21c — Jul 2027
postgresql
Active
PostgreSQL
32 versions tracked
Next EOL: 15 — Nov 11, 2027
postgresql-jdbc-driver
Active
PostgreSQL JDBC Driver (pgJDBC)
8 versions tracked
8 active versions
redhat-data-grid
Active
Red Hat Data Grid
9 versions tracked
Next EOL: 8.6 — Dec 31, 2027
redis
Mixed
Redis
12 versions tracked
Next EOL: 8.0 — Dec 1, 2026
sqlite
Active
SQLite
3 versions tracked
1 active version
sqlite-jdbc
Active
SQLite JDBC
40 versions tracked
40 active versions
tarantool
Mixed
Tarantool
20 versions tracked
Next EOL: 3.3 — Nov 29, 2026
valkey
Active
Valkey
5 versions tracked
Next EOL: 8.0 — Sep 15, 2027
vitess
Warning
Vitess
12 versions tracked
Next EOL: 24 — Apr 30, 2027

Why Database EOL Is High Risk

An EOL database continues to function normally — queries execute, data persists, applications operate. This functional stability is exactly what makes database EOL so dangerous. There is no visible signal that the system is accumulating unpatched vulnerabilities. Security teams often discover EOL databases only after a breach, not before.

MySQL 5.7 reached EOL in October 2023 and remains one of the most widely deployed database versions globally. MySQL 8.0 reached EOL in April 2026. Redis 6.x and 7.0 are both past end of life. These are not obscure versions — they are production workhorses running in environments of every scale.

Database migration carries real risk and complexity, but the risk of running EOL database software in production environments that handle sensitive data is greater. A phased migration approach — read replica on new version, validate, promote — reduces risk while ensuring continuity.

Related Categories