Methodology

Five inputs. One transparent formula.

Every number this calculator produces comes from five inputs and four simple steps — no hidden model, no black box. This page walks through exactly how the math works, using the calculator's own default example.

how to calculate cost of downtime downtime cost formula SLA budget calculation hidden outage tax explained

Walk through the formula Use the calculator

Scroll for the worked example

49h Annual outage hours in the worked example

$12.9M Resulting annual cost, direct + hidden

Step by step

The same four steps behind every page on this site.

Worked using this site's own default example: 850 systems, $180 revenue impact per system-hour, 3.5-hour MTTR, 14 incidents a year, and a 99.9% SLA target.

Step 1 — Annual outage hours MTTR × incident frequency = 3.5 hours × 14 incidents = 49 hours of downtime per year. This is the raw exposure before any dollar figure enters the picture.

Step 2 — Direct loss Systems affected × revenue impact per system-hour × annual outage hours = 850 × $180 × 49 = $7,497,000. This is the cost a finance team would recognize immediately — lost revenue or productivity for the time systems were down.

Step 3 — SLA budget and breach 8,760 hours per year × (100% − SLA target) = 8,760 × 0.1% = 8.76 hours allowed under a 99.9% target. Annual outage hours (49) minus that budget leaves 40.24 hours over budget — the input that drives how severe the hidden-cost multiplier below becomes.

Step 4 — Hidden outage tax A risk-weighted percentage of the direct loss, starting at 18% and scaling up with how far over SLA budget you run and how frequently incidents occur, capped at 72% of direct loss. In this example the breach is severe enough to hit the cap: $7,497,000 × 72% = $5,397,840.

Total annual cost Direct loss + hidden outage tax = $7,497,000 + $5,397,840 = $12,894,840 — the number this exact combination of inputs produces on the calculator today.

Why it's built this way

The hidden tax isn't padding — it's the point.

Most downtime calculators stop at direct loss. This one doesn't, because direct loss is rarely the number that changes minds in a budget conversation.

Direct loss alone understates the case

Compliance review, SLA credits, customer churn, and remediation labor rarely show up in a simple revenue-times-hours calculation — the hidden tax exists specifically to represent them without requiring you to model each one separately.

The multiplier responds to your specific risk

A team well within its SLA budget sees a hidden tax near the 18% floor. A team running chronically over budget sees it climb toward the 72% cap — the formula reflects that risk compounds, it doesn't stay flat.

Every input is yours to challenge

Systems affected, revenue impact, MTTR, frequency, and SLA target are all editable on every calculator page — the formula is fixed and transparent, but the inputs should always be your own operational data, not this page's illustrative defaults.

FAQ

The formula, answered.

Questions that come up when someone wants to defend or challenge this model's assumptions.

Why does the hidden tax cap at 72%? The cap keeps the model from producing an unbounded multiplier for extreme inputs — it represents a ceiling on how much indirect cost is credible to attribute to a single outage pattern, based on the qualitative severity tiers built into the formula.

Why does frequency affect the hidden tax, not just direct cost? Frequent incidents compound organizational fatigue, erode customer patience faster than isolated events, and increase the odds that a stakeholder review escalates the cost beyond the immediate outage — this is captured as a modest additional pressure term, separate from the SLA-breach pressure.

Can I get a lower hidden tax by improving my SLA target on paper? No — the SLA budget is derived from your target and compared against your actual outage hours. Raising the target without reducing MTTR or frequency increases your breach, not decreases it. See scenario planning for a worked example of this exact case.

Is this the same formula used across every calculator on the site? Yes — every cost-per-X page, industry page, and the general calculator all run this exact formula; only the default input values differ to reflect each context.

Your turn

Now run it with your own numbers.

You've seen exactly how the math works. Replace the five inputs with your own data for a real estimate.

Open the calculator Build a business case