When a network goes down, the number most businesses reach for first is lost sales during the outage window. That’s real, but it’s usually the smallest piece of the actual cost. Once you account for productivity loss, recovery labor, and the longer-tail effects, an outage that “only lasted three hours” often costs far more than three hours of revenue.
What Actually Gets Counted (and What Usually Doesn’t)
Lost transactions or sales — the obvious, easy-to-estimate piece, and the one most commonly cited.
Idle labor — every employee who can’t work because they can’t reach shared drives, cloud applications, VoIP phones, or internal systems is still being paid during the outage. For a 50-person office, three hours of full-staff downtime is three hours of fully loaded payroll cost producing nothing.
Recovery labor — IT staff time spent diagnosing and fixing the issue, which is often disproportionate to the outage length itself. A three-hour outage frequently involves considerably more than three hours of IT time once you count diagnosis, the fix itself, and verification afterward.
Data loss or corruption — if the outage was caused by a hardware failure rather than a clean restart, there’s real risk of data loss depending on what was mid-transaction at the time.
Customer trust — harder to quantify, but real. A customer-facing outage during business hours affects perception in a way that’s disproportionate to the actual downtime duration, especially for repeat B2B relationships.
Why Single Points of Failure Are the Most Common Root Cause
In our assessments, the majority of “unexplained” or recurring outages trace back to a single point of failure that nobody had explicitly identified as one — a single ISP circuit with no failover, a core switch with no redundant pair, a firewall that’s the sole path for all traffic with no secondary unit. These aren’t exotic failure modes; they’re the direct, predictable consequence of infrastructure that grew without a redundancy plan.
How an Assessment Catches This Before It Costs You
A network assessment specifically maps failure domains — asking “if this device or link failed right now, what happens?” for every critical piece of infrastructure. This surfaces single points of failure while they’re still a line item on a remediation roadmap, not an active outage.
It also documents actual failover behavior, not assumed failover behavior. We frequently find “redundant” configurations that were set up correctly once but never actually tested — meaning the failover path exists on paper but doesn’t function when it’s actually needed.
Doing the Math for Your Business
A useful exercise before your next budget conversation: take your fully loaded hourly labor cost across affected staff, add your average hourly revenue during business hours, and multiply by your worst recent outage duration. Compare that number to the cost of addressing the single point of failure that caused it. In most cases we’ve seen, the math isn’t close — the fix costs a fraction of a single repeat incident.
If you want to see how failure-domain findings get documented and prioritized in practice, our sample network assessment report shows the full format, including a remediation roadmap example.