Not long ago, I worked with an enterprise that believed it had done everything right. The company had spread workloads across multiple regions, replicated key data stores, documented failover procedures, and invested heavily in automation. On paper, it looked like a mature cloud deployment. Then a control-plane issue hit one of its core providers. The infrastructure itself was not entirely gone, but the management layer became unstable enough that teams could not make timely changes, trigger the recovery actions they expected, or trust the environment’s state in real time. What failed was not simply compute or storage. What failed was the company’s assumption that the cloud’s control mechanisms would always be there.
That experience gets to the heart of a growing problem. Cloud reliability is under renewed scrutiny because more outages are now being tied to control-plane failures rather than isolated infrastructure faults. An Uptime Institute report recently highlighted that shift, and it should get the attention of every serious architect. When the management layer becomes the problem, the blast radius can be much broader than most organizations anticipate.
For years, the industry has talked about resilience primarily in terms of infrastructure. We focus on zones, regions, backups, and service redundancy. Those things still matter, of course. However, they do not tell the whole story anymore. The cloud is not just a collection of servers, storage systems, and networks. It is also a massive operating model built around APIs, orchestration layers, identity systems, policy engines, service controllers, and automation frameworks. When that higher-order control structure breaks or becomes impaired, your recovery plans can unravel very quickly.
