A disaster-recovery contract is meant to be the document a company reaches for when everything else fails. It promises a recovery seat, a server environment, a data-centre footprint, a managed failover path, a backup plan, a named support team, and a commercial answer to a frightening question: what happens when the office is shut, the primary systems are down, or a cyber event turns normal operations into triage? Sungard Availability Services built its identity around that anxiety. The European record around Sungard Availability Services (Europe), however, turns the same anxiety back onto the vendor. The first number is not a rack count. It is the UK operating company's 2020 revenue: GBP 139.4 million, down 10 percent, with a GBP 17.8 million net loss, as reported from its filed accounts by The Register at the time the UK arm entered administration (https://www.theregister.com/on-prem/2022/03/30/cloud-and-dc-player-sungards-uk-arm-in-administration/1381024). For a buyer of continuity, that number changes the economic decision from "which recovery service has the best feature set?" to "which provider balance sheet, lease structure and power pass-through can actually support the recovery promise when stress arrives?"
That is the governing issue. Sungard AS was not a speculative hosting start-up with no operating history. The group described itself in April 2022 as a 40-year provider serving enterprise customers from 75 hardened data centres and workplace recovery facilities in nine countries (https://www.prnewswire.com/news-releases/sungard-availability-services-takes-action-to-strengthen-operating-cost-structure-for-future-success-301522862.html). Its proposition was familiar and serious: cloud-connected infrastructure, disaster recovery, workplace recovery, managed cloud, consulting and operational resilience. Yet the UK entity behind an important part of the European business entered administration on 25 March 2022, later moved into creditors' voluntary liquidation on 5 April 2024, and is shown by Companies House as due to be dissolved on 20 September 2026 (https://find-and-update.company-information.service.gov.uk/company/02368123/insolvency). In other words, the public record does not merely show a vendor selling recovery. It shows a vendor whose own recovery path became a case study in burden-sharing among customers, landlords, lenders, acquirers and network operators.
The hard underwriting question is therefore specific: in the disaster-recovery contract file, where is the clause, schedule or side letter proving that power surcharges, site-transfer rights, prepayments, customer migration obligations and data-return duties survive a vendor administration without making the customer an unsecured creditor? Sungard UK's 2022 event makes that question practical rather than theoretical. The administrators' communications, reported by The Register, said customers would be invoiced for the full amount of increased electricity costs going forward, that some prepaid amounts could not be set off against future costs, and that continued services required customers to pay charges as they fell due (https://www.theregister.com/on-prem/2022/03/30/cloud-and-dc-player-sungards-uk-arm-in-administration/1381024). A continuity buyer who ignores that page is not buying resilience; it is buying an assumption.
The continuity guarantee turns into counterparty credit
Sungard AS Europe is best understood through a paradox. The more important the service, the more the customer must diligence the provider's own continuity. A commodity virtual server can be replaced, sometimes painfully but quickly. A workplace recovery arrangement, a managed recovery environment, a colocation migration, or an enterprise cloud continuity plan is different. It includes physical access, staff knowledge, network addressing, software images, backup schedules, test windows, named escalation paths and contractual confidence that the vendor will still be present during a crisis. The customer is not only buying technology. It is extending operational credit to the provider.
The UK insolvency record makes that credit visible. Companies House lists Sungard Availability Services (UK) Limited, company number 02368123, as a private company incorporated on 4 April 1989, with the previous names Comdisco Continuity Services (UK) Limited, Failsafe ROC Limited and Drivestir Limited (https://find-and-update.company-information.service.gov.uk/company/02368123). That history matters because Comdisco continuity heritage is part of the older disaster-recovery market, where the product was physical preparedness as much as software. The same record now shows "Liquidation" as the company status. The Gazette notice records the appointment of Benji Dymant and Ian Colin Wormleighton of Teneo as administrators on 25 March 2022, with the principal trading address at Unit B Heathrow Corporate Park, Green Lane, Hounslow (https://www.thegazette.co.uk/notice/4031233). This is not a small clerical footnote; it is the legal frame around a provider of business-critical services.
The public reason for the stress was not one bad system outage. It was a cost-base mismatch. DataCenterDynamics reported that the UK division entered administration after surging UK energy prices, landlords declining to reduce rent costs, and lost business after Covid-19; it also reported around 300 UK employees and interim funding obtained by Teneo to keep trading while buyers were sought (https://www.datacenterdynamics.com/en/news/sungard-uk-goes-into-administration-blames-it-on-energy-crisis/). Sky News similarly reported nearly 300 jobs at risk, a landlord rent impasse, energy costs and clients including JP Morgan and the Home Office (https://news.sky.com/story/soaring-energy-costs-push-data-giant-sungards-uk-arm-into-administration-12576716). The point for customers is uncomfortable: even a company selling resilience can be vulnerable to the same fixed-cost and utilisation arithmetic as any data-centre tenant.
The public record also shows that the stress was not confined to the UK. Sungard AS announced on 11 April 2022 that it had filed voluntary Chapter 11 petitions in the U.S. and commenced Canadian CCAA proceedings, while saying its UK subsidiary had initiated an administration proceeding on 25 March 2022 to preserve value (https://www.prnewswire.com/news-releases/sungard-availability-services-takes-action-to-strengthen-operating-cost-structure-for-future-success-301522862.html). The company's statement cited delayed customer spending decisions, insourcing, reductions in IT spending, energy inflation and reduced demand for certain services. DataCenterDynamics reported about USD 424 million in secured debt and about USD 5 million of cash at the U.S. filing, and noted landlords, AWS, Microsoft, Vertiv, Ensono and Micro Focus among creditor categories visible in court material (https://www.datacenterdynamics.com/en/news/sungard-files-for-second-us-bankruptcy-in-three-years/). A continuity provider can survive such proceedings operationally, but the customer cannot treat the proceeding as irrelevant. Vendor solvency becomes part of the service design.
The old network name is now an inherited control surface
The network evidence is equally revealing because it shows continuity of identifiers across a changed commercial situation. PeeringDB still carries a network profile named Sungard Availability Services (Europe) under AS15533, with "Comdisco, ixGuardian, Hosting 365 (IE)" as aliases, a website override pointing to sungardas.com, network type "Content", 100 IPv4 prefixes, 20 IPv6 prefixes, traffic in the 5-10Gbps range, and geographic scope Europe (https://www.peeringdb.com/net/513). But the same record carries the economically important note: AS15533 has moved behind AS1828, Unitas Global, and peering requests should go to the Unitas peering team. That tells the reader this is not a clean current identity where brand, legal entity, routing policy and asset owner all point to the same place.
BGP sources sharpen the point. bgp.tools now labels AS15533 as Redcentric Solutions Ltd, says it is a 24-year-old BGP network, shows Redcentric Solutions Ltd as the upstream AS13009, and lists peers such as Bank of Montreal, Mitsubishi HC Capital UK, APAK Group and IDD Enterprises (https://bgp.tools/as/15533). IPinfo similarly presents AS15533 as Redcentric Solutions Ltd and lists four peers, including Redcentric's AS13009, Bank of Montreal, Mitsubishi HC Capital UK and APAK Group (https://ipinfo.io/AS15533). Hurricane Electric reports AS15533 as Redcentric Solutions Ltd, with the company website still shown as sungardas.com, country of origin United Kingdom, 17 originated prefixes and 52,224 originated IPv4 addresses (https://bgp.he.net/AS15533). A RIR mirror of the RIPE record shows the aut-num as AS15533, as-name SASEUROPE, organisation ORG-RSL38-RIPE, and remarks for AS-SASEUROPE and AS-SASEUROPE6 European hosting and customer networks, with Unitas Global import and export entries (https://whois.ipip.net/AS15533).
That combination is exactly why the company is interesting. The directory name points to Sungard Availability Services (Europe). The live routing mirrors point to Redcentric. The PeeringDB notes point to Unitas for peering. The historic website now resolves into the 11:11 Systems world, where 11:11 markets cloud, backup, disaster recovery, security and networking services (https://www.sungardas.com/). The economic asset is not a simple brand page. It is an inherited service surface: IP ranges, customer blocks, recovery contracts, colocation sites, support knowledge, route objects and account relationships that moved through a restructuring rather than disappearing.
For a buyer, this matters more than a logo. If an enterprise has firewall allowlists, VPN tunnels, DNS records, backup replication targets, recovery scripts or cloud interconnects tied to AS15533-era addressing, the name on the invoice may change before the technical dependency disappears. That makes the route contract a diligence document. A large customer should ask who is now authorised to originate each customer prefix, who pays Unitas or Redcentric for transit, what happens if a legacy customer block is renumbered, and whether any customer-specific route object still refers to a legacy Sungard maintainer. Those are not esoteric network questions. They are the hidden parts of a recovery plan.
Administration converted customers into the scarce asset
The UK administration tells a harsher story than a normal acquisition. In a normal sale, a buyer acquires a business because it likes the assets and expects the customers to follow. In the Sungard UK case, customer commitment appears to have been part of the price discovery itself. Redcentric's 7 June 2022 RNS said it had exchanged conditional contracts to acquire the business and assets relating to up to three data centres and the provision of other colocation and network services from Sungard Availability Services (UK) Limited in administration; the value would be calculated by reference to annualised recurring revenue from Sungard data-centre customers with which Redcentric agreed new contract terms (https://www.investegate.co.uk/announcement/rns/redcentric--rcn/acquisition-of-business-and-assets-of-sungard/7112796). The initial minimum consideration for all three data centres was GBP 11 million, the initial maximum was GBP 22 million, and up to GBP 7.625 million more could become payable under performance criteria. Redcentric also completed the acquisition of Sungard UK's consulting and AWS cloud-related services business for GBP 4.2 million in cash.
That structure tells the whole economic story: the asset value depended on customers signing. The Register reported the administrators' customer letter saying continued service after completion would be at Redcentric's discretion if the customer had not signed a new contract, and that customers without a new contract risked service cessation from completion (https://www.theregister.com/on-prem/2022/06/08/sungard-uk-bit-barns-offloaded-to-redcentric/1132894). Redcentric's own acquisition note framed the data-centre assets as colocation and cloud services with a blue-chip customer base (https://www.investegate.co.uk/announcement/rns/redcentric--rcn/acquisition-of-business-and-assets-of-sungard/7112796). The price was not a simple property valuation. It was a measure of how many customers could be converted quickly enough into durable contracts with a new provider.
Redcentric's later annual report gives a cleaner post-event accounting view. It says Redcentric Solutions Limited acquired the Sungard consulting business on 7 June 2022 for GBP 4.2 million cash, and on 6 July 2022 acquired certain business and assets relating to three data centres from Sungard Availability Services (UK) Limited in administration for GBP 10.1 million initial cash consideration plus a GBP 3.4 million cash prepayment and contingent consideration with a maximum potential value of GBP 19.0 million depending on customer retention and performance criteria (https://www.redcentricplc.com/wp-content/uploads/Redcentric-RA-2024.pdf). The same report says the combined transaction had total consideration of GBP 20.229 million and recognised GBP 8.8 million of customer relationships. That is the accounting translation of the stress event: the intangible value lay in customers who could be retained, migrated and cross-sold.
Daisy was the other important UK transition path. DataCenterDynamics reported in May 2022 that some Sungard workplace recovery customers were being transferred to Daisy Corporate Services, and that administrators had told clients some workplace recovery sites were unable to continue as a going concern (https://www.datacenterdynamics.com/en/news/daisy-group-acquires-sungards-uk-customers/). The report said customers were being advised to agree new terms with Daisy within a month or services could cease. That does not mean every customer suffered an outage. It means the continuity product itself became dependent on a rapid contracting exercise under insolvency time pressure. A recovery buyer should remember that more vividly than any marketing brochure.
The renewal window priced the service, not the brand
The most useful unit-economics clue is what happened between Redcentric's exchange and completion. London South East's Sharecast report on Redcentric's July 2022 update said 162 Sungard data-centre customers, equal to 60.4 percent of the historical revenue base, signed long-term contracts with Redcentric ranging from 12 to 60 months and generating GBP 34.9 million of total annual recurring revenue (https://www.lse.co.uk/news/redcentric-updates-market-on-two-data-centre-acquisitions-hq5sobj80rdg8wg.html). It also reported that a further 57 customers signed short-term contracts of one to nine months, adding GBP 4.2 million of revenue and taking expected first-12-month contracted revenue to GBP 39.1 million. Insider Media reported the same 162-customer, 60.4 percent and GBP 34.9 million figures, and added that the former Sungard data-centre business was loss-making but expected to move to profitability within six months under Redcentric ownership based on customer contracts and cost restructuring (https://www.insidermedia.com/news/yorkshire/redcentric-provides-further-details-on-acquisitions).
Those numbers should change how the business is read. The value was not "Sungard" in the abstract. It was revenue that could be re-papered under a new, more financeable operator. A customer that signed a 36-month or 60-month Redcentric contract was not merely accepting a new supplier name; it was helping convert distressed facility obligations into bankable recurring revenue. A customer that signed only a short-term contract was economically different. It preserved service for a few months but did not give the buyer the same confidence to pay, invest, restructure and retain staff. A customer that refused to sign became an operational and valuation problem.
This is why customer concentration files and churn files matter more than facility photographs. A disaster-recovery room full of desks or a data hall full of racks can look stable while the revenue base is unstable. If 60.4 percent of a historical revenue base could be converted into longer contracts quickly, the business was not worthless. If a meaningful share required short-term arrangements, urgent authorisations, or exit planning, the buyer had to price uncertainty. The facility was only one side of the transaction. The contract-duration mix was the other.
The reduced initial consideration also matters. London South East reported that Redcentric had been committed to paying a GBP 11 million minimum conditional on revenue thresholds, but that because the minimum thresholds were not met it exercised its right to proceed at a reduced price of GBP 10.12 million (https://www.lse.co.uk/news/redcentric-updates-market-on-two-data-centre-acquisitions-hq5sobj80rdg8wg.html). That is a public-market version of a lender's discount. The buyer wanted the assets, but not at a price that ignored customer attrition. In continuity infrastructure, a retained customer is not just revenue; it is proof that the service remains trusted enough to survive a vendor failure event.
The contract-term distribution is also a clue to procurement friction. Some customers were able to sign long contracts within the short window. Others could only sign short contracts because they were leaving or could not achieve authorisation fast enough, according to the same Redcentric update. That distinction is important for public-sector and regulated customers. Their procurement cycles may be slow precisely because the service is critical. Yet a vendor administration can compress decision time into weeks. If the customer's governance cannot approve a new supplier quickly, the technical continuity of the environment may be less relevant than the customer's own ability to contract.
The lesson for buyers is to pre-authorise failure options before failure. A customer relying on a recovery vendor should have a board-approved successor-provider playbook, a legal review of assignment clauses, a data-export plan, a backup DNS and routing plan, and a budget path for emergency power or migration costs. That is not bureaucratic excess. It is the work needed to prevent a supplier event from becoming a customer emergency.
The lesson for acquirers is equally clear. A distressed continuity platform can be attractive if it has sticky customers, strong recovery know-how, usable data-centre assets and underpriced cross-sell potential. But the acquirer must rapidly sort customers into four groups: those ready to sign long-term, those needing short-term bridge terms, those already leaving, and those whose contracts or regulated status make transfer difficult. The price of the business should follow that segmentation, not the brand's historic reputation.
What the public record cannot prove is part of the valuation
The evidence supports a strong thesis, but it does not support a complete account-level map. Public sources show the UK entity's insolvency status, the parent restructuring, the asset transfers, AS15533's changed operating context, and Redcentric's customer-renewal figures. They do not show every customer name, every recovery objective, every prepaid balance, every data-return clause, every retained engineer, every route object that still matters to a customer, or every cross-border contract in Ireland, France, Belgium, Luxembourg and Poland. That absence is not a weakness in the public record alone. It is the central underwriting gap.
Sungard AS's April 2022 statement said operations in Ireland, France, India, Belgium, Luxembourg and Poland were not affected by the proceedings in the U.S., Canada or the U.K. (https://www.prnewswire.com/news-releases/sungard-availability-services-takes-action-to-strengthen-operating-cost-structure-for-future-success-301522862.html). That statement is important, and it should be read narrowly. "Not affected" in a company announcement does not mean every contract was economically identical before and after the wider restructuring. It means those operations were outside the named proceedings at that time. A European customer still had to ask whether shared systems, parent funding, brand, support, cross-border staffing, insurance, software licensing, cloud management, network transit or account ownership could be affected indirectly.
The evidence also does not prove that AS15533 itself is a risk today. Current public mirrors show it associated with Redcentric, and Redcentric and later Stellanor present materially different capital and operating contexts from Sungard UK's 2022 crisis. The point is more precise: the same numerical identifier and some legacy records can outlive the legal and commercial identity that customers thought they were buying from. That makes AS15533 a continuity artifact. It is a sign that inherited infrastructure can remain useful, but also that diligence has to trace control rather than assume the name on an old network record is the current operating answer.
Market commentary around the 2022 event was thin but informative. The Register reported one client-side source saying Sungard was good at what it did but expensive in an environment trying to reduce costs (https://www.theregister.com/on-prem/2022/03/30/cloud-and-dc-player-sungards-uk-arm-in-administration/1381024). That is not proof of broad customer sentiment. It is a useful market clue because it joins quality and price in the same sentence. A continuity provider can be operationally respected and still commercially vulnerable if customers are under pressure to cut spend, if work-area recovery feels less necessary after remote-work adoption, or if power increases arrive faster than customers accept them.
There is also a reputational asymmetry. A recovery vendor's success is often invisible; its failure becomes memorable. If Sungard kept services running during administration while assets were transferred, that is a meaningful operational achievement. Redcentric's and Teneo's public statements emphasised service continuity and customer transfer. But for a buyer evaluating the next contract, the fact that the transfer had to be managed under insolvency conditions is itself part of the risk memory. The service may have worked. The governance surrounding it still had to be repaired.
This uncertainty should not be flattened into a moral judgement. The public record suggests real work by administrators, buyers, engineers and customers to preserve value and service. It also suggests that customer protections were uneven, because prepayments, new contracts, power charges and service-continuation rights were not all equivalent. The right conclusion is not that customers should avoid every provider with restructuring history. It is that they should demand a clearer price for that history.
The failure scenario is a contract event, not a dramatic blackout
The practical failure scenario for Sungard AS Europe is not only "power fails at a data centre." It is a disaster-recovery invocation during a vendor transition. Imagine a financial-services customer with a recovery contract tied to a Sungard-era UK facility, AS15533 addressing, a tested failover runbook, prepaid recovery seats and a cloud recovery environment that has not been fully migrated to the successor provider. The customer's main office is unavailable after a cyber incident, and the customer invokes the recovery arrangement. At that exact time, the customer receives notice that power surcharges must be paid, pre-administration prepayments cannot be set off, a new Redcentric or Daisy contract must be signed to secure continued service, and some route or facility details now sit behind a different network operator.
The technical problem might be solvable. Racks can stay powered. Engineers can keep systems running. The economic problem is more dangerous because it is ambiguous under time pressure. Who has the right to release backup media? Who controls site access lists? Which provider accepts liability for missed recovery time if the contract changed during administration? Does the old service credit have value if the old entity is insolvent? If an address block must be renumbered, who pays for firewall, VPN and application remediation? If a customer refuses a new three-year commitment because it wants only emergency cover, does the provider have to keep serving it?
This is where the public record becomes operational. The Register reported that Redcentric told customers it would adopt Sungard's terms and conditions and offer market rates, while also saying customers should sign new contracts to ensure continuation of services (https://www.theregister.com/on-prem/2022/06/08/sungard-uk-bit-barns-offloaded-to-redcentric/1132894). It also reported that prepayments made before administration would not be transferred to Redcentric or repaid, irrespective of whether service had been provided, leaving customers to submit unsecured claims. That is a pure continuity lesson: cash paid in advance to a recovery vendor is not the same as recovery capacity guaranteed through a stress event.
The buyer's hard document request is therefore a disaster-recovery contract annex. It should show where customer data sits, who owns or controls the recovery environment, which party can transfer the contract, what happens to prepaid amounts, how power pass-throughs are calculated, which sites are substitutable, which network routes are customer-specific, and which successor providers must honor recovery objectives. Without that annex, a customer is underwriting a chain of assumptions.
Power, leases and utilisation explain why resilience can fail quietly
Sungard UK's stress was economically rational even if the service was technically capable. Data centres and recovery facilities combine fixed real-estate obligations, power exposure, staff costs and utilisation risk. Workplace recovery was especially exposed to the pandemic because shared office recovery seats made less sense when customers had already moved large portions of staff to home-working. The Business Continuity Institute captured the broader market shift in a 2021 discussion of work area recovery providers: customers questioned the value of shared work-area services as they changed working models, and cost reduction led to reduction or removal of some work-area services (https://www.thebci.org/news/how-have-work-area-recovery-providers-been-impacted-and-evolved-since-the-pandemic.html). Sungard's UK arm was not outside that market reality.
The economic trap was pass-through timing. A provider can have a contract that allows power increases to be passed to customers, but the value of that clause depends on enforceability, customer willingness, billing cadence, public procurement rules, competitive alternatives and the buyer's own budget cycle. The Register reported that some customers disputed amounts when Sungard tried to recover increased electricity costs, and that the company had not been successful in passing incremental electricity price rises to all customers (https://www.theregister.com/on-prem/2022/03/30/cloud-and-dc-player-sungards-uk-arm-in-administration/1381024). DataCenterDynamics reported administrator Benji Dymant saying medium- to long-term trading would require burden-sharing from customers and landlords (https://www.datacenterdynamics.com/en/news/sungard-uk-goes-into-administration-blames-it-on-energy-crisis/). That phrase is the real unit economics of recovery infrastructure: burden-sharing failed, and insolvency followed.
Lease structure compounded the problem. A data-centre or recovery-site operator with uneconomic leases cannot instantly resize its cost base when customers leave, test less, move cloud workloads elsewhere or reject power surcharges. Sungard AS itself said the 2019 restructuring eliminated more than USD 800 million of debt and added USD 100 million of liquidity, but did not solve operating-structure challenges, mainly uneconomical leases and underutilized space (https://www.prnewswire.com/news-releases/sungard-availability-services-takes-action-to-strengthen-operating-cost-structure-for-future-success-301522862.html). That is why old continuity providers can be riskier than they look. Their credibility rests on decades of service, but their cost base may still be tied to old facility footprints and customer behaviour that changed faster than leases could be renegotiated.
The story after acquisition confirms the value and the burden. Redcentric's 2024 annual report says its FY24 revenue reached GBP 163.2 million, with recurring revenue of GBP 149.1 million, and that FY23 had only about nine months of trading from both Sungard and 4D acquisitions (https://www.redcentricplc.com/wp-content/uploads/Redcentric-RA-2024.pdf). Later, in 2025, Redcentric announced a disposal of Redcentric Data Centres Limited, explaining that acquisitions culminating in Sungard's data-centre assets had built a portfolio of eight data centres with 23MW of secured grid capacity, but also that MSP and data-centre businesses had different models, capital requirements and valuation metrics (https://www.investegate.co.uk/announcement/rns/redcentric--rcn/disposal-of-redcentric-data-centres-limited/9188574). Stellanor announced completion of the acquisition of eight Redcentric data centres in May 2026, saying it now operated eleven UK data centres with 39MVA of secured grid capacity and about 450 enterprise customers (https://www.stellanordatacenters.com/stellanor-completes-acquisition-of-eight-data-centers-from-redcentric/). The assets did not vanish. They moved into a different capital story.
The competitive market rewards scale, but local legacy still has value
The UK and European continuity market has consolidated because buyers want resilience but do not want to pay unlimited bespoke facility costs. Redcentric, Daisy, 11:11 Systems, 365 Data Centers, Stellanor and other managed-infrastructure players demonstrate the same logic from different angles. Redcentric acquired customers, contracts, consulting and data-centre assets. Daisy took workplace-recovery customers. 11:11 acquired Sungard AS recovery and cloud managed-services businesses in North America and said the acquisitions helped form a cloud, connectivity and security platform with nearly 5,000 customers and more than 60 global cloud points of presence (https://1111systems.com/resources/1111-systems-completes-acquisition-of-sungard-as-cm/). 365 Data Centers acquired a U.S. colocation and network business that it said added eight primarily high-density facilities, a network platform and 400 customers (https://365datacenters.com/365-data-centers-acquires-us-colocation-and-network-business-of-sungard-availability-services/).
For Europe, the competitive lesson is not that Sungard had no value. The buyer behaviour says the opposite. Redcentric paid cash for consulting and data-centre assets because it saw customer relationships, cross-sell potential and recovery-based services. Daisy accepted workplace recovery customers because it had relevant scale in business continuity. Stellanor later presented Redcentric's data-centre portfolio as a strategic urban infrastructure platform. A distressed seller can still own valuable assets; distress changes who captures the value and how customers must recommit.
This is why the article's conclusion cannot be a simple warning against Sungard-branded heritage. Legacy recovery providers can be valuable because they hold deep customer knowledge, proven operating procedures, trained staff, data-centre access, and long-used address space. The same heritage creates diligence needs because old contracts may not reflect today's power volatility, cyber-recovery expectations, cloud dependencies or data-centre capital requirements. A buyer does not need to reject every legacy provider. It needs to price the provider's own continuity risk.
Competition also changes the meaning of price. A lower monthly recovery fee can be a subsidy if the provider is undercharging for power, space or staffing. A higher fee may be rational if it funds multi-site design, reserved capacity, current hardware, tested recovery objectives and a solvent operator. Sungard UK's event shows that the cheapest contract is not necessarily the lowest-risk contract. The right benchmark is not price per rack or price per seat. It is the cost of assured recovery after factoring vendor solvency, site control, energy pass-throughs, migration rights and customer concentration.
Customers, lenders and acquirers should pay for proof, not promises
A large customer should pay for verified continuity and discount anything that depends on untested assumption. The proof package should include the disaster-recovery contract and amendments, site schedules, power-surcharge formula, prepaid-balance treatment, assignment and novation language, step-in or transfer rights, latest recovery-test results, backup retention evidence, RTO/RPO reporting, network route inventory, data-return procedures, customer-specific hardware lists, supplier contracts for power and transit, and the provider's own financial and lease exposure. The customer should also require a named successor-service plan if the provider sells a facility, loses a lease, moves a customer block, or transfers a recovery service to a new operator.
A lender or acquirer would underwrite a different bundle. It would pay for contracted recurring revenue that survives customer consent, customer relationships that can be renewed at market rates, network assets with clear route authority, clean prepayment handling, staff retention, facility leases that match customer contract duration, and the ability to cross-sell managed security, cloud and recovery services. It would discount old contracts with capped power pass-throughs, customers who are already migrating, facilities with uneconomic lease terms, service obligations without matching revenue, and any legal entity where customer cash is trapped behind insolvency priorities. Redcentric's accounting treatment of customer relationships and contingent consideration shows exactly why customer renewal was the value bridge (https://www.redcentricplc.com/wp-content/uploads/Redcentric-RA-2024.pdf).
A regulator or public-sector buyer should be especially careful because public services often treat continuity arrangements as invisible until invoked. If a government agency, hospital, utility or financial institution relies on a recovery site, it should not only ask whether the site is secure. It should ask who pays the next power shock, who controls the lease, who can transfer customer data, which entity holds the contract, whether the provider has gone through recent administration or liquidation events, and whether the service depends on a network identity whose control has changed. Sky's report that the Home Office was among clients served by Sungard UK makes this more than a private procurement lesson (https://news.sky.com/story/soaring-energy-costs-push-data-giant-sungards-uk-arm-into-administration-12576716).
The one fact that would most change the judgement is a current, customer-by-customer continuity map for the remaining European Sungard-era obligations: which contracts transferred to Redcentric, Daisy, 11:11, Stellanor or other providers; which AS15533 customer routes remain active; which legacy disaster-recovery commitments were terminated; and which customers had prepayments, bespoke recovery objectives or regulated workloads. Public sources show the broad asset migration. They do not show the account-level continuity outcome.
Until that map is available, the practical decision frame is conservative. A customer should treat a Sungard-era European service as potentially viable but not self-explanatory. If the current provider can show a clean successor contract, current site schedule, tested recovery run, named support team, accepted power formula, route-control statement and data-return mechanism, the old Sungard history becomes a diligence note rather than a disqualifier. If the provider cannot show those documents, the buyer should discount the service even if the facility looks professional and the technical team sounds credible. A lender should use the same discipline in reverse: recurring revenue is valuable only to the extent that customer consents, renewal terms, pass-through rights and site obligations are enforceable after a stress event. An acquirer should value inherited network and recovery assets only after separating customers that truly committed from those that merely bridged for a few months. A regulator should ask whether regulated workloads can keep operating if a recovery provider again needs a rapid sale, site transfer or contract rewrite. The public record around Sungard AS Europe does not say that continuity outsourcing is unsafe. It says that continuity outsourcing has a second layer of continuity risk, and that layer has to be priced before the emergency.
Public evidence register
Companies House shows Sungard Availability Services (UK) Limited as company number 02368123, incorporated 4 April 1989, now in liquidation, with past Comdisco Continuity Services naming and IT-service SIC classification: https://find-and-update.company-information.service.gov.uk/company/02368123.
Companies House insolvency data records administration from 25 March 2022 to 5 April 2024, creditors' voluntary liquidation from 5 April 2024, appointed practitioners and a due-dissolution date of 20 September 2026: https://find-and-update.company-information.service.gov.uk/company/02368123/insolvency.
The London Gazette gives the formal appointment of administrators, principal trading address and nature of business: https://www.thegazette.co.uk/notice/4031233.
PeeringDB identifies the Sungard Availability Services (Europe) network as AS15533, with European scope, content network type, traffic estimate and a note that it moved behind AS1828 Unitas Global: https://www.peeringdb.com/net/513.
bgp.tools, IPinfo and Hurricane Electric show the live or mirrored AS15533 view now associated with Redcentric Solutions Ltd, including peers, upstreams, prefixes and a lingering sungardas.com website reference: https://bgp.tools/as/15533, https://ipinfo.io/AS15533, and https://bgp.he.net/AS15533.
RIPE-derived mirrors show the AS15533 aut-num as SASEUROPE under ORG-RSL38-RIPE, with remarks for European hosting and customer networks and Unitas import/export policy: https://whois.ipip.net/AS15533.
Sungard AS's April 2022 announcement gives the U.S. Chapter 11 and Canadian CCAA context, reasons for stress, bridge and DIP financing, and the statement that Ireland, France, India, Belgium, Luxembourg and Poland were not affected by U.S., Canadian or UK proceedings: https://www.prnewswire.com/news-releases/sungard-availability-services-takes-action-to-strengthen-operating-cost-structure-for-future-success-301522862.html.
DataCenterDynamics and The Register provide contemporaneous reporting on the UK administration, energy-price pressure, landlord negotiations, customers, employees, power pass-through disputes, prepayment treatment and service-continuation mechanics: https://www.datacenterdynamics.com/en/news/sungard-uk-goes-into-administration-blames-it-on-energy-crisis/ and https://www.theregister.com/on-prem/2022/03/30/cloud-and-dc-player-sungards-uk-arm-in-administration/1381024.
Redcentric's acquisition announcement and annual report support the data-centre, consulting, AWS/cloud services, GBP 4.2 million consulting consideration, GBP 10.1 million data-centre consideration, GBP 3.4 million prepayment, contingent consideration and customer-relationship value: https://www.investegate.co.uk/announcement/rns/redcentric--rcn/acquisition-of-business-and-assets-of-sungard/7112796 and https://www.redcentricplc.com/wp-content/uploads/Redcentric-RA-2024.pdf.
Daisy, 11:11 Systems, 365 Data Centers, Redcentric disposal and Stellanor sources show where customer and infrastructure assets moved after the stress event: https://www.datacenterdynamics.com/en/news/daisy-group-acquires-sungards-uk-customers/, https://1111systems.com/resources/1111-systems-completes-acquisition-of-sungard-as-cm/, https://365datacenters.com/365-data-centers-acquires-us-colocation-and-network-business-of-sungard-availability-services/, https://www.investegate.co.uk/announcement/rns/redcentric--rcn/disposal-of-redcentric-data-centres-limited/9188574, and https://www.stellanordatacenters.com/stellanor-completes-acquisition-of-eight-data-centers-from-redcentric/.
Bottom line
Sungard Availability Services (Europe) is not mainly a story about a failed brand. It is a story about how continuity value changes hands. The service promise survived in parts because assets, customers, engineers, contracts and network identifiers could be transferred to stronger or more focused operators. But the public record also shows that customers had to navigate administration, new contracts, power charges, prepayment risk and identity changes in the middle of that transfer. The economic lesson is severe: when a company buys disaster recovery, it must underwrite the vendor's disaster recovery too.