EOL.Wiki EOL.Wiki
← ← Back to all products

IBM MQ

Active
Middleware Latest Version: 9.4 Latest Release: N/A

IBM MQ is enterprise messaging middleware for reliable, secure message delivery between applications.

Versions

12

Latest Version

N/A

Active Support

2

EOL

10

Lifecycle Timeline

Today
9.4
9.4
9.3
9.3
9.2
9.2
9.1
9.1
9.0
9.0
8.0
8.0
7.5
7.5
7.1
7.1
7.0
7.0
6.0
6.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
9.4Jun 18, 2024-No-No
Active
9.3Jun 23, 2022-No-No
Active
9.2Jul 23, 2020-Sep 30, 2025-No
EOL
9.1Jul 23, 2018-Sep 30, 2023-No
EOL
9.0Jun 2, 2016-Sep 30, 2021-No
EOL
8.0Jun 13, 2014-Apr 30, 2020-No
EOL
7.5Jun 15, 2012-Apr 30, 2018-No
EOL
7.1Nov 1, 2011-Apr 30, 2017-No
EOL
7.0May 1, 2008-Sep 30, 2015-No
EOL
6.0May 1, 2005-Sep 30, 2012-No
EOL
5.3Jun 1, 2002-Sep 28, 2007-No
EOL
5.2Dec 1, 2000-Dec 31, 2003-No
EOL

Frequently Asked Questions

Which versions of IBM MQ have reached end of life?
The following IBM MQ versions have reached end of life and no longer receive security updates: 9.2, 9.1, 9.0, 8.0, 7.5, 7.1, 7.0, 6.0 (and 2 more). It is recommended to upgrade to a supported version.
Is it safe to continue using IBM MQ 9.2?
IBM MQ 9.2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of IBM MQ?
The latest version of IBM MQ is 9.4, released in the 9.4 release cycle.
How many versions of IBM MQ are currently supported?
IBM MQ currently has 2 actively supported version(s): 9.4, 9.3.
When does IBM MQ 9.4 reach end of life?
IBM MQ 9.4 does not have a specific end-of-life date announced yet.
What should I do when IBM MQ reaches end of life?
When a IBM MQ version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.