Every server, storage array and switch runs on a support clock the manufacturer sets, not you. When that clock stops, the vendor stops repairing the hardware and steers you toward a refresh. This guide explains the terminology, shows you how to find your own dates, and lays out what actually happens at end of service life.
Figures are indicative estimates shown as a range, based on the Gartner 50–70% saving band applied to an example spend, and confirmed by a free Servnet support audit — not a quotation. Third-party maintenance covers hardware break-fix and defers refresh; it does not supply software or firmware security patches.
EOS, EOL and EOSL: what the terms actually mean
Vendors use a chain of milestones. End of Sale (EOS) is when the product stops being sold new. End of Life (EOL) is when it leaves the active portfolio. End of Service Life (EOSL) is the one that bites: the point at which the OEM will no longer repair the hardware, ship spares, provide TAC assistance or issue updates. HPE, for example, publishes these dates for storage families such as MSA and Nimble, and its MSA end-of-life notice puts EOSL typically five years after the obsolescence date, so the gap between 'discontinued' and 'unsupported' can be substantial. For ProLiant servers, HPE sets support end dates per serial number rather than per model. Support withdrawal is a commercial lever, not a technical necessity.
Why OEMs withdraw support, and how to find your dates
Perfectly serviceable ProLiant Gen10 servers and MSA or Nimble arrays don't fail on their EOSL date; the OEM simply stops offering renewals so the economics push you toward new hardware. Post-warranty programmes like HPE Tech Care Basic exist, but they run only until HPE ends support for the product. To find your own dates, check the OEM's record first. HPE publishes end-of-life notices for storage such as MSA, Nimble and 3PAR in the HPE Support Center, and some need an HPE account sign-in. It lists HPE Aruba Networking end-of-support dates on the HPE Networking Support Portal, and shows ProLiant coverage end dates per serial number in Warranty Check. Cross-reference model and serial against your active Tech Care or Complete Care contract, then sanity-check against an independent EOSL database.
Your options at EOSL: refresh or extend with TPM
At end of service life you have two honest paths. Refresh means new hardware plus a new support agreement, spread over finance if it suits cash flow. Extend means keeping healthy kit running under third-party maintenance, typically at a large discount to OEM renewal pricing and often adding several supported years. Be clear on the trade-off: TPM covers hardware break-fix and spares, not vendor software or firmware security patches. For systems that must stay patched for compliance, refresh is the straight answer; for stable or non-critical estate, extension usually wins. Use the calculator above and our storage EOSL checker to see where you stand.
FAQs
Does hardware stop working when OEM support ends?
No. EOSL is a contractual and commercial line, not a technical failure point. A ProLiant server or MSA array runs exactly the same the day after its EOSL date as the day before. What changes is that the manufacturer will no longer repair it, supply spares or provide support, which is precisely the gap third-party maintenance is designed to fill.
How long after end of life does support usually last?
It varies by vendor and product, but a common pattern puts End of Service Life several years after End of Life. HPE's DL360 and DL380 Gen10, for instance, entered the end-of-life process on 1 May 2024, yet the August 2026 Service Pack for ProLiant still carried new System ROM firmware for both, and HPE sets their support end dates per serial number. Always confirm the exact EOSL date against the manufacturer's own lifecycle notice rather than assuming a fixed interval.
What does third-party maintenance not cover?
TPM covers hardware break-fix, replacement parts and engineer support to keep kit running past EOSL. It does not include the OEM's proprietary software updates or firmware security patches, since those remain the manufacturer's intellectual property. If a system carries compliance or security exposure that depends on ongoing patching, a refresh is the honest recommendation over extension.
How we work these figures out
- Saving band: Gartner, "Market Guide for Data Center and Network Third-Party Hardware Maintenance", 29 Aug 2019 (ID G00414695) — TPM contracts save 50–70% off OEM support NET prices. The report is dated; net-price basis (not off-list).
- Optional spend estimator seeds ONE editable per-device starting figure for HPE ProLiant: £1,250/yr, an indicative Servnet assumption rather than a quoted HPE price — replace it with your own renewal. Non-HPE OEM support pricing is quote-gated — enter your own renewal figure.
- EOSL life extension: the 3–5 (up to 7) additional years modelled are Servnet's planning assumption, not a published statistic; actual supportable life depends on spares availability for each model.
- All figures are indicative estimates shown as a range and confirmed by a free Servnet support audit — not a quotation. TPM covers hardware break-fix and defers refresh; it does NOT supply software/firmware security patches.
Third-party maintenance across your estate
One independent contract can cover every OEM below. Model your saving →
Guides
- What is TPM? →
- TPM vs OEM support →
- When does OEM support end? (this page)
Related tools & services
Last reviewed 7 October 2026. Manufacturer programme names, lifecycle dates and every cited figure on this page are re-checked against the manufacturers’ own published material at each review.
Talk to a UK specialist
Get expert advice or a no-obligation quote — servers, storage, networking, maintenance, finance and cloud. We reply the same working day.