How-to
How to Calculate Cost of IT Downtime: A Step-by-Step Formula
Table of Contents
- Why IT Downtime Cost Matters More Than Most SMBs Think
- The Four Cost Buckets Every Downtime Estimate Needs
- The Cost of Downtime Formula: Lost Revenue, Productivity, and Recovery
- Calculating IT Downtime Cost per Hour for Your Business
- Using an IT Downtime Cost Calculator Without Guessing
- Business Downtime Cost Examples Across Three Operating Models
- Separating Direct Costs from Indirect and Opportunity Costs
- Turning Your Downtime Number into a Prevention Decision
- Frequently Asked Questions
Last Updated: October 31, 2026
Why IT Downtime Cost Matters More Than Most SMBs Think
Published downtime benchmarks often put the average cost of an outage in the hundreds of thousands of dollars per hour across large organizations. That number is almost useless to a 40-person business.
Most guides hand you a scary hourly average and stop there. Averages hide everything that matters: a law firm and an e-commerce store lose money in completely different ways when the network drops.
Below, we show you exactly how to calculate cost of it downtime step by step, with a reusable formula, three worked examples, and a worksheet you can fill in today. For the incident side, see our guide on how to minimize downtime during a cyber attack.
The Four Cost Buckets Every Downtime Estimate Needs
Every credible downtime estimate sorts losses into four buckets. Miss one and your total is too low. Double count one and your total is fiction.
The four buckets:
- Lost revenue or production, sales you couldn't make or output you couldn't ship.
- Lost productivity, paid hours that produced nothing while systems were down.
- Recovery costs, repair, remediation, overtime, and vendor callouts.
- Indirect costs, churn, reputation damage, and missed opportunity.
A Gatling's downtime cost breakdown uses the same core structure: revenue per hour times downtime hours, plus recovery costs, lost productivity, and reputational damage.
The catch is that buckets 1 and 2 overlap if you are careless. More on that next.
Avoid Double Counting When You Add the Buckets
Double counting is the most common error we see in downtime math. It happens when the same lost dollar gets claimed twice.
Say a sales team of six can't work for four hours. You count their salaries as lost productivity, then also count the deals they didn't close as lost revenue. If those deals would have closed anyway once systems returned, you counted the same hours twice.
The fix is a simple rule:
- Count lost productivity only for work that never gets recovered.
- Count lost revenue only for sales that are permanently lost.
- If work catches up later, the cost is delay, not loss.
Apply that filter and your business downtime cost estimate drops, but it becomes defensible. A number you can defend beats a scary number you can't.
The Cost of Downtime Formula: Lost Revenue, Productivity, and Recovery
The cost of downtime formula is: (hourly revenue × downtime hours × impact percentage) + lost productivity + recovery costs + indirect costs.
Here is the formula written out:
Total outage cost = lost revenue + lost productivity + recovery costs + indirect costs
Where:
- Lost revenue = hourly revenue × hours down × impact percentage
- Lost productivity = affected employees × hourly labor cost × hours down × recovery factor
- Recovery costs = repair, remediation, overtime, and vendor fees
The impact percentage is the share of normal activity that actually stops. A full network outage might hit 100%.
The recovery factor is the share of stalled work that never comes back. If your team catches up over two days, that factor is low.
Published guidance from Xurrent's downtime calculation method takes the same approach: establish revenue per hour, add productivity and recovery costs, then factor in uptime and service-level commitments.
Calculating IT Downtime Cost per Hour for Your Business
IT downtime cost per hour is your total annual downtime loss divided by total annual downtime hours. To get there, start with one hour of outage and build up.

Follow these steps:
- Find hourly revenue. Take annual revenue and divide by operating hours per year. A business open 2,500 hours a year with $5 million in revenue earns $2,000 per hour.
- Set the impact percentage. Ask what share of that revenue stops during an outage. Be honest, not dramatic.
- Add hourly labor cost. Multiply affected employees by their hourly cost.
- Add recovery cost per hour. Divide last year's repair and remediation spend by outage hours.
- Sum the four figures. That is your cost per hour.
Run this once per system, not once per company. Your VoIP platform and your order management system have different impact percentages, and averaging them hides the risk.
A common mistake is using total revenue instead of revenue per operating hour.
Using an IT Downtime Cost Calculator Without Guessing
An IT downtime cost calculator is only as good as the inputs you feed it. The tool does the arithmetic; you supply the judgment. Most calculators ask for revenue and hours down, then return a single scary number.
This section gives you the worksheet behind the calculator so you can reproduce the estimate yourself, see every assumption, and present a range instead of a false-precision point estimate.
The Downtime Cost Worksheet
Fill in each row. Leave a cell blank if you do not have the input yet; a blank is more honest than a guess.
| Input | Symbol | Your value | Notes |
|---|---|---|---|
| Annual revenue (or production value) | R | ______ | Use the revenue that depends on the affected system |
| Annual operating hours | H | ______ | 2,080 for a standard office; 8,760 for 24/7 |
| Revenue per operating hour | r = R ÷ H | ______ | The base rate of loss |
| Outage duration (hours) | t | ______ | Use your last 12 months' average, not a worst case |
| Impact percentage | i | ______ | Share of normal activity that stops (0-100%) |
| Affected employees | n | ______ | Headcount whose work stops |
| Fully loaded hourly labor cost | c | ______ | Salary + benefits + overhead ÷ annual hours |
| Recovery factor | f | ______ | Share of stalled work that never comes back (0-1) |
| Recovery and remediation spend | m | ______ | Repair, overtime, vendor callouts |
| Expected churn and reputation cost | k | ______ | Estimate separately; do not fold into revenue |
Formulas:
- Lost revenue = r × t × i
- Lost productivity = n × c × t × f
- Recovery costs = m
Handling Uncertainty with Low, Expected, and High Scenarios
Every input above is uncertain. Instead of picking one number, run three scenarios and present the range. A common pattern is to set the impact percentage and recovery factor at low, expected, and high values while holding the other inputs fixed.
| Scenario | Impact % | Recovery factor | What it represents |
|---|---|---|---|
| Low | 50% | 0.10 | Partial degradation, most work recovers |
| Expected | 80% | 0.30 | Typical outage for your system |
| High | 100% | 0.60 | Full outage, significant permanent loss |
Run the formula three times. The expected case drives your decision; the high case tells you whether you can survive the downside; the low case keeps you from over-insuring a low-impact system.
Before You Touch Any Calculator
Gather five inputs first:
- Annual revenue and annual operating hours
- Headcount affected by a typical outage
- Average fully loaded hourly labor cost
With those five numbers, any calculator becomes useful. Without them, you are just moving guesses around a screen. The worksheet above is the transparent version of the same calculation, and it is the one you can defend in a budget conversation.
Business Downtime Cost Examples Across Three Operating Models
Business downtime cost examples matter because the same outage hits different companies in different places. The three models below use the same four-bucket formula, but each shows every input, every assumption, and a low/expected/high range. None are real client figures; they are illustrative models built to show the mechanics.
Example 1: A 40-Person Professional Services Firm
A 40-person firm bills by the hour. When email and file access drop for four hours, billable work stops.
Inputs and assumptions:
- 25 billable staff
- $150 per billed hour
- 60% of paid time is typically billable
Calculation:
- Normal billable output per hour = 25 staff × $150 × 0.60 = $2,250/hour
- Lost billing during outage = $2,250 × 4 = $9,000
- Permanently lost billing = $9,000 × 0.30 = $2,700
Sensitivity:
- Low case (80% recovery, no momentum loss): about $6,550
- High case (50% recovery, full momentum loss): about $11,050
The lesson: for services firms, the biggest cost is usually idle labor and permanently lost billing, not lost sales. The range matters more than the point estimate.
Example 2: An E-Commerce Retailer
An online store with $8 million in annual online revenue earns about $900 per hour. A four-hour checkout outage at 100% impact removes $3,600 in sales, and some of those customers never return.
Inputs and assumptions:
- $8,000,000 annual online revenue
- 8,760 operating hours per year (24/7 storefront)
- Revenue per hour = $8,000,000 ÷ 8,760 = about $913/hour
Calculation:
- Lost sales during outage = $913 × 4 = $3,652
- Permanently lost sales = $3,652 × 0.15 = $548
- Recovery costs = $1,200
Sensitivity:
- Low case (5% permanent loss, 1% churn): about $2,383
- High case (30% permanent loss, 4% churn): about $6,296
For retailers, customer churn and permanently lost sales dominate the math, and the churn assumption swings the total more than the outage length does.
Example 3: A Light Manufacturing Operation
A plant running 200 units per hour at $40 gross margin per unit loses $8,000 in margin for every hour the line control system is down. Four hours is $32,000 in lost production, before overtime to catch up.
Inputs and assumptions:
- 200 units per hour
- $40 gross margin per unit
- 4-hour outage
Calculation:
- Lost margin during outage = 200 × $40 × 4 = $32,000
- Permanently lost margin = $32,000 × 0.40 = $12,800
- Overtime premium = $3,000
Sensitivity:
- Low case (80% recovered, no overtime): about $10,400
- High case (20% recovered, full overtime): about $32,600
For manufacturers, lost production and recovery overtime are the whole story, and the recovery factor is the single input that moves the total most.
| Model | Biggest cost driver | What to measure first | Expected total (4-hr outage) |
|---|---|---|---|
| Professional services | Idle labor and lost billing | Billable hours lost | $9,250 |
| E-commerce | Lost sales and churn | Revenue per hour online | $3,748 |
| Manufacturing | Lost production | Units per hour × margin | $19,800 |
Separating Direct Costs from Indirect and Opportunity Costs
Direct costs are cash that leaves or fails to arrive during the outage. Indirect costs are the slower damage that shows up in later months.
Direct costs include:
- Lost sales and lost production
- Idle labor you still paid for
- Repair and remediation invoices
Indirect costs include:
- Customer churn after a visible failure
- Reputational damage and slower sales cycles
- Missed deadlines and contract penalties
The distinction matters: direct costs are easier to prove, so they belong in the budget conversation.
If you are weighing prevention spend against downtime loss, our breakdown of how to calculate total cost of ownership for managed IT puts both sides on the same page.
Turning Your Downtime Number into a Prevention Decision
Once you have a defensible cost per hour, the decision becomes arithmetic. Compare your annual expected downtime loss against the cost of preventing it.
Use this worksheet:
- Expected outages per year: ______
- Average hours per outage: ______
- Cost per hour (from your formula): $______
If the ratio is above 2:1, prevention usually pays for itself. Below 1:1, you may be over-insuring a low-impact system.
This is where managed support can change the math. Get a fully managed network, endpoint security, VoIP, and unlimited helpdesk to see what predictable IT coverage looks like. VegaMSP offers fully managed network services, endpoint security, VoIP integration, and unlimited helpdesk support through its Secure-IT-In-The-Box model. Explore the fully managed service to see what predictable IT coverage looks like, or read why managed IT supports business continuity before you commit.
Frequently Asked Questions
How do you calculate the cost of IT downtime?
Start with your hourly revenue and multiply it by the hours systems were down. Add lost productivity by multiplying affected employees, their hourly labor cost, and the impact percentage of their lost work. Add recovery and repair costs, then add customer churn and reputational damage as a separate line. The result is your total outage cost. Build the estimate from your own revenue per hour, productivity, and recovery inputs rather than copying a benchmark, because the same outage costs a law firm and a factory very different amounts.
What costs should be included in an IT downtime estimate?
Include four buckets: lost revenue or lost production, lost employee productivity and idle labor, recovery and remediation costs, and customer impact such as churn and reputational damage. A common downtime formula adds revenue loss, recovery costs, lost productivity, and reputational damage together. Keep direct cash costs separate from indirect and opportunity costs so you can see what actually left the bank account. Planned downtime, such as a scheduled migration window, usually carries lower customer impact than an unplanned outage, so note which type you are modeling.
How do you calculate lost revenue and productivity during an outage?
For lost revenue, divide annual online revenue by annual operating hours to get hourly revenue, then multiply by hours down and by the percentage of transactions the outage actually blocked. For productivity, multiply affected employees by their hourly labor cost, then by the impact percentage of work they could not do. A team of 20 at $45 per hour with 60% impact over four hours loses $2,160 in idle labor. Use conservative impact percentages and run a low and high scenario so your IT downtime cost per hour lands in a defensible range.
How can a business reduce the cost of IT downtime?
Reduce either the hours down or the cost per hour. Shorten outages with monitoring, tested backups, and a documented disaster recovery plan. Lower the cost per hour by cross-training staff, keeping manual workarounds ready, and moving critical workloads to redundant infrastructure. Managed services help because monitoring and patch management catch failures before they become outages. Track your cost per incident over time and compare it to what you spend on prevention; that ratio is the clearest argument for changing how your IT is supported.
The uncomfortable truth is that most businesses only calculate downtime cost after an outage forces them to. Doing it first turns a vague worry into a number you can act on. Get started with VegaMSP and replace the guesswork with a support model built around uptime.