Your Cloud Vendor Died. Who Owns the Servers?

Somewhere in a Denver data center sits 50 terabytes of St. Louis television history — coverage of the Great Flood of 1993, East St. Louis history, the COVID-19 pandemic, more than 70 years of a public broadcaster's output. Nine PBS knows exactly which building it's in. It just can't have it, because the company it paid to store the data is dead, and the company that owns the building says the servers aren't theirs to open.

That's the short version of the lawsuit Nine PBS filed on July 28 in Denver District Court against Iron Mountain Data Centers. The longer version is a case study in a failure mode that most backup strategies don't model at all: not disk failure, not ransomware, not region outage, but custody collapse — the chain of companies between you and your bytes losing a link.

How you lose data that still exists

The timeline, per Nine PBS's complaints and reporting from Current and The Desk: the station (broadcast license KETC) had been buying hardware, software, and cloud storage since 2019 from a vendor called Open Source Storage, which ran its servers inside Iron Mountain's Denver facility. The contract renewed annually and was set to expire March 6, 2026, with a 30-day post-termination window for retrieving data.

In February, Nine PBS tried to schedule a renewal meeting. No response. On March 6, access was cut off without warning. OSS's website went dark, and the company turned up delinquent with the Colorado Secretary of State. Nine PBS sued OSS and its president in Missouri in April and won a default judgment — a court has already ruled the station owns the data and has an immediate right to possess it.

Which turns out not to matter much, because Iron Mountain's position is that OSS owns the physical servers inside its facility, and Nine PBS isn't its customer. A Denver judge has at least granted preliminary relief barring Iron Mountain from deleting or overwriting anything while the case proceeds.

Here's the uncomfortable part: Iron Mountain isn't obviously wrong. A colocation provider that hands a third party access to hardware it doesn't own — on the strength of that third party's claim, or even an out-of-state judgment against its actual customer — is taking on real legal risk. The company whose entire brand is "we protect archives" refusing to release an archive reads as grim irony, but it's the predictable output of the contracts involved. Nine PBS had privity with OSS. OSS had privity with Iron Mountain. Nine PBS and Iron Mountain had nothing, and when the middle link dissolved, so did every practical right the station thought it had.

We've run this experiment before

This keeps happening, and it keeps surprising people. Nirvanix — an actual venture-backed cloud storage platform, not a small reseller — collapsed in 2013 and gave enterprise customers roughly two weeks to evacuate petabytes. Digital Railroad, a photo archive and marketplace, shut down in 2008 and gave photographers about 24 hours before the servers went dark. And the Megaupload seizure in 2012 stranded legitimate customer data on hosting-company hardware for years; Kyle Goodwin, the videographer who fought in court to recover his files, became the canonical example of how little "it's my data" means when someone else controls the machines.

The Nine PBS variant is nastier than any of those, though, because there was no shutdown announcement and no window. The vendor simply stopped answering email and then stopped existing. Every contractual protection Nine PBS had negotiated — including that 30-day retrieval clause — depended on a counterparty that was still picking up the phone. A retrieval window in a contract with a ghost is worth exactly nothing.

What this means if you own a backup architecture

The standard 3-2-1 rule (three copies, two media, one offsite) quietly assumes the copies fail independently. Custody is a dimension of independence, same as geography and media. Two copies held through the same vendor — or through two vendors who both resell the same underlying infrastructure — are one copy for custody purposes. If you can't diagram the chain from your contract to the physical hardware, you don't know how many copies you have.

Concretely:

• Know who actually holds your bytes. "Cloud storage" from a small vendor very often means their boxes in someone else's colo. Ask. Put the answer in the vendor file. If the answer is a facility you have no relationship with, understand that your recovery path runs through a company that owes you nothing.
• Treat exit clauses as untested code. Nine PBS had a data-retrieval provision. It never got exercised because the counterparty vanished before termination was even formalized. Do an actual restore-from-vendor drill annually — pull a meaningful sample out through the front door and time it.
• For irreplaceable archives, hold one copy under your own administrative control. The math here is what makes this story genuinely painful. Fifty terabytes in S3 Glacier Deep Archive runs about $50 a month at current list pricing. On LTO-9 tape it's three cartridges — a few hundred dollars, once, sitting in a safe the station owns. The entire corpus at the center of two lawsuits in two states could have had an independent copy for less than the filing fees.
• Watch for vendor distress signals. Unanswered renewal emails in February were the tell. A vendor going quiet ahead of a contract date is the moment to start pulling data, not the moment to send a second email.

The verdict

Nine PBS will probably get its archive back. It has an ownership judgment, a preservation order, and a sympathetic set of facts; some negotiated process for imaging OSS's servers is the likely endgame. But "eventually, via litigation in two states" is not a disaster-recovery plan, and the station's experience shouldn't be read as an Iron Mountain problem or even an OSS problem. It's an architecture problem. The data never failed. The disks are presumably fine. What failed was a custody chain nobody had drawn on a whiteboard — and if your archive's survival depends on a vendor's continued corporate existence, you don't have an archive. You have a lease on one.