Home Resources OEM EOSL Calendar F5 Networks

OEM EOSL Calendar · F5 Networks

F5 Networks EOSL Calendar — every milestone date, every active model

F5 hardware support renewal pricing on BIG-IP iSeries is high relative to the value delivered on stable application-delivery workloads. TPM economics dominate at year +3 post-EoS for shops not actively consuming new TMOS / BIG-IP feature releases. WUC supports all F5 platforms below indefinitely post-LDoS.

11
F5 Networks products tracked
2
Reaching LDoS in next 12 months
0
Already post-LDoS (TPM-only)
11
Still under active OEM coverage

Data verified May 21, 2026 · Source: my.f5.com

Product calendar

F5 Networks products by family.

Each row shows full lifecycle milestones. Click a model to expand WUC commentary on TPM economics for that platform.

Past LDoS — TPM-only LDoS within 12 months Active OEM coverage

BIG-IP iSeries (7)

Model End of Sale EoSW Maint. EoVS Maint. LDoS Status
BIG-IP i2600 / i2800 Apr 30, 2024 Apr 30, 2028 Apr 30, 2028 Apr 30, 2029 Active
BIG-IP i4600 / i4800 Oct 31, 2024 Oct 31, 2028 Oct 31, 2028 Oct 31, 2029 Active
BIG-IP i5600 / i5800 Apr 30, 2024 Apr 30, 2028 Apr 30, 2028 Apr 30, 2029 Active
BIG-IP i7600 / i7800 / i7820 Apr 30, 2025 Apr 30, 2029 Apr 30, 2029 Apr 30, 2030 Active
BIG-IP i10600 / i10800 Apr 30, 2025 Apr 30, 2029 Apr 30, 2029 Apr 30, 2030 Active
BIG-IP i11600 / i11800 Apr 30, 2025 Apr 30, 2029 Apr 30, 2029 Apr 30, 2030 Active
BIG-IP i15600 / i15800 Apr 30, 2025 Apr 30, 2029 Apr 30, 2029 Apr 30, 2030 Active

BIG-IP rSeries (2)

Model End of Sale EoSW Maint. EoVS Maint. LDoS Status
BIG-IP r5800 / r10800 Apr 30, 2028 Apr 30, 2032 Apr 30, 2032 Apr 30, 2033 Active
BIG-IP r12800 / r15800 Apr 30, 2028 Apr 30, 2032 Apr 30, 2032 Apr 30, 2033 Active

VIPRION (2)

Model End of Sale EoSW Maint. EoVS Maint. LDoS Status
VIPRION 2400 Apr 30, 2022 Apr 30, 2026 Apr 30, 2026 Apr 30, 2027 LDoS soon
VIPRION 4480 / 4800 Apr 30, 2022 Apr 30, 2026 Apr 30, 2026 Apr 30, 2027 LDoS soon

How to use this calendar

The 30-day fleet review procedure.

If you maintain a F5 Networks fleet of any size, this four-step pass yields a 36-month refresh-and-TPM roadmap.

  1. 1

    Pull asset inventory

    Export your F5 Networks fleet from CMDB / spreadsheet / OEM portal. Minimum columns: serial number, model, install date, support contract end date.

  2. 2

    Map against this calendar

    Cross-reference each model against the table above. Flag every unit where LDoS lands within your refresh planning horizon (typically 18–36 months).

  3. 3

    Bucket by economics

    For each model bucket: refresh-now (year +1), refresh-soon (year +2), TPM-and-hold (LDoS +1 or beyond), evaluate-app-stack (LDoS dependent on application lifecycle).

  4. 4

    Cost-compare per bucket

    For TPM-and-hold gear, compare current OEM renewal cost vs WUC TPM quote vs replacement TCO. The math typically favors TPM at LDoS minus 12 months and beyond.

Run your F5 Networks renewal numbers against a real alternative.

Bring four data points to a 60-minute call and we'll map your F5 Networks fleet sequence:

  • Current F5 Networks asset count
  • Annual OEM maintenance spend
  • Contract anniversary distribution
  • Asset visibility state (CMDB, spreadsheet, none)

Reference data · Open to industry peers · Quarterly refresh cadence

Get a Custom Solution