IT infrastructure calculators

Elasticsearch End of Life Dates

Release, end of support and end of life dates for every tracked Elasticsearch 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: 12 versions tracked; 3 supported, 0 security fixes only, 0 ending within 90 days, 9 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 ->

VersionStatusReleasedSupport endsLatest
9.5Supported2026-08-04Not announced9.5.5
9.4Supported2026-05-05Not announced9.4.8
9.3End of life2026-02-032026-08-049.3.8
9.2End of life2025-10-232026-05-059.2.8
9.1End of life2025-07-292026-02-039.1.10
8.19Supported2025-07-292027-07-158.19.23
8.18End of life2025-04-152025-10-218.18.8
9.0End of life2025-04-152025-10-239.0.8
8.17End of life2024-12-122025-08-128.17.10
8.16End of life2024-11-122025-04-158.16.6
7End of life2019-04-102026-01-157.17.29
6End of life2017-11-142022-02-106.8.23

Frequently asked questions

Which Elasticsearch versions are still supported?

Using the dates stored here, status calculated for 2026-11-04 shows 3 of 12 tracked Elasticsearch versions are still in support (9.5, 9.4, 8.19). The table above shows the calculated status of every tracked version; retained values may still need vendor confirmation.

What is the newest Elasticsearch version tracked here?

9.5 (latest update 9.5.5), released 2026-08-04. 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 Elasticsearch 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.

Planning notes

Elastic's published policy gives each major release maintenance for the longer of 30 months from its general availability or 18 months from the general availability of the next major release. Within that window, Elastic maintains the two most recent minor releases of the current major release, plus the final minor release of the previous major release.

Support lasts for the maintenance term plus six months after it. In practice that means you cannot sit on an old minor release of the current major version and expect fixes: only the newest two minors get maintenance. The table above lists the dates the data source tracks for each version.

Before a major upgrade, check the vendor's upgrade guidance for the version you are on, take a snapshot of your indices, and test the new version against a copy of your data. Client libraries and plugins have to match the server's major version.

Sources: Elastic end of life 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.