A New York insurtech wrote a policy that pays out automatically when AWS, Azure or Google Cloud stops working. Then, on one July morning, CrowdStrike proved the whole thesis was worth billions.
Ask an insurer to cover the risk that the internet stops working and, for most of the last two decades, you would have been laughed out of the room. Cloud providers sell reliability; that is the entire point. Yet everyone who runs a business online knows the quieter truth - the cloud does go down, and when it does, the losses arrive all at once, for thousands of companies, on the same afternoon. Parametrix was built in 2019 around that inconvenient fact.
The New York company, led by co-founder and CEO Jonathan Hatzor, created what it describes as the first insurance category designed for technology downtime. Its policies do not cover a hacker or a stolen laptop. They cover the outage itself - the hours your storefront, your checkout, or your logistics dashboard sits dark because a data center you have never heard of, run by a provider you do not directly pay, went offline.
Most companies assume their cyber insurance has them covered. It usually does not. Standard cyber policies were written around data breaches and ransomware, and cloud-outage losses tend to be excluded, sub-limited, or buried under waiting periods long enough to erase the claim. That gap is the whole reason Parametrix exists.
Traditional business-interruption insurance does not help much either. It is slow, it is adversarial, and it was designed for a warehouse fire, not a synchronized global outage. You file, an adjuster investigates, and months later you negotiate. Parametrix's answer was to change the mechanism entirely.
"Cloud downtime is one of the most significant and rapidly growing risks, yet there was no proper solution available."Jonathan Hatzor, Co-Founder & CEO
The word in the company's name is the product. A parametric policy pays out when a measured parameter crosses an agreed line - in this case, a covered cloud provider being down beyond a set number of minutes across specified regions. If the trigger is met, the payment is owed. There is no debate about how much revenue you truly lost, no forensic accounting, no adjuster standing in your server room.
In practice that means claims settle in days rather than months. The trade-off is honesty: because the payout is tied to a public, objective event, the insurer and the insured both know exactly where they stand the moment the outage clears.
On July 19, 2024, a faulty CrowdStrike update took down Windows machines across the world. Airlines grounded flights, hospitals fell back to paper, payment systems froze. It was not a cloud outage in the strict sense, but it was exactly the kind of correlated, everyone-at-once technology failure Parametrix had spent five years modeling.
Within days, Parametrix published an estimate that became the headline number quoted everywhere: US Fortune 500 companies (excluding Microsoft) faced roughly $5.4 billion in direct financial losses, of which only an estimated $540 million to $1.08 billion was covered by insurance. The weighted-average hit worked out to about $44 million per company, ranging from $6 million in manufacturing to $143 million in aviation.
CrowdStrike outage - estimated direct loss by sector
US Fortune 500, July 19, 2024. Source: Parametrix analysis.
The report did two things at once. It put a defensible price on an event the whole business world had just lived through, and it demonstrated, in public, that the coverage gap Parametrix sold against was real and enormous. Few marketing campaigns land like a well-timed catastrophe model.
Underneath the insurance sits a monitoring engine, and it is arguably the harder half of the company. Parametrix continuously watches more than 750 data centers and tracks over 9,000 software, SaaS, PaaS and IaaS providers, measuring latency, connectivity and response codes with millisecond precision. Only a couple of years earlier that figure was 297 data centers - the surveillance footprint has grown roughly as fast as the risk.
This is what lets the company price a policy, decide whether a trigger was met, and - crucially - understand its own aggregation risk when a single AWS region can knock out thousands of insured customers simultaneously. It is sold to insurers and reinsurers as a platform in its own right, so they can see their exposure to concentrated cloud risk that would otherwise be invisible on a balance sheet.
"Our system continuously monitors and collects granular data on cloud performance across multiple metrics."Jonathan Hatzor
A single insurer cannot swallow the tail risk of the entire cloud failing. So Parametrix did something the reinsurance world had not seen before: it structured a catastrophe bond focused purely on cloud outages. Sponsored by reinsurer Hannover Re and called Cumulus Re, it lets capital-market investors take on cloud-downtime risk the way they already trade hurricanes and earthquakes.
The bond has grown every year, which is its own quiet endorsement - investors keep coming back, and none of the prior issues were triggered.
Cumulus Re - the first cloud-outage catastrophe bond
Size of each issuance, structured by Parametrix for Hannover Re.
In August 2026, AIG launched a parametric cloud-outage solution in the US, available as an endorsement for eligible cyber clients - and it runs on Parametrix's monitoring of those 750-plus data centers and 9,000-plus providers. When one of the largest names in global insurance builds a product on your data rather than reinventing it, the category has stopped being a pitch and started being infrastructure.
That is the shape of Parametrix's ambition. It sells policies directly, but it also wants to be the measurement layer other insurers depend on - the referee everyone agrees to trust when the question is simply "was the cloud down, and for how long?"
Parametrix operates as a Managing General Agent and a Lloyd's Coverholder backed by more than 20 Lloyd's syndicates, which means the paper behind its policies carries serious weight. Revenue comes from two directions: premiums on its parametric cloud-outage and business-interruption policies, priced against a customer's annual revenue and cloud footprint, and subscriptions from insurers and reinsurers who license its monitoring data.
The venture backing has followed the thesis. A $17.5 million Series A in 2021, led by FirstMark Capital - the firm's first-ever investment in Israel - was followed by a $27 million Series B led by Mundi Ventures, with Hannover Digital Investments and F2 Venture Capital alongside. The company puts its addressable market at roughly 1.6 million potential customers today, projected toward 4 million by 2027 as more of the economy runs on someone else's servers.
The honest competitor is not another startup; it is the status quo of doing nothing. Most companies self-insure cloud downtime by absorbing the loss and hoping the outage is short. Traditional cyber insurers occupy the adjacent ground, but their exclusions are precisely the space Parametrix built in. The company's edge is being early, holding the monitoring data, and having convinced reinsurers and a major carrier to stand behind it.
It is not a fit for everyone. Parametric cover pays on a trigger, not on your actual invoice, so a business whose losses do not line up neatly with measured downtime may find the payout imperfect. The model also leans on public, agreed-upon outage events - a subtle, partial or slow-burn degradation that never crosses the threshold may not pay at all. And the whole edifice depends on the monitoring being trusted as the source of truth. Parametrix has spent its existence making that bet, and so far the outages keep proving it right.
For a founder, the takeaway is almost annoyingly simple. Read the exclusions in the contracts everyone already signs. Find the risk that is obviously real, obviously growing, and conveniently uninsured. Then build the measurement system that makes it underwritable before the market realizes it needs you. The cloud was always going to go down. Parametrix just decided to be standing there with a check when it did.