https://www.theregister.com/2001/04/12/missing_novell_server...
The portfolio of apps we developed/maintain for these legacy systems have all been ported to their modern replacement systems years ago, but we still regularly release updates targeting legacy that maintain feature parity with modern releases.
I'll be glad when legacy support hits EOL though, if only for the indirect consequence of unambiguously seperating wheat from chaff as we embrace a new tech stack approaching stability. Although it isn't the case, it sure has felt like we've been operating like cost center baggage these past few years.
In the aggregate, these legacy systems are on the right tail of the bathtub curve quickly approaching EOL, hence their modern replacements already being fielded. As legacy systems are decommissioned, reclamation buffers the spares inventory pool. Push come to shove, cannibalization in the field keeps most balls rolling at the cost of diminished availability/throughput.
Based on a sample size of 2 legacy systems in our lab that saw daily use over the past decade, things definitely broke, but I don't recall the production Alpha hosts every giving up the ghost beyond CMOS battery replacement nuisance.
We still have a few support Alphas laying around just in case, but virtualization[1] on commodity bare metal effectively renders them redundant.
[1] https://www.stromasys.com/solution/charon-axp-alpha-virtuali...