August 29, 2026

Nine PBS’ 50TB Data Disaster: How 70 Years of TV History Got Trapped in the Cloud

Nine PBS’ 50TB Data Disaster: How 70 Years of TV History Got Trapped in the Cloud
Nine PBS in St. Louis has found itself dealing with a nightmare scenario for anyone responsible for long-term data storage: the data apparently still exists, but the organization can't access it. The public television station is fighting to recover more than 50 terabytes of archival material representing roughly 70 years of programming and regional history. The archive includes coverage of major events such as the Great Flood of 1993, the COVID-19 pandemic and the history of East St. Louis. The problem began when Nine PBS's cloud-storage provider, Open Source Storage (OSS), apparently ceased operations and stopped responding to the station. (link)

The interesting part from a technology perspective is that this isn't really a case of "the cloud lost the data." The physical servers containing the information are reportedly sitting inside an Iron Mountain data center in Denver. OSS had been using Iron Mountain's infrastructure to house the servers, while Nine PBS had contracted with OSS for the hardware, software and cloud-storage services. When OSS disappeared, Nine PBS effectively lost the ability to manage or retrieve its own archive. Iron Mountain has maintained that it provides the physical infrastructure and doesn't have access to the data stored on customer-owned hardware. (link)

This is where things get particularly interesting for IT administrators. Nine PBS had apparently been working with the storage provider since 2019 and renewed the arrangement annually. When the latest contract expired in March 2026, the station says it suddenly lost access despite contractual provisions that were supposed to provide time to retrieve its data. The situation eventually turned into a legal battle involving multiple companies and jurisdictions. A Denver judge has now established a process allowing Nine PBS to recover the archive, including requiring cooperation from Iron Mountain and giving the station 30 days to identify a qualified third party capable of accessing and extracting the data. (link)

There is a bigger lesson here for anyone running important infrastructure: owning your data isn't necessarily the same as controlling your data. A contract might say that your organization owns the files, but if the only person who has the credentials, encryption keys, hardware access or proprietary software disappears, ownership doesn't automatically give you technical access. This is especially important with large archives because 50 TB isn't something you casually download overnight. Depending on the storage technology, network connectivity, encryption and hardware involved, recovering that much information can require specialized equipment and a carefully controlled migration. The situation also highlights why organizations should maintain independent backups, document encryption keys and credentials, and periodically test whether they can actually restore their data.

For Nine PBS, the stakes go well beyond recovering some old video files. These archives contain unique pieces of regional history that may be impossible to recreate if they are lost or corrupted. The court has ruled that Nine PBS owns the material and is entitled to recover it, which is an important step forward, but the technical recovery still has to happen. (link) For IT departments, the story is a great reminder that a 3-2-1 backup strategy, vendor exit plan, independent credentials, documented recovery procedures and periodically tested restores aren't just enterprise buzzwords. When your cloud provider disappears, they can be the difference between having a temporary inconvenience and spending months in court trying to get your own data back.

References



Popular post in the past 30 days