Application Delivery / Lifecycle / EoS / Budget Planning

BIG-IP Next ended 1 January 2026: are you about to buy Next and rSeries for the same job?

F5 discontinued BIG-IP Next (EoS January 1, 2026) and is modernizing TMOS instead — here is what it means for your platform refresh, licensing, and budget timing.

Quick Take

Quick Take: BIG-IP Next SKUs are End of Sale on 1 January 2026 (K000156713, 20.3 final). Replace the software path with TMOS 17.5 LTS through 2029, and refresh hardware to rSeries or VELOS before iSeries EoSS in 2026–2027. Do not double-buy Next plus rSeries. Lock quotes in 14 days; unused Next licenses can waste 25 percent of the refresh budget.

Next EoS Timeline

Quick Answer: F5 announced (Aug 2025) it would discontinue BIG-IP Next and modernize TMOS. Next 20.3 was the final release (EoL April 30, 2025); all BIG-IP Next SKUs reached End of Sale January 1, 2026. BIG-IP Next for Kubernetes and cloud-native network functions (CNF) continue under separate programs.

If your shortlist still mentions BIG-IP Next, or your iSeries estate is running 15.x/16.x toward EoTS, this guide is the budget sanity check. Related: rSeries specs, VELOS vs BIG-IP, SKU Lookup. Request a quote.

Event Date
Strategic update (discontinue Next)Aug 2025
BIG-IP Next 20.3 final release EoLApr 30, 2025
BIG-IP Next SKUs End of SaleJan 1, 2026
Next for Kubernetes / CNFContinues separately

Buyer implication: do not spec new BIG-IP Next licenses. If you evaluated Next as a “modern control plane”, the equivalent ongoing investment is TMOS 17.5/21.x + BIG-IQ (or F5OS for rSeries/VELOS).

TMOS Roadmap

Quick Answer: Active TMOS lines: 17.5.x LTS (support to Jan 2029, long-term stability), 21.0.x (Nov 2025, short-term), 21.1.x (May 2026, three-year support to May 2029). 16.1.x and 15.1.x hit EoTS in 2025 — estates on those versions face security-risk exposure unless upgraded.

Version First ship End of support Status
21.1.x (LTS)May 2026May 2029Current
21.0.xNov 2025Aug 2026Short-term
17.5.x (LTS)Feb 2025Jan 2029Current LTS
17.1.xMar 2023Mar 2027Maintained
16.1.xJul 2021Jul 2025EoTS
15.1.x—Dec 2024/2025EoTS

Budget both hardware and OS: 15.x/16.x → 17.5.x or 21.1.x is a version-gated refresh on most appliances; combine with the hardware lifecycle below for one project.

Risk note: F5 support covers only maintained versions. Estates on 15.x/16.x past EoTS face unpatched CVEs — this is the strongest argument to front-load the refresh in FY2026/27 budget.

Hardware Lifecycle

Quick Answer: Standard iSeries platforms from i2000 to i11000 reached end of sale on 1 January 2024, with hardware end of software support falling between 2026 and 2027. FIPS i5820-DF, i7820-DF and i15820-DF, TurboSSL i11400-DS to i11800-DS, and i15000 remain orderable exceptions. Replacement runs to rSeries appliances or VELOS chassis.

Platform EoS Hardware EoSS Replace with
i2000 / i4000 / i5000 / i7000 / i10000 / i11000 (standard)Jan 1, 20242026–2027r2000/r4000/r5000/r10000
i5820-DF / i7820-DF / i15820-DF (FIPS)ExceptionPer F5 lifecycleFIPS rSeries equivalents
i11400-DS / i11600-DS / i11800-DS (TurboSSL)ExceptionPer F5 lifecyclerSeries high-density
i15600 / i15800 (i15000)ExceptionPer F5 lifecycleVELOS CX410/CX1610
VIPRION (legacy chassis)EarlierRollingVELOS

iSeries FIPS exception SKUs remain useful for compliance, but plan them as bridge buys — F5 lifecycle policy pushes hardware to rSeries/VELOS for software support continuity.

Cost Drivers

Quick Answer: Refresh spend combines hardware replacement, operating system upgrade, module license migration, high availability pairing with optics, and installation. The largest hidden cost is moving 15.x or 16.x configurations to 17.5 LTS or 21.x and revalidating iRules and ASM policies, so budget 15 to 25 percent above bare hardware.

  1. Hardware: rSeries appliances or VELOS chassis/blades per tier
  2. OS migration: TMOS 15.x/16.x → 17.5.x LTS or 21.1.x (config + iRules + ASM policy revalidation)
  3. Licensing: module bundles per tenant; check term/subscription renewal timing to avoid overlap
  4. HA pair: two units + sync networking + failover testing
  5. Optics/PSU: 100G/400G transceivers and airflow variants where applicable
  6. Install: staging, cutover window, rollback plan
  7. Support: F5 premium + renewal on the new estate

Budget timing tip

F5 announced a price increase effective June 2026 — refresh quotes issued before that date lock list-price basis. Place orders before iSeries EoSS deadlines to avoid last-minute premium sourcing.

How to Replace BIG-IP Next After EoS

Quick Answer: Run six steps as one project rather than version-by-version drift: inventory every appliance version and end of support date, map tiers so i7800 moves to r7800 class and i15800 to VELOS, validate with F5 sizing against your cipher mix, quote with an end of sale gate, schedule the cutover, then retire.

Step 1 — Inventory

List every appliance: model, TMOS version, modules, EoSS date (K9476 compatibility matrix).

Step 2 — Map tiers

i5800-class → r5000-class; i7800-class → r7000/r10000-class; i11800-DS → r10000-class high density; i15800 → VELOS BX520.

Step 3 — Validate

F5 sizing tools + your cipher mix and concurrent TLS sessions; not “line rate” alone.

Step 4 — Quote & schedule

BOM risk-check via RFQ; schedule cutover before EoSS, ideally aligned with support renewal.

Frequently Asked Questions

Quick Answer: Will my iSeries stop working? No, but software support ends 2026–2027 for standard SKUs — security exposure grows. Should I buy FIPS iSeries now? Only as a short bridge; rSeries is the migration path. Is VE affected by Next EoS? No — VE continues on TMOS. Where to get refresh pricing?

Do not buy more BIG-IP Next SKUs after the 1 January 2026 End of Sale (K000156713). Stay on TMOS 17.5 LTS through 2029, or refresh hardware to rSeries or VELOS. Kubernetes Next is a different product line — confirm it is outside that EoS before you plan the cutover.

F5 published K000156713 (Advance EoS, 1 January 2026) and the TMOS-modernization note K000152956. This page is the refresh RFQ — iSeries EoSS versus rSeries or VE — so you size the cutover before opening those K articles. Confirm Next for Kubernetes is outside that EoS.

Hardware keeps running, but F5 stops software/security support on standard i2000–i11000 SKUs between 2026 and 2027. Unpatched CVEs and no hotfixes are the practical deadline for migration.

Only as a short compliance bridge. F5's lifecycle direction moves hardware to rSeries/VELOS, so new builds should size rSeries FIPS equivalents for longer software support.

No. BIG-IP Virtual Edition continues on the TMOS line (17.5.x / 21.x) with the same license model. The Next EoS only touches BIG-IP Next licenses, not VE.

BENQUAN GLOBAL LIMITED supplies F5 rSeries, VELOS, licenses, and support. Contact info@benquan.hk or request a quote.

Key Takeaway

Key Takeaway: BIG-IP Next SKUs went end-of-sale on 1 January 2026; F5 is investing in TMOS 17.5.x LTS through 2029 and rSeries and VELOS hardware. iSeries SKUs reach end-of-support in 2026-2027, with FIPS, TurboSSL and i15000 orderable as bridges. Budget hardware, OS upgrade and license migration as one project. BENQUAN GLOBAL LIMITED supplies F5 rSeries and VELOS systems with competitive pricing.

Not sure your BOM is optimal?

If you are unsure whether your BOM is optimal, click below for a free compatibility and delivery risk assessment. Fast global BOM validation and risk assessment.

Free Compatibility & Delivery Risk Assessment

Or call +852-21349834

Contents