- HŪMNZ Newsletter
- Posts
- The HŪMNZ Element: Issue 41 - What This Week's Outages Reveal About Your Business
The HŪMNZ Element: Issue 41 - What This Week's Outages Reveal About Your Business
When the systems you rely on fail, you find out how much of your business you never actually controlled. This week made that lesson hard to ignore.

💡 Editor's Note
As this goes out, a lot of the internet is having a bad week. Apple services are down for many users today. A Microsoft Outlook outage hit last week. A technical failure at one of the largest banks delayed transactions a day later.
None of it was caused by the businesses it disrupted. That is the point. Their operations stopped anyway, because the systems they run on belong to someone else.
An outage is not just an IT event. It is a live test of how much of your business you actually control, and most owners do not like the answer.
Before the next outage makes the decision for you, find out which systems your business cannot run without.
Five questions, 90 seconds, a read on your own operation straight away. No call to book, no gate.
Executive Brief
Bottom line: Your business depends on systems and vendors you do not own, do not control, and usually cannot fix. That dependency is normal and often smart. What is dangerous is not knowing how deep it runs until the day it fails.
The exposure is widespread. Across publicly reported outages tracked by Uptime Institute, roughly two-thirds trace back to third-party providers such as cloud, telecom, and hosting companies. The failure rarely starts in your building, but the lost revenue, the stalled orders, and the frustrated customers all land on you.
And it is expensive. In Uptime Institute's survey, 54% of organizations said their most recent significant outage cost more than $100,000, and one in five said it cost more than $1 million. Most leaders have never put a number on a single hour of downtime, which means they are carrying a risk they have never priced.
In 30 seconds
A modern business runs on systems owned by other companies, and an outage is what reveals that.
Roughly two-thirds of reported outages originate with third-party providers, not the affected business.
Most owners cannot say what an hour of downtime costs them, so the risk goes unmanaged.
Resilience is not an IT project. It is an operating discipline that protects both revenue and value.
⚠️ Four signals leaders should be watching this week
1. Do you know what your business actually runs on?
Signal: You could not list, from memory, the outside systems your operation stops without.
Evidence: The tools a business depends on accumulate quietly, one subscription and integration at a time, until no single person holds the full map. What is not mapped cannot be protected.
Implication: You cannot plan around a dependency you have never named. The first time you see the full list is usually during the outage, when it is too late to do anything with it.
Action: Write down the five systems that, if they went dark for a day, would stop your business. That short list is your real risk map, and most owners have never made it.
Related: The software every CEO buys twice
2. Do you know what an hour of downtime costs you?
Signal: You have never put a dollar figure on being unable to operate for an hour, a morning, or a day.
Evidence: As Uptime Institute found that 54% of organizations' most recent major outages cost more than $100,000, that number is rarely just lost sales. It includes idle staff, missed commitments, and customers who do not come back.
Implication: A risk you have not priced is a risk you cannot weigh. You end up either over-investing in protection you do not need or, far more often, under-preparing for a cost you never calculated.
Action: Estimate the cost of one full day down: lost revenue, paid but idle people, and recovery. That one figure tells you how much resilience is worth buying.
3. Do you have a plan for when, not if?
Signal: Your answer to a core system going down is to wait for it to come back.
Evidence: Outages are a routine feature of modern infrastructure, not a rare surprise. The businesses that recover fastest are the ones that decided what to do before it happened, not during.
Implication: Hope is not a continuity plan. When the only option is to wait, every hour of the outage is an hour your business has no move to make.
Action: For your single most critical system, write the one-page answer to a simple question: if this is down for a day, how do we keep serving customers? Even a rough plan beats none.
4. Is too much of your risk sitting with one provider?
Signal: A single vendor, platform, or region quietly underpins most of what you do.
Evidence: Concentration makes an outage worse. When one provider carries your email, your payments, and your data, a single failure takes all of it at once, and you recover on their timeline, not yours.
Implication: Convenience and concentration tend to arrive together. The setup that is simplest to run is often the one with the largest single point of failure buried inside it.
Action: Find the one provider your business can least afford to lose. Decide, in advance, what you would do for the first 24 hours without it.
Stat of the Week
54%
The share of organizations whose most recent significant outage cost more than $100,000, in Uptime Institute's survey. One in five said it cost more than $1 million.
The outage starts somewhere else. The bill arrives at your desk.
Sources: Uptime Institute, Annual Outage Analysis and Global Data Center Survey. Figure on third-party providers drawn from Uptime Institute's analysis of publicly reported outages, 2016 to 2024.
The Core Question
Dependence on outside systems is not a mistake to undo. No one is running payroll on paper again, and they should not. The mistake is treating that dependence as if it were your own reliable infrastructure, when it belongs to someone whose priorities are not yours.
The goal is not to control everything. It is to know exactly where you are exposed, what it would cost, and what you would do, before the day you have to.
If the system your business depends on most went down tomorrow morning, how long could you keep serving customers, and who already knows the plan?
The VALŪE lens: Resilience is not just protection, it is worth. A buyer examining your business looks hard at how it runs when something breaks, how concentrated your vendors are, and whether continuity depends on luck or design. A company that can absorb a common outage without stopping is lower risk, and lower risk is worth more. Fragility you have not addressed is a discount waiting to be found.
You cannot stop the systems you rely on from failing. You can decide, well before they do, how much of your business goes down with them.
Know a leader whose business would stop cold if one system went down? Send this on.
Until next time,
The HŪMNZ Element · Weekly Pulse
If this was useful, forward it to one person: a leader who assumes the systems they rely on will always be there.