Downtime cost is the money your business loses while a system is down. The downtime cost calculator turns an outage into a dollar figure, combining lost revenue, idle staff wages, and the cost of the recovery work.
An outage is usually reported in minutes, but a business case is written in dollars. Until you translate one into the other, it is hard to say whether a redundant server, a better monitoring tool, or a faster incident process is worth paying for.
How downtime cost is calculated
The total cost has three parts. Lost revenue is the revenue the affected service would have earned during the outage. Idle labor is the wages of the staff who could not do their jobs while the system was down. Recovery cost is the cost of the team’s time spent restoring service.
The formula for each part is straightforward. Lost revenue equals hourly revenue multiplied by the outage length in hours, scaled by the share of users or transactions affected. Idle labor equals the number of affected employees multiplied by their average loaded hourly cost and the outage length. Recovery cost equals the hours spent fixing the problem multiplied by the hourly cost of the people doing the fixing.
Add the three parts together for the total. The calculator asks for each input separately so you can see which part dominates — for a retailer it is usually revenue, for an office it is usually idle labor.
Worked example
A small online store earns $1,200 per hour during business hours. Its checkout goes down for 2 hours on a Saturday, and all orders stop. Lost revenue is $1,200 times 2, or $2,400.
The store has 6 staff who cannot process orders or answer customers while the site is down. Their loaded cost is $35 per hour each. Idle labor is 6 times $35 times 2 hours, or $420.
Two engineers spend 3 hours each restoring the service, at a loaded cost of $90 per hour. Recovery cost is 2 times 3 times $90, or $540. The total downtime cost is $2,400 plus $420 plus $540, or $3,360 for a two-hour outage.
How to use the result
Use the total to size the problem. A $3,360 outage that happens once a quarter costs about $13,400 a year, which is the budget you can justify spending to prevent it. That comparison is the whole point of the exercise.
Use the breakdown to find the cheapest fix. If lost revenue dominates, invest in redundancy or faster failover for the revenue system. If idle labor dominates, invest in workarounds that let staff keep working, such as an offline mode or a backup process.
If recovery cost dominates, the fix is usually process, not hardware. A runbook, a practiced restore, or better alerting can cut recovery hours dramatically, and those are the cheapest improvements in IT. The MTTR calculator shows how much faster recovery needs to be to move the number.
Tip: Run the calculation twice — once for a peak-hours outage and once for an overnight one. The two numbers are often ten times apart, and the peak figure is the one that should drive your resilience budget.
What the number does not include
This estimate leaves out SLA service credits, regulatory fines, and reputation damage, because those depend on contracts and circumstances no calculator can know. Treat the total as a floor: the real cost of a bad outage is usually higher, not lower.
It also assumes the outage affects the whole service. For a partial outage, reduce the revenue and staff numbers by the share affected, and say so in your notes. A clear, honest estimate beats a precise-looking one built on guessed inputs.
Frequently asked questions
What counts as the cost of downtime?
Lost revenue from orders or transactions that did not happen, wages paid to staff who could not work, and the cost of the recovery work itself. Reputation damage and SLA credits are real too, but harder to put a number on.
How do I estimate revenue lost per hour?
Take the revenue the affected service normally earns in an hour during the same time of day and day of week. For a store, use average hourly sales; for a SaaS product, use hourly subscription revenue at risk.
Should I count partial outages?
Yes, but scale the numbers. If half your users were affected, count half the revenue and half the affected staff. A degraded service still costs money, just less than a full outage.
Does downtime cost include the IT team's time?
Yes. The hours your engineers spend fixing the outage are hours they did not spend on other work. Count their loaded hourly cost in the recovery total.
How accurate is this estimate?
It is a planning figure, not an accounting total. It is accurate enough to compare options, set an SLA target, or justify a resilience investment, as long as you use honest inputs.