endoflife.ai
RHEL RHEL 9 RHEL 10 EOL Checker

RHEL 9 Life Cycle: Full Support Ends May 31, 2027, Every Phase Dated

By Scott Bissett  ·  Published: September 28, 2026  ·  Reference guide  ·  Dates read from Red Hat's life cycle data on the day of publication and re-read at every site build; phase definitions quoted from Red Hat's life cycle page.

Red Hat Enterprise Linux 9, released May 18, 2022, leaves Full Support on May 31, 2027, leaves Maintenance Support on May 31, 2032, and can be covered by Extended Life Cycle Premium until May 31, 2036. Those are the three dates of the RHEL 9 life cycle. The first one is the one that changes day-to-day operations: after it, RHEL 9 gets no new minor releases, no new features and no new hardware enablement, only fixes.

Short version. RHEL 9 is safe to run for years, but it stops moving forward on May 31, 2027. Hardware bought after that date may not be enabled on RHEL 9. Plan the move to RHEL 10 around that date, not around the 2032 one, unless you have already decided to buy Extended Life Cycle Premium for RHEL 9.10.
Quick answer: The RHEL 9 end-of-life (EOL) date is May 31, 2032, the end of Maintenance Support. Full Support ends May 31, 2027. Every RHEL version's dates are on the RHEL lifecycle page.

The three phases, with Red Hat's own definitions

PhaseRHEL 9 datesWhat Red Hat says it delivers
Full SupportMay 18, 2022 to May 31, 2027Errata meeting the standard errata criteria as they become available, plus software enhancements, which Red Hat defines as new functionality beyond correcting defects or enabling existing functionality on a new hardware generation. Minor releases ship in this phase.
Maintenance Supportto May 31, 2032Errata meeting the standard errata criteria as they become available. Red Hat's policy states that new functionality and new hardware enablement are not planned for availability in this phase.
Extended Life Phaseafter May 31, 2032Continued access to previously released content on the Customer Portal, documentation and the Knowledgebase, and migration advice. Red Hat states that no bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase.
Extended Life Cycle Premium (ELCP), paidRHEL 9.10 to May 31, 2036Continued errata for an eligible minor release after standard support. ELCP replaces the older Extended Life Cycle Support offering, and provides an additional four years of extended support for the last minor release of RHEL 8, 9 and 10.

Sources: Red Hat's Red Hat Enterprise Linux Life Cycle page for the phase definitions, ELCP rules and Long-Life terms, and Red Hat's Product Life Cycle Data API for the dates, which our RHEL adapter re-reads at every build. The dates on this page are bound to that data, so they update if Red Hat revises them.

Running RHEL past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers RHEL is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Minor releases: the date that applies to your box

The major-version dates above are the outer envelope. Within it, each RHEL 9 minor release has its own support window, and the version you actually run decides whether you are receiving errata today. Red Hat ships minor releases roughly every six months during Full Support; an odd-numbered minor is supported only until the next minor ships, while even-numbered minors qualify for extended coverage:

The per-minor dates for RHEL 9.4, 9.6 and 9.7, and the answer to "is my minor still supported", are in our RHEL minor-version guide. The rule of thumb: if you are on an odd minor, you are on a short clock; if you are on an even minor without ELCP, your clock is the next even minor's release.

Why May 31, 2027 is the planning date

Nothing breaks on May 31, 2027. Security fixes continue for five more years. What ends is growth: no RHEL 9.11, no new features, and, in Red Hat's words, no new hardware enablement. For a fleet that refreshes servers on a three-to-five-year cycle, that is the constraint that bites first, because the hardware arriving in 2028 is qualified against RHEL 10, whose own Full Support runs to May 31, 2030. Leapp upgrades run one major at a time, 9 to 10, so a fleet still carrying RHEL 8 (Maintenance Support to May 31, 2029) has two hops to plan.

What to do

  1. Find your minors. cat /etc/redhat-release on each host, or your Satellite or Insights inventory. Separate odd minors (short clock) from even minors (ELCP-eligible).
  2. Decide per workload by how long it must run. Under a year past 2027: stay on RHEL 9 in Maintenance Support. One to five years: plan RHEL 10 for anything that needs new hardware or features, keep the rest on RHEL 9 until 2032. Beyond 2032: either RHEL 10, or RHEL 9.10 with ELCP to May 31, 2036 and Long-Life terms after that, which is a purchase decision with Red Hat, not a default.
  3. Check the stack on top. Middleware and databases have their own dates. Our pages for JBoss EAP, Satellite and OpenShift carry Red Hat's dates for each.
  4. Weigh the paths. Upgrade, Red Hat extended coverage, or third-party support: the trade-offs are in our RHEL decision guide.
What to do about it

RHEL currently carries an EOL Risk Score™ of 90/100 — Grade F, critical risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the RHEL lifecycle page.

The right response comes down to one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.

Guides: RHEL: upgrade, Red Hat ELS, or third-party?

Frequently Asked Questions

What is the RHEL 9 life cycle?

RHEL 9 was released May 18, 2022. Its Full Support phase ends May 31, 2027, its Maintenance Support phase ends May 31, 2032, and Extended Life Cycle Premium can cover the final minor release until May 31, 2036. After Maintenance Support the standard subscription enters the Extended Life Phase, which provides access to existing content but no new fixes.

When does RHEL 9 end of life happen?

The date most people mean by end of life is the end of Maintenance Support: May 31, 2032. Full Support, the phase with new features and minor releases, ends earlier, on May 31, 2027. Paid Extended Life Cycle Premium coverage of RHEL 9.10 can run to May 31, 2036.

Which RHEL 9 minor releases get extended support?

Red Hat's life cycle page lists RHEL 9.2, 9.4, 9.6, 9.8 and 9.10 as eligible for Extended Life Cycle Premium: the even-numbered minor releases. Each ELCP stream provides six years of support from the minor release's general availability date, and the terminal .10 release receives nine years.

Related