endoflife.ai
RabbitMQ RabbitMQ 4.1 RabbitMQ 4.4 EOL Checker

RabbitMQ 4.1 End of Life: Community Support Ended January 31, 2026

By Scott Bissett  ·  Published: November 21, 2026  ·  Reference guide  ·  Dates read on the day of publication from RabbitMQ's release information page, its Erlang version requirements page and its upgrade guide.

RabbitMQ 4.1 reached the end of community support on January 31, 2026, and commercial support for the 4.1 series ends on April 30, 2027. Both dates are on RabbitMQ's release information page, in the columns End of Community Support and End of Commercial Support. RabbitMQ 4.1 was released on April 15, 2025, so its community window lasted about nine and a half months. Since the community date, the 4.1 series is covered only for users who hold a commercial support licence.

The commercial date is indicative. RabbitMQ's page marks every End of Commercial Support date as indicative and says the official commercial support lifecycle is on the Broadcom support portal. The End of Community Support date is the open source project's own. On this site, the end-of-life date of a RabbitMQ series is its End of Community Support date, and the End of Commercial Support date is shown beside it.
Quick answer: RabbitMQ 4.1 reached end of life (EOL) on January 31, 2026. VMware Extended Commercial Support (paid) runs to April 30, 2027. Every RabbitMQ version's release and end-of-support date is on the RabbitMQ lifecycle page. Running a RabbitMQ version that is past end of life? See the support options on this page ↓

Key Dates at a Glance

Running RabbitMQ past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers RabbitMQ 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 →

RabbitMQ 4.x series and their support dates

SeriesReleasedEnd of Community SupportEnd of Commercial Support (indicative)
RabbitMQ 4.4October 20, 2026July 31, 2027October 31, 2028
RabbitMQ 4.3April 23, 2026January 31, 2027April 30, 2028
RabbitMQ 4.2October 27, 2025July 31, 2026June 30, 2030
RabbitMQ 4.1April 15, 2025January 31, 2026April 30, 2027
RabbitMQ 4.0September 18, 2024April 30, 2025September 30, 2026

Column names are RabbitMQ's own. The 3.x series are on our RabbitMQ page. The series that is still inside community support and closest to its date is 4.3: see RabbitMQ 4.3 end of community support.

What community support and commercial support mean

RabbitMQ's release information page uses two support terms and defines both in the legend under its support timeline.

The community support policy in the RabbitMQ server repository states the practical effect. Being covered by community support for a series means patch releases are produced regularly and are publicly available. For a series outside community support, the policy says patch releases, even if produced, are not made available to non-paying users, with a possible exception for very high severity CVEs.

The newest 4.1 release on RabbitMQ's public page is 4.1.8, dated January 22, 2026, nine days before the End of Community Support date. A 4.1 broker keeps running after that date. What changed is who can get later fixes for the 4.1 series: holders of a commercial licence.

Erlang/OTP versions RabbitMQ 4.1 runs on

RabbitMQ runs on Erlang/OTP, and each RabbitMQ release supports a set range of Erlang versions. The rows below are from the compatibility matrix on RabbitMQ's Erlang Version Requirements page.

RabbitMQ releasesMinimum required Erlang/OTPMaximum supported Erlang/OTP
RabbitMQ 4.427.029.x
RabbitMQ 4.2.927.027.x
RabbitMQ 4.1 (4.1.0 to 4.1.8)26.227.x

The same page gives a status for each Erlang series. It says Erlang 26 has reached end of life and is no longer supported, and its entry for the next series reads "Erlang 27 is supported." That leaves Erlang 27 as the one Erlang series inside the 4.1 range that RabbitMQ still lists as supported. A 4.1 node that is still on Erlang 26 is on an Erlang series RabbitMQ no longer supports.

Erlang 27 is also inside the range of RabbitMQ 4.2.9 and RabbitMQ 4.4. A cluster on Erlang 27 can therefore move from 4.1 to 4.4 without an Erlang change on the way. RabbitMQ's upgrade guide recommends using the latest Erlang version the target RabbitMQ version supports, which for RabbitMQ 4.4 is a 29.x release. RabbitMQ 4.2.0 to 4.2.8 share the 4.1 row, with 26.2 as the minimum.

The upgrade path from RabbitMQ 4.1

RabbitMQ 4.4 is the newest series. It was released on October 20, 2026 and its community support ends on July 31, 2027.

RabbitMQ's upgrade guide does not allow a rolling upgrade straight from 4.1 to 4.4. It says 4.1.x users must first upgrade to 4.2.x before a rolling upgrade to 4.3.x or 4.4.x. The supported rolling path is 4.1.x to 4.2.x, then 4.2.x to 4.4.x.

RabbitMQ 4.2 is a step on that path, not a place to stay on community support: its End of Community Support date is July 31, 2026. It does carry the latest End of Commercial Support date in the 4.x table, June 30, 2030.

What a RabbitMQ 4.1 owner should plan

  1. List every 4.1 broker. Include clusters inside containers pinned to a 4.1 image tag and brokers installed by another product. Record the Erlang/OTP version of each node as well.
  2. Decide: upgrade or commercial support. Without a commercial licence, 4.1 has been outside community support since January 31, 2026. With one, RabbitMQ's indicative date for 4.1 is April 30, 2027; confirm it on the Broadcom support portal, which RabbitMQ names as the official source.
  3. Put the nodes on Erlang 27 first. It is the Erlang series RabbitMQ lists as supported for 4.1, and RabbitMQ 4.2.9 and 4.4 require at least 27.0.
  4. Enable all stable feature flags. RabbitMQ's upgrade guide says all stable feature flags must be enabled before a rolling upgrade, or the upgrade may fail.
  5. Upgrade 4.1.x to 4.2.x, then 4.2.x to 4.4.x. Read the release notes of every series on the way. The upgrade guide also describes a blue-green deployment, a migration to a fresh cluster, as another way to move.
  6. Plan the next move as well. Community windows in the 4.x line are short. RabbitMQ 4.4's ends on July 31, 2027.

The EOL Checker looks up one product and version. The Stack Scanner reads a dependency file and reports the end-of-life dates of the components it recognizes.

Frequently Asked Questions

When did RabbitMQ 4.1 reach end of life?

Community support for RabbitMQ 4.1 ended on January 31, 2026. That is the date this site publishes as end of life for the 4.1 series. RabbitMQ lists a second, later date for 4.1: End of Commercial Support, April 30, 2027.

When does commercial support for RabbitMQ 4.1 end?

RabbitMQ's release information page lists End of Commercial Support for the 4.1 series as April 30, 2027. The page calls its commercial dates indicative and points to the Broadcom support portal for the official commercial support lifecycle.

Is RabbitMQ 4.1 still supported?

Only for users who hold a commercial support licence. RabbitMQ 4.1 has been outside community support since January 31, 2026. RabbitMQ's community support policy says patch releases for a series outside community support are not made available to non-paying users, with a possible exception for very high severity CVEs.

Which Erlang/OTP versions does RabbitMQ 4.1 support?

RabbitMQ's compatibility matrix gives the 4.1 series a minimum required Erlang/OTP of 26.2 and a maximum supported Erlang/OTP of 27.x. The same page says Erlang 26 has reached end of life and Erlang 27 is supported.

Can RabbitMQ 4.1 be upgraded directly to RabbitMQ 4.4?

Not by a rolling upgrade. RabbitMQ's upgrade guide says 4.1.x users must first upgrade to 4.2.x before a rolling upgrade to 4.3.x or 4.4.x.

What is the newest RabbitMQ series?

RabbitMQ 4.4, released on October 20, 2026. Its community support ends on July 31, 2027.

Related

© 2026 endoflife.ai · How we verify our dates · API · About