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

Kong Gateway

Active
Server Software Latest Version: 3.9.1 Latest Release: Jun 4, 2025

Kong Gateway is a cloud-native, platform-agnostic API gateway for managing and securing APIs.

Versions

11

Latest Version

3.9.1

Active Support

2

EOL

9

Lifecycle Timeline

Today
3.9
3.9
3.8
3.8
3.7
3.7
3.6
3.6
3.5
3.5
3.4
3.4
3.3
3.3
3.2
3.2
3.1
3.1
3.0
3.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.9Dec 12, 2024-No3.9.1No
Active
3.8Sep 9, 2024-Dec 12, 20243.8.1No
EOL
3.7May 28, 2024-Sep 9, 20243.7.1No
EOL
3.6Feb 9, 2024-May 28, 20243.6.1No
EOL
3.5Nov 8, 2023-Feb 15, 20243.5.0No
EOL
3.4Aug 9, 2023-No3.4.2
Yes
Active
3.3May 18, 2023-Aug 9, 20233.3.1No
EOL
3.2Feb 20, 2023-May 18, 20233.2.2No
EOL
3.1Dec 6, 2022-Feb 21, 20233.1.1No
EOL
3.0Sep 12, 2022-Dec 9, 20223.0.2No
EOL
2.8Mar 1, 2022-Jun 24, 20242.8.5
Yes
EOL

Frequently Asked Questions

Which versions of Kong Gateway have reached end of life?
The following Kong Gateway versions have reached end of life and no longer receive security updates: 3.8, 3.7, 3.6, 3.5, 3.3, 3.2, 3.1, 3.0 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Kong Gateway 3.8?
Kong Gateway 3.8 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 Kong Gateway?
The latest version of Kong Gateway is 3.9.1, released in the 3.9 release cycle.
How many versions of Kong Gateway are currently supported?
Kong Gateway currently has 2 actively supported version(s): 3.9, 3.4.
When does Kong Gateway 3.9 reach end of life?
Kong Gateway 3.9 does not have a specific end-of-life date announced yet.
What should I do when Kong Gateway reaches end of life?
When a Kong Gateway 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.