Microsoft Outage Insured Losses Under $100M, CyberCube Says

CyberCube estimates that global cyber insured losses from the 12-14 November Microsoft 365 outage will most likely be less than $100 million, with a conservative upper bound of $350 million. By our arithmetic, that ceiling is $50 million below the $400 million low end CyberCube gave for the 2024 CrowdStrike outage, and under $100 million works out to less than about $5.6 million for each of the roughly 18 hours of severe disruption.

The cyber risk analytics firm published the preliminary analysis from London at 09:04 UTC on 16 November, and Reuters reported it the same day. CyberCube nicknames the event “M364”.

Short explainer · Insured vs economic loss

A Business Pill Short on insured versus economic loss that uses this story as its worked example. Its figures are the estimates reported in the piece.

Business Pill · Concentration Explained

An evergreen Business Engineer explainer on concentration, when a few big pieces make the total. It teaches the general idea only and does not discuss Microsoft, CyberCube or this outage.

The key insight: As we read CyberCube’s estimate, duration and cost pull apart: about 18 hours of severe disruption passed the 8 to 12 hour waiting periods it cites, yet its most likely figure is under $100 million.

Under $100 Million, With a $350 Million Ceiling

CyberCube said the event “is expected to have a loss ratio impact for cyber insurers of 0% to 2% of global cyber premium”, in line with the Level 2 (moderate) tier assessment it issued to clients on 13 November. It said it “sees most outcomes clustering toward the lower end of the range”, with the high estimate “allowing headroom for information that could still emerge”.

The estimate is based on CyberCube’s catastrophe model and global industry exposure database, the company said. It activated its Cyber Aggregation Event Response Service on 12 November and issued a Security Incident Report to clients on 13 November.

CyberCube described severe disruption lasting about 18 hours and an event running roughly 38 hours in total, “well beyond the eight to 12 hour waiting periods common in contingent system failure cover”. Microsoft’s own review, as The Register reported it, puts 15 hours 17 minutes between the first alert and the mitigation, by our arithmetic in our post-incident review piece.

CyberCube’s upper bound for the Microsoft 365 outage, $350 million, is below the $400 million low end of
CyberCube’s upper bound for the Microsoft 365 outage, $350 million, is below the $400 million low end of its 2024 CrowdStrike range. Sources: CyberCube press releases (16 November 2026, 25 July 2024); Kovrr as reported by Reuters; Morningstar DBRS as reported by Insurance Business.

Why CyberCube Expects Small Claims After 38 Hours

CyberCube said that despite the duration, several factors will suppress insured losses. “Cover only responds where policies extend business interruption to non-malicious system failure at an outside provider”, it said, and reported impacts “all focus on the inconvenience and productivity loss, with workarounds widely available and little to no mention of lost revenue”.

The release added: “Simply put, email is not in the critical transaction path of most businesses.” Microsoft attributes the outage to a technical issue introduced during a network capacity upgrade, not cyber activity, CyberCube noted.

Jon Laux, CyberCube’s VP of Products and Analytics, said the event “once again reminds us how the technology world is concentrated in the hands of a few key providers”. He added that the estimate reflected “the relatively short duration of this event, the absence of any reported data corruption or leakage, and the ease with which companies fell back on alternative communication channels to email”.

Four Estimates, a Sevenfold Spread

Kovrr went higher. Reuters reported on 13 November that Shalom Bublil, Kovrr’s co-founder and chief product officer, put insured losses at around $700 million, with a preliminary range of $300 million to $1.4 billion. Bublil based it on economic losses of about $16 billion on a lost-productivity basis and called the figures a “back-of-an-envelope” assessment, Reuters reported. The same report said one broker had already received claims notifications relating to the outage.

By our arithmetic, Kovrr’s central figure is 7 times CyberCube’s most-likely ceiling, and it implies about 4.4% of Kovrr’s economic estimate would be insured. Insurance Business reported that Morningstar DBRS estimates $300 million to $500 million.

Marsh Re, formerly Guy Carpenter, wrote on 13 November that “the impact on the insurance market is expected to be minimal, with most losses likely limited to short-term productivity and operational delays”. Insurance Business reported that Marsh Re said waiting periods average around four hours for smaller organisations and 12 hours or more for larger ones.

Set Against CrowdStrike 2024

On 25 July 2024, CyberCube estimated preliminary insured losses from the CrowdStrike outage for the standalone cyber market at between $400 million and $1.5 billion, “a loss ratio impact of roughly 3-10% on global cyber premiums of $15bn today”. Its loss-ratio range for this outage is 0% to 2%.

By our arithmetic, CyberCube’s most-likely ceiling of $100 million is a quarter of its CrowdStrike low end and one fifteenth of its high end. Reuters reported that a later estimate by Guy Carpenter, now Marsh Re, put CrowdStrike insured losses at approximately $250 million.

Our first root-cause piece leads the coverage. The 84-organisation tally, the pool alarm piece and the SLA math piece cover the wider fallout.

The Structural Read

As we read CyberCube’s release, its deciding variable is revenue rather than hours: it says email is not in the critical transaction path of most businesses, and that reported impacts mention little to no lost revenue.

As we read the four estimates, the gap is about assumptions, not data: Kovrr started from a lost-productivity figure of about $16 billion, while CyberCube weighted whether policies extend business interruption to non-malicious system failure at an outside provider.

Jon Laux, CyberCube VP of Products and Analytics, 16 November 2026

“not all layers of the technology stack are equally critical to business operations.”

Three Implications

FOR CYBER INSURERS CyberCube puts the loss ratio impact at 0% to 2% of global cyber premium, against roughly 3-10% for its CrowdStrike estimate in 2024.

FOR INSUREDS Cover only responds where policies extend business interruption to non-malicious system failure at an outside provider, CyberCube said.

FOR BROKERS Insurance Business reported that Marsh Re put average waiting periods at around four hours for smaller organisations and 12 hours or more for larger ones.

The Business Engineer Lens

This story maps onto the Business Engineer framework Enterprise AI: From Software to Substrate.

The framework argues: “enterprise vendors don’t sell software anymore—they sell irreversibility.”

As we read it, the estimates measure that dependence from the insurer’s side: CyberCube lists the ease with which companies fell back on alternative communication channels to email among the factors behind its estimate. The framework predates the outage and does not discuss it.

Microsoft 365 outage, 12-14 November 2026: about 38 hours in total and about 18 hours of severe disruption per CyberCube, 15 hours 17 minutes from alert to mitigation per Microsoft, against waiting periods of up to 12 hours
About 18 hours of severe disruption ran past the 8 to 12 hour waiting periods CyberCube cites. Sources: CyberCube press release, 16 November 2026; Microsoft’s preliminary post-incident review as reported by The Register; 15 hours 17 minutes is our arithmetic.

What Is Not Established

No insurer has reported a claims total for this outage in the texts we read. All four estimates are preliminary: CyberCube said it will reassess if material new information emerges, and Reuters reported that Kovrr’s figure assumed the outage would be resolved by 19:00 GMT on 13 November.

CyberCube did not publish an economic-loss figure, and its model inputs are not public. We did not read the Morningstar DBRS estimate directly; it is as Insurance Business reported it. CyberCube was not contacted for this piece.

This Week In The AI Supercycle

AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source

This week’s issue: the Nvidia leadership change, read as the AI build-out losing its central banker: who now finances the GPU landlords, backstops the data centres and sponsors open models, and why two labs are becoming the bank.

Read the full issue →

Business Engineer Framework

Enterprise AI: From Software to Substrate

The Business Engineer framework on why enterprise platforms become layers other systems depend on.

Read the Map of AI →

The Bottom Line

CyberCube puts insured losses from the Microsoft 365 outage most likely under $100 million and at most $350 million, a 0% to 2% hit to global cyber premium. That is less than about $5.6 million per severe hour and below the low end of its own CrowdStrike range, by our arithmetic, while Kovrr’s estimate of around $700 million is 7 times higher.

95,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.

A note on sourcing. We read in full CyberCube’s press releases of 16 November 2026 (09:04 UTC) and 13 November 2026, its 25 July 2024 CrowdStrike estimate, Marsh Re’s 13 November briefing, two Reuters reports carried in full by Business Recorder (13 and 16 November) and Insurance Business’s 16 November report. The per-hour figure, the gaps between estimates and the ratios are our own arithmetic. CyberCube was not contacted for this piece.

Sources: CyberCube: Less Than $100M Global Insured Losses From M364 Outage (16 Nov 2026) · CyberCube: CrowdOut insured loss estimate (25 Jul 2024) · Reuters via Business Recorder: Kovrr $700 million estimate (13 Nov 2026) · Insurance Business: loss estimates range from minimal to US$700 million (16 Nov 2026) · Marsh Re: Delivery failed, Microsoft 365 outage (13 Nov 2026)

Scroll to Top
FourWeekMBA