The editorial argues this isn't a cloud-is-bad story but a specific class of failure engineering teams don't plan for. SLAs, RPO/RTO targets, and multi-region replication all assume the vendor remains a going concern — when the vendor folds, none of that machinery helps because the paperwork chain, not the technology, is what breaks.
The Tom's Hardware reporting emphasizes that Iron Mountain physically holds the tapes and drives but has no contract with Nine PBS — only with the defunct middleman. The lawsuit exists because ownership of the content and possession of the media were separated by a subcontracting arrangement that collapsed when one link in the chain went out of business.
The editorial stresses that Nine PBS's collection includes civil-rights-era interviews, gubernatorial debates, and local news that exists nowhere else, and is treated by historians as a primary source. Public broadcasters are often the only institutions that recorded a region's civic life on video, making the loss categorically different from losing replaceable commercial content.
Nine PBS, the St. Louis public television station that has been on the air since 1954, is suing Iron Mountain to regain physical access to seven decades of broadcast tapes, master files, and digitized archives. The immediate cause isn't a hardware failure or a ransomware event — it's that the cloud storage vendor Nine had contracted with to manage the collection quietly went out of business, leaving the physical media stranded inside an Iron Mountain data center that Nine has no direct contractual relationship with.
According to reporting by Tom's Hardware, Nine had outsourced its long-term preservation to a third-party provider that in turn colocated the storage inside Iron Mountain. When the vendor folded, the paperwork chain broke: Iron Mountain holds the boxes and racks, but its contract is with the defunct middleman, not with the actual owner of the content. Nine's lawsuit asks the court to force Iron Mountain to hand over the material — or at least allow supervised access — before the drives spin down for the last time or the tapes degrade past the point of transfer.
The archive itself is not replaceable. It includes decades of local news, civil-rights-era interviews, gubernatorial debates, and children's programming that exists nowhere else. Public broadcasters are often the only institutions that recorded a region's civic life on video, and Nine's collection is treated by historians as a primary source. A generation of tape masters and the digital surrogates made from them are now sitting on someone else's shelf, behind someone else's lock.
This is not a story about the cloud being bad. It's a story about a specific class of failure that most engineering teams are structurally bad at planning for: vendor insolvency. Availability SLAs, RPO/RTO targets, redundancy zones, and even multi-region replication all assume the vendor is a going concern. When the vendor stops answering the phone, none of that matters — your data is now a creditor's asset in a bankruptcy proceeding, or worse, orphaned in a colo where nobody has authority to release it.
The uncomfortable truth is that "the cloud" is almost always a stack of contracts, and each contract is a single point of failure that no amount of erasure coding can save you from. Nine did what a reasonable non-profit does: hired a specialist to handle a hard problem. The specialist did what a lot of specialists do: rented rack space from a larger operator and put a logo on the invoice. That works right up until the middle layer disappears, at which point the customer discovers they have no privity of contract with the party who physically possesses their bits.
The developer community has been here before, just at smaller scales. Parse shut down in 2016 and gave customers 12 months to migrate. Heroku killed its free tier and countless side projects with it. Google has a graveyard of retired APIs. What's different about the Nine case is the combination of long time horizons and physical media: archival storage is often bought precisely because the customer doesn't plan to touch it for years, which means they also don't notice when the vendor stops being able to serve it. By the time you need the data, the company may have been gone for six months.
The legal question is genuinely messy. Iron Mountain isn't the villain here — it's a data center operator being asked to hand over property it holds under a contract with a now-defunct entity, which creates real liability exposure if they get it wrong. But the practical outcome is the same for Nine: the tapes are hostages of a paperwork dispute, and every month that passes is a month closer to LTO degradation, drive failure, or a fire suppression event that nobody has an incentive to prevent.
If you run infrastructure for anything with a retention requirement measured in years — compliance archives, medical records, source-of-truth event logs, ML training data, customer document vaults — this case should reshape your vendor due diligence. A durability guarantee from a company that might not exist in 2030 is a marketing claim, not a control.
A few concrete things to change on Monday:
Demand a data escape clause in writing, with a real bit-level exit path. "You can export via our API" is not sufficient if the API requires a login to a domain that stops resolving. Ask for a documented process to recover raw storage — S3 bucket handoff, physical drive shipment, or third-party escrow — that survives the vendor's dissolution. If they can't answer, price in the cost of building it yourself.
Know the physical location and the operator. If your vendor is a reseller of AWS, GCP, or a colo, get that in writing and know which hyperscaler or facility your bytes actually live in. In a wind-down, you want to be able to knock on the underlying provider's door with a signed data processing agreement and a court order if necessary. Nine didn't have that lever.
Test the restore, not just the backup. The standard advice — "an untested backup is not a backup" — extends to vendor exits. Once a year, actually pull a non-trivial slice of your archive out through the documented exit process, end to end, and time it. If your entire archive is 400 TB and your egress path is a single API endpoint rate-limited to 10 MB/s, you have a business-continuity problem hiding as an engineering problem.
For truly irreplaceable data, keep a copy you physically control. LTO-9 tape is under $10/TB and lives on a shelf in a room you own. It's slow, it's annoying, and it will outlive any SaaS logo on your invoice. The 3-2-1 rule (three copies, two media, one offsite) exists because every generation rediscovers it the hard way.
Expect this pattern to repeat, and probably to escalate. A decade of ZIRP-fueled infrastructure startups is now aging into a rate environment where a lot of them will not survive their next funding round, and their customers' data will become the collateral damage. Regulators may eventually mandate escrow arrangements for archival cloud services the way they do for source code in some enterprise deals, but until then the burden sits with you. Treat every vendor contract as a bet on the vendor's five-year survival — and make sure you can walk away with your bytes if the bet doesn't pay off.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.