Apache APISIX End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 3.20.0

Apache APISIX end of life (EOL) and end of support (EOS) dates: 26 Apache APISIX versions have reached EOL, including Apache APISIX 3.19 (EOL date: Nov 11, 2026) — no longer receiving security updates or patches. Apache APISIX 3.20.0 is the current supported release. Also see Apache ActiveMQ Artemis EOSL dates for related end-of-life information.

Apache APISIX end of life dates timeline — release schedule chart of the 8 most recent Apache APISIX versions, mapping security support windows against their EOL dates
Apache APISIX end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Apache APISIX releases of 27 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Apache APISIX EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Apache APISIX Releases - Active EOS/EOSL Support (1)

Release Released Security Support Latest LTS
3.20 (1 week and 4 days ago) Active 3.20.0 (1 week and 4 days ago) -

Apache APISIX End of Life (EOL) Releases - No Longer Supported (26)

Release Released Security Support Latest LTS
3.19 (1 month and 3 weeks ago) (1 week and 4 days ago) 3.19.0 (1 month and 3 weeks ago) -
3.18 (3 months ago) (1 month and 3 weeks ago) 3.18.0 (3 months ago) -
3.17 (5 months ago) (3 months ago) 3.17.0 (5 months ago) -
3.16 (7 months ago) (5 months ago) 3.16.0 (7 months ago) -
3.15 (9 months ago) (7 months ago) 3.15.0 (9 months ago) -
3.14 (1 year and 1 month ago) (9 months ago) 3.14.1 (1 year and 1 month ago) -
3.13 (1 year and 4 months ago) (1 year and 1 month ago) 3.13.0 (1 year and 4 months ago) -
3.12 (1 year and 7 months ago) (1 year and 4 months ago) 3.12.0 (1 year and 7 months ago) -
3.11 (2 years and 1 month ago) (1 year and 7 months ago) 3.11.0 (2 years and 1 month ago) -
3.10 (2 years and 3 months ago) (2 years and 1 month ago) 3.10.0 (2 years and 3 months ago) -
3.9 (2 years and 8 months ago) (2 years and 3 months ago) 3.9.1 (2 years and 6 months ago) -
3.8 (2 years and 10 months ago) (2 years and 8 months ago) 3.8.1 (2 years and 6 months ago) -
3.7 (3 years ago) (2 years and 10 months ago) 3.7.0 (3 years ago) -
3.6 (3 years and 1 month ago) (3 years ago) 3.6.0 (3 years and 1 month ago) -
3.5 (3 years and 2 months ago) (3 years and 1 month ago) 3.5.0 (3 years and 2 months ago) -
3.4 (3 years and 4 months ago) (3 years and 2 months ago) 3.4.1 (3 years and 4 months ago) -
3.3 (3 years and 6 months ago) (3 years and 4 months ago) 3.3.0 (3 years and 6 months ago) -
3.2 (LTS) (3 years and 8 months ago) (2 years ago) 3.2.2 (3 years and 4 months ago) LTS
3.1 (3 years and 10 months ago) (3 years and 8 months ago) 3.1.0 (3 years and 10 months ago) -
3.0 (4 years ago) (3 years and 10 months ago) 3.0.0 (4 years ago) -
2.15 (LTS) (4 years and 4 months ago) (3 years and 8 months ago) 2.15.3 (3 years and 8 months ago) LTS
2.14 (4 years and 5 months ago) (4 years and 4 months ago) 2.14.1 (4 years and 5 months ago) -
2.13 (LTS) (4 years and 8 months ago) (4 years and 3 months ago) 2.13.3 (4 years and 2 months ago) LTS
2.12 (4 years and 10 months ago) (4 years and 8 months ago) 2.12.1 (4 years and 9 months ago) -
2.11 (4 years and 11 months ago) (4 years and 10 months ago) 2.11.0 (4 years and 11 months ago) -
2.10 (LTS) (5 years and 1 month ago) (4 years and 7 months ago) 2.10.5 (4 years and 7 months ago) LTS

Is your Apache APISIX end of life date already behind you? In October 2026 only version 3.19 still receives fixes, so every older release needs an upgrade or paid help soon. This guide lays out the EOL dates of the open source API gateway, how its LTS rules work and what to check before you move. The cloud native gateway routes microservices traffic through plugins and a busy community, yet its support window stays short.

Apache APISIX End of Life Status Today

Apache APISIX keeps one line alive at a time. The latest release, 3.19.0, shipped on 28 September 2026, and on the same day 3.18 lost its security fixes. Anything older is unsupported, so a deployment on 3.17 or earlier runs without patches for new vulnerabilities. The project publishes no formal policy, so these dates are inferred from the release record across all versions.

Which Supported Release Numbers Still Get Fixes

Only the newest minor version is covered. Compare your number with the table, which lists a sample of lines in descending order.

VersionReleasedSecurity support endsStatus
3.1928 Sep 2026Still openCurrent
3.1820 Aug 202628 Sep 2026Ended
3.1410 Oct 20255 Feb 2026Ended
3.2 (LTS)6 Mar 202313 Nov 2024Ended
2.15 (LTS)22 Jul 20223 Mar 2023Ended

You can track the same data in a JSON endpoint, an RSS feed or the CPE identifier cpe:2.3:a:apache:apisix, while the source and tags live on GitHub.

Lifecycle and Release History: How the LTS Release Works

The Apache Software Foundation project has labelled some versions as long term since 2.10, but its documentation never promises a fixed window. The release history shows that an LTS release kept receiving patches for a while, yet no latest LTS release is in support today. Read the lifecycle as a rolling window, not a calendar.

Semantic Versioning in Practice

Apache APISIX follows semantic versioning: a minor bump such as 3.18 to 3.19 adds features, while a patch bump fixes defects. Upgrades inside 3.x rarely disturb stability, but the move from 2.x to 3.0 changed behaviours that needed careful versions testing.

Latest Release vs LTS: Which Line to Run

Run the newest line unless a freeze forces you to stay put. An older line gets less maintenance each month, and picking LTS today buys no extra time.

EOL Planning: Patch Releases, Security Fixes and Upgrades

Schedule your upgrade right after each minor drop, because patch releases and security fixes stop flowing to the previous line within weeks. Test in staging before production, and plan migration steps for the Admin API and SSL settings first.

Read the Changelog and New Features

Skim the changelog for each release between yours and the target. The new features in past versions include route-level mTLS, the loki-logger plugin for logging, OpenTelemetry tracing and full Wasm support.

Bug Fixes and Breaking Changes

Release notes group bug fixes as bugfixes and flag breaking changes separately. One example: version 2.13 stopped exposing each plugin API by default, so configuration had to bind it to a route.

Apache APISIX API Gateway Features Behind the Version Choice

Apache APISIX is a dynamic, high-performance, open-source gateway built on NGINX and etcd, so hot updates reach every node without a restart. It runs on Kubernetes or bare metal, which makes deployment flexible across infrastructure. Every capability below ships in the current line, so a gateway stuck past its end date misses both these additions and patches.

Plugins, Routing and Traffic Management

More than 100 plugins handle routing, traffic management, load balancing and rate limiting. Performance and scalability stay high, and Prometheus metrics plus a dashboard help you watch every route, API and traffic spike. Plugin behaviour can change between lines, which is why an unsupported plugin setup deserves a test before any upgrade.

Security, Observability and AI Gateway Protocols

Authentication plugins and observability exports protect and watch microservices, while the AI gateway proxies LLM requests. The proxy also speaks gRPC, WebSocket, Dubbo and MQTT, which eases operations. Once your version is past its end date, these exposed entry points stay unpatched, so that risk is the strongest reason to upgrade.

Open Source Self-Operation or Commercial Security Support

You can self-operate the gateway with full control, rely on the community, or buy commercial support from API7 for migration and fixes. An enterprise platform adds governance when many teams share gateways.

EOL dates of related software products