{
  "id": 20684850,
  "title": "Six days, six outages: Why reliability isn’t resilience",
  "url": "https://urgent.news/2026/11/19/six-days-six-outages-why-reliability-isnt-resilience",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-19T01:21:51.000Z",
  "source": {
    "name": "SiliconANGLE",
    "slug": "siliconangle",
    "url": "https://siliconangle.com/2026/11/18/six-days-six-outages-why-reliability-isnt-resilience/"
  },
  "original_language": "en",
  "account": "Six consecutive days of major outages have highlighted a troubling pattern. Services went dark, Downdetector's graphs spiked, providers issued multiple status updates, a root cause was eventually identified, and everyone returned to work, presuming the issue wouldn't reoccur. None of these events were attributed to cyberattacks, and no clear connections exist between them. The root causes range from dormant bugs, overloaded legacy routers, an internal update gone wrong, and an on-premises hardware malfunction. These systems span public and private clouds, company data centers, and even air traffic control equipment that's decades old. The common denominator isn't the technology, but rather that each organization experienced a critical dependency failure, and the business operations ground to a halt. This report aims to provide business leaders with a vital lesson: outages are not isolated occurrences to be addressed after the fact, but rather a certainty that requires proactive planning. The focus should be on preparing for an entire service failure, not just a single server or data center. To explore this concept further, I spoke with Jay Chaudhry, Zscaler's CEO, and Misha Kuperman, the company's Chief Reliability Officer. Zscaler serves as a prime example of a company that has prioritized resilience over mere reliability. By deploying Zscaler, every user, branch, and device connects through its Zero Trust Exchange. This central position makes Zscaler a critical link in the chain. If it goes down, users cannot access Microsoft 365, Salesforce, internal applications, or anything else, regardless of their health. Zscaler recognized this critical nature and implemented resiliency in its service design. Despite the complexity, Zscaler has not experienced any downtime due to its own service failures. However, it's crucial to understand that this doesn't mean Zscaler can ensure the continuity of other services. The company is merely preparing for its own platform failures. For business leaders, this case study offers valuable insights on how to architect their own critical path services. Chaudhry, a former IBM executive, emphasizes that most large customers had both a production data center and a disaster recovery (DR) data center. However, when companies moved to the cloud, they forgot about the need for a DR strategy. The responsibility for disaster recovery should not be solely placed on the cloud provider. Availability zones and multiregion designs offer protection against hardware failures and localized events, but they do not prevent software, control plane, configuration pipeline, or DNS issues from propagating system-wide. This distinction between availability and resilience is critical to understand. While availability ensures a service remains operational when a component fails, resilience ensures the business continues functioning when the entire service fails. Most companies have established the first, but not the second. A 99.999% uptime commitment, while reassuring, doesn't guarantee business continuity. With this in mind, Chaudhry uses an analogy to illustrate the importance of having a contingency plan, much like buying insurance in addition to owning a reliable car. Zscaler has constructed a cyber equivalent of this contingency plan. Regulators worldwide have recognized the need for improved resilience. The EU's Digital Operational Resilience Act and Australia's CPS 230 both mandate that technology providers assess, test, and mitigate risks associated with their services. In light of recent outages, IT executives must shift their focus from asking about service-level agreements (SLAs) to considering what business processes must continue when a critical dependency fails, and whether they have validated their ability to do so.",
  "summary": "A rash of major outages over the past week all seem to follow a similar script. Services go dark, Downdetector lights up, the provider posts a string of status updates, a root cause emerges a few days later, and everyone goes back to work, assuming it won’t happen again. This past week, that script was […] The post Six days, six outages: Why reliability isn’t resilience appeared first on…",
  "key_points": [
    "Six consecutive days of major outages highlight reliability issues",
    "Outages caused by dormant bugs, overloaded routers, and hardware malfunctions",
    "Zscaler's Zero Trust Exchange demonstrates resilience over reliability"
  ],
  "editors_take": "Frequent service disruptions reveal that relying on uptime guarantees is insufficient for business continuity when critical dependencies fail, forcing leaders to prioritize systemic resilience over mere component availability.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}