Nine PBS is suing its dead vendor's landlord, and the colo contract holds the keys

Perspective Coverage

Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.

Builder

20%

Operator

57%

Investor

23%

Builder

For builders, this is a concrete failure of the abstraction stack: a customer bought 'cloud storage' but the durability of 50TB of irreplaceable video ultimately depended on who owned the physical drives in a Denver colo cage. Nothing in the reporting shows an escrow arrangement, a second copy, exportable metadata, or a tested restore path; the retrieval plan is a former employee of a dead company working against a 30-day clock, with the possibility that the volumes are encrypted and the keys are gone. The derived per-file average of roughly 4.5GB underlines that this was a video-master archive where egress was likely slow and expensive enough to discourage routine verification.

Operator

Operationally, the story maps the seam between a SaaS/cloud contract and the colocation contract underneath it. Nine PBS had a 30-day post-termination retrieval clause with OSS, but the counterparty stopped answering in February 2026 and access ended on March 6; the facility operator, Iron Mountain, refused pre-order access because the hardware and the data belong to its tenant, not to it. The remedy path was legal, not contractual: a default judgment against OSS, a preservation order against Iron Mountain, then an August ruling requiring handover of the physical devices with third-party retrieval inside 30 days and status updates by September 14. The operator lesson is to know your provider's provider, to obtain preservation and access rights that survive vendor insolvency, and to test restores before the vendor is delinquent with the Secretary of State.

Investor

Financially, the exposure is asymmetric and mostly reputational. Iron Mountain's Denver footprint in this dispute is a single site, DEN-1, bought with Mag Datacenters/Fortrust for $128 million in 2017, and the company's public statement stresses it never had data access and honored its contract with OSS. But the sources supply no litigation reserve, damages figure, customer churn, pricing or contract-term change, so any claim of financial impact would be speculation. The durable investable signal is that when a wholesale colo tenant fails, the landlord absorbs legal and reputational cost from end customers it never contracted with — a diligence question about tenant-failure clauses rather than a quantified earnings event.

Reality

Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.

Evidence82

Court record plus three independent write-ups and a named vendor statement

The factual spine — filing date, court, 50TB/70-year scope, preservation order, and the August handover ruling — is corroborated by three publishers drawing on court documents, trade outlet Current, and the Denver Post, and Iron Mountain supplied an on-the-record statement of its own position. Gaps remain: OSS is unreachable so its side is absent, and whether the data is actually recoverable (for example if encrypted) is unresolved.

Adoption34

One fully documented real-world failure, no evidence of a wider pattern

This is a live production incident with a named customer, a quantified footprint (about 50TB, 11,000-plus files), an identified facility, and court-enforced remediation steps — far more concrete than an announcement. But the supplied sources document exactly one such vendor-insolvency custody failure and give no data on frequency, on other stranded OSS clients, or on comparable colo disputes, so breadth cannot be scored higher.

Hype gap