In the span of five days, two of the biggest names in American business went sideways, and neither one was hacked.
Last week, Microsoft 365 went dark for about 38 hours. Today, JPMorgan Chase spent the day working through a “technical issue” that slowed transactions for customers across the country. Different companies, different industries, same story: no attacker, no breach, just technology failing at scale, and thousands of businesses and customers feeling it in real time.
For business owners, these two events carry the same uncomfortable lesson about insurance: when the failure is not an attack, your cyber policy may not respond the way you think it does.
Today: the Chase slowdown
JPMorgan Chase said Monday that some transactions were taking longer than normal to process while the bank worked through a technical issue. Customers kept access to their accounts and funds, and according to a person familiar with the matter, the disruption was not tied to a cybersecurity issue. Downdetector logged more than 3,000 reports of disruption, and other major banks, Bank of America and Wells Fargo among them, saw spikes in reported problems as well. JPMorgan’s stock fell 2.6% on the day.
Insurance Journal’s report on the Chase disruption points out that tech challenges have been plaguing U.S. companies in recent weeks: the Microsoft outage, and even an airline ground stop tied to a single router in Arkansas.
Last week: the Microsoft outage
Microsoft has attributed the Nov. 12–14 outage to a technical issue introduced during a network capacity upgrade. Severe disruption lasted roughly 18 hours; the event ran about 38 hours in total. Insured loss estimates now range from $100 million to $700 million, per Insurance Journal. CyberCube expects the figure to land under $100 million, Morningstar DBRS puts it at $300 million to $500 million, and broker Acrisure estimates $700 million.
No hacker. No ransomware. No data breach.
And that one fact is where the coverage problems start.
The gap most business owners don’t know they have
Many cyber policies are built to respond to attacks: ransomware, breaches, social engineering. A plain system failure is a different animal.
As the analysts cited by Insurance Journal explain, coverage for an event like the Microsoft outage only responds where a policy extends business interruption coverage to non-malicious system failure at an outside provider. That protection is called contingent, or dependent, business interruption, and it is not automatic. Some policies restrict it to certain providers, or to a scheduled list of suppliers. If your platform is not within your policy’s definition, the claim may go nowhere.
Then there is the waiting period. Business interruption under a cyber policy typically carries a time retention of 8 to 12 hours before coverage begins. The Microsoft outage blew past that, but a shorter disruption, the kind that “only” costs you a day of productivity or a day of delayed transactions, may never trigger coverage at all. And even when coverage does respond, a business still has to demonstrate and quantify the financial loss that resulted.
Morningstar DBRS put it plainly: not all businesses will automatically be entitled to compensation. It depends on the terms and conditions of the policy. Economic losses that fall outside those terms are borne by the business itself.
We have seen this movie before
In 2024, the CrowdStrike outage, also caused by a faulty software update and not an attack, disrupted airlines, hospitals, banks, and retailers, and generated an estimated $400 million to $1.5 billion in insured losses. The Microsoft event is expected to land lower, in part because email, as CyberCube noted, is not in the critical transaction path of most businesses, and workarounds were widely available.
But the lesson compounds. The technology world is concentrated in the hands of a few key providers: one email platform, one bank, one payment network. When one of them stumbles, everyone downstream stumbles with it. Covered or not.
Three questions to ask about your cyber policy this week
- Does my policy include contingent (dependent) business interruption for outages at my outside providers?
- Does it cover non-malicious system failure, or malicious attacks only?
- What is my waiting period, and could my business absorb a loss shorter than that?
If you cannot answer those three questions from your policy, you do not have a cyber strategy. You have a hope.
At Varchas Risk Group, we read policies with business owners every week and point out exactly where the gaps are, before an outage does it for them. If you want a second set of eyes on your cyber coverage, the review is free. Learn more about cyber coverage.
This article is general information, not legal advice or a guarantee of coverage. Coverage depends on your policy’s terms, conditions, and exclusions.
