ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

Analyst Zeus Kerravala: Multi-Availability Zones Prevent Component Failures, Not Total Service Outages

ZK Research Principal Analyst Zeus Kerravala uses six major IT outages that occurred within a week in November 2026 to demonstrate the fundamental difference between availability architecture and resilience architecture. Using Zscaler’s Business Continuity Cloud as a case study, he explains the specific architectural conditions required for true fate separation.

2026-11-19 09:21 GMT+8

Between November 12 and 17, 2026, six major IT outages occurred over six days: Microsoft 365 experienced a global outage lasting nearly 24 hours; Workday inadvertently connected its disaster recovery environment to production databases; the U.S. Federal Aviation Administration issued a nationwide ground stop due to router overload; United Airlines delayed flights because it could not obtain aircraft weight data; JPMorgan Chase suffered customer transfer failures due to local hardware and software defects; and Apple experienced outages affecting iCloud and Apple Pay due to an internal update. While the root causes varied—a dormant bug, overloaded routers, a faulty internal update, and local hardware failure—the pattern was identical: a critical dependency failed, and business operations stopped. ZK Research Principal Analyst Zeus Kerravala argues from this that availability architecture and resilience architecture are not the same thing. The former keeps services running when components fail; the latter keeps businesses running when an entire service fails. Most companies possess the former but mistakenly believe they have the latter.

Kerravala points out that cloud computing has caused the industry to forget disaster recovery discipline. In the financial services sector, maintaining both a production data center and a disaster recovery (DR) data center is non-negotiable standard practice. As the world shifted to the cloud, many assumed disaster recovery became the responsibility of the cloud provider; however, it remains a shared responsibility. Availability zones and multi-region designs protect against hardware failures and localized events, but these environments share software, control planes, configuration pipelines, and DNS. When a bad configuration or a dormant bug propagates, it spreads everywhere—as seen with Microsoft’s July network gateway bug, which cascaded across 74 countries and territories.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Kerravala cites Zscaler’s Business Continuity Cloud as a concrete example of what fate separation requires. This environment operates in third-party data centers rather than Zscaler’s own facilities, utilizing independent networks, autonomous system numbers, DNS, and cloud domains. Software and threat intelligence updates are deliberately staggered so that a defective production release does not simultaneously land in the backup. Policy and identity data sync unidirectionally into a read-only, last-known-good state. Spanning nine regions, the architecture is sufficient to maintain domestic operations if a nation were cut off. Zscaler also encourages customers to route synthetic or trusted user traffic to the backup environment continuously during peacetime, validating the failover path daily rather than testing it only during annual tabletop exercises. Failover can be triggered automatically or manually by the customer, ensuring functionality even if Zscaler itself becomes unreachable.

Kerravala’s conclusions are directed at buyers: define the minimum viable business, identifying three to five workflows that must continue running along with all their dependencies; interrogate each key vendor’s continuity architecture—if the answer is 'multiple availability zones,' that indicates availability, not continuity; test continuously rather than relying on annual exercises; keep security capabilities online during crises, as attackers will act immediately when defenses are relaxed; and leverage buyer power at renewal time by making fate-separated continuity a contractual requirement. He acknowledges that Zscaler cannot keep Microsoft mailboxes online or restart FAA routers; its architecture serves merely as a continuity model for its own platform, not a panacea.

Sources

  • siliconangle.comSiliconANGLE↗
Continue researching →