Infra & Compute 13/08/2026 à 20h4310Ajouter aux favoris

PBS lost access to 50TB of archival content - 70 years of television history - after its cloud storage vendor ceased operations. The failure mode is vendor business failure, not downtime: SLAs don't protect against it, and most organizations aren't structured to prevent it.
In plain terms: The cloud didn't go down. The vendor went out of business. SLA uptime guarantees don't protect against that - and most archival data strategies haven't been written for it.
PBS has lost access to 50TB of archival content after its contracted cloud storage vendor ceased operations. The organization is suing Iron Mountain Data Center, which hosts the physical infrastructure, to preserve access to materials covering 70 years of public television. The content exists physically; the legal and operational path to recovering it is unresolved.
This is a categorically different failure than cloud outage. Uptime SLAs, redundancy architecture, and disaster recovery plans are designed for infrastructure failure. They are not designed for vendor liquidation - the legal, operational, and contractual chaos of a vendor ceasing to exist as a going concern. 50TB at commodity cloud storage rates is a sub-$1,000/month problem. The failure was not technical; it was organizational and contractual. The lesson isn't cloud avoidance - it's data custodianship: who is legally and operationally responsible for ensuring data survives vendor transitions, and does your contract give you egress rights before a vendor becomes insolvent?
[Under the hood] Data custodianship clauses, egress rights, and replication requirements are the contract terms that matter for archival data - not uptime SLAs.
Whether this becomes a reference case in enterprise cloud contract negotiations, particularly for archival and compliance data where long-term durability is the actual requirement.
Article produit par intelligence artificielle, relu sous contrôle éditorial humain.
Connectez-vous pour rejoindre la discussion.
Does this mean we’re quietly accepting that 70 years of public broadcasting is now at the mercy of corporate balance sheets? Feels like a slow surrender to convenience over preservation.
I agree - this isn’t just a cloud problem; it’s a classic case of putting all your tapes in one digital basket. Cultural preservation needs decentralized solutions, not just ‘set and forget’ storage.
If even PBS couldn’t secure 70 years of TV history, how can smaller archives ever trust cloud storage? Feels like a wake-up call for decentralized backups.
But wouldn’t decentralized storage just shift the risk-from vendor failure to human error or malware-without solving the governance problem entirely?
This is exactly why redundancy isn’t optional for critical archives-even with cloud providers. What’s alarming is how often we assume 'the cloud' is a bulletproof lockbox.
Isn’t this what happens when you treat digital storage like a fire-and-forget solution? Data durability should be a top priority, not an afterthought.
Seventy years of history wiped out in a week shows cloud storage isn’t a magic solution-it just moves the risk elsewhere. Maybe regulations should mandate split custody, like splitting gold bars between two vaults.
This is why institutions handling cultural heritage need immutable backups-whether on-site or with strictly audited third parties. How can we ensure such failures don’t become recurring oversights?
That’s terrifying. If a giant like PBS can lose decades of history just like that, who’s safe? Not exactly reassuring for smaller archives.
That’s the risk of relying solely on third-party storage. Maybe they should’ve diversified providers years ago-no single vendor should hold irreplaceable history.
But isn't this exactly why historical archives shouldn't be outsourced to for-profit vendors? Some things should be publicly owned and managed.