Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your cloud survived everything except the real world

War damage, air traffic chaos, and a storage shortage expose the cost of treating resilience as someone else's problem

Your cloud survived everything except the real world

In a recent incident, Amazon Web Services (AWS) suffered permanent data loss in its Middle East infrastructure due to war damage, leaving customers without access to their data. This serves as a stark reminder that cloud redundancy does not guarantee safety. The incident highlights the importance of having independent backups outside of a single cloud region, as physical destruction can be a major threat.

The UK air traffic control system also faced a major outage in September, which was reportedly caused by an incompatible flight plan entered by a military aircraft. This further illustrates the potential risks of relying solely on one cloud region for critical systems. The complexities and costs associated with backup strategies make them difficult to implement and test.

Additionally, the AI infrastructure boom has further strained storage capacity, as drives become scarce. While it may seem ironic to reference the 3-2-1 backup rule, the reality is that implementing such a strategy can be challenging, especially when provisioning the necessary storage for large-scale data centers. The story emphasizes the need for a robust data resilience strategy, as infrastructure is increasingly operating in hostile conditions.

Factors such as cable cuts, chaotic climate changes, cyber threats, and misinformed leaders pose risks to data safety. The story draws a parallel to the marine insurance industry, which developed to manage risks in an interconnected world. However, there is currently no global market for "data equivalent of war-risk insurance." Therefore, organizations must proactively plan for potential data loss and determine how to survive with less data if their primary data store becomes unavailable.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at theregister.com →

More in Tech

Laravel 13: What Actually Breaks When You Upgrade (and What Doesn't)

Laravel 12 stopped receiving bug fixes on August 13, 2026. Since then only security patches remain, and those run out on February 24, 2027.

  • Laravel 12 stopped receiving bug fixes on August 13, 2026
  • Two high-impact changes: Dependencies in composer.json and CSRF middleware updates
  • PHP 8.3 minimum required for Laravel 13 upgrade

More from Monday 21 September →