Data Center 19 November 2026
What does one hour of downtime really cost? A simple way to find out
Downtime costs more than lost sales. A simple formula to work out what an outage costs your organization, and how much resilience is worth buying.
CITS Global editorial team, 3 min read

Excerpt: You cannot decide how much resilience to buy until you know what an outage costs. Here is a simple way to work it out, with an example. Tags: downtime, business continuity, risk, resilience, planning
"We need high availability."
Almost every organization says it. Far fewer can answer the next question: how much should we pay for it?
The answer starts with one number: what an hour offline costs you. Once you have it, decisions about redundant power, a second site or a higher-tier facility become much easier to justify, or to say no to.
Start with the direct costs
These are the easy ones to count.
Lost revenue or transactions while systems are down Staff paid but unable to work Penalties or refunds owed under service agreements Emergency repair and overtime Then add the indirect costs
These are harder to measure and often larger.
Customers who leave or buy less afterwards Damage to reputation and trust Regulatory attention or reporting duties Management time spent on recovery instead of running the business A simple formula
Cost per hour offline = (revenue per hour × share of revenue affected) + (staff cost per hour × share of staff idle) + penalties + recovery costs
It is rough on purpose. A rough number is far better than none.
A worked example (illustrative numbers only)
Imagine a company where:
Revenue is ₹10,00,000 per hour, and 60% of it depends on the affected systems → ₹6,00,000 Staff cost is ₹2,00,000 per hour, and 50% of staff cannot work → ₹1,00,000 Contract penalties for the outage are ₹50,000 Emergency repair and overtime come to ₹50,000
Estimated cost: about ₹8,00,000 for every hour offline, before counting any lost customers or reputation damage.
Replace these with your own figures. The point is the method, not the numbers.
Use the number to decide If an hour offline costs little, a basic facility may be enough. If it costs a great deal, redundant power, cooling, network routes and a second site can pay for themselves quickly.
The goal is to match resilience to real risk, instead of buying the highest tier out of habit or the lowest to save money.
Two more questions every system needs
Different systems in the same company have very different answers. Ask for each one:
How long can we be down before it becomes serious? This is your recovery time objective. How much recent data can we afford to lose? This is your recovery point objective.
A payments system may need near-zero on both. An internal reporting tool may be fine with a day.
A quick way to start this week List your five most important systems. For each, estimate the cost of one hour offline using the formula. Write down the recovery time and data loss you could accept. Compare the results with what your current setup actually delivers.
The gaps you find are where to invest first.
CTA: Want help sizing resilience to your real risk? Write to enquiry@citsglobal.org.in or visit www.citsglobal.org.in, and our consulting team will help you work it out.
LinkedIn caption
"We need high availability."
Great. But how much is it worth paying for? 🤔
It starts with one number: what does one hour of downtime cost you?
Here is a simple way to work it out:
💰 Lost revenue 👥 Idle staff ⚖️ Penalties 🛠️ Recovery costs
Add them up, then compare the result with what your current setup delivers. The gap shows you where to invest first, and where you may be overspending.
Full guide with a worked example on our blog. 🔗 www.citsglobal.org.in ✉️ enquiry@citsglobal.org.in
Do you know what an hour offline costs your business? Tell us below.
#DataCenter #BusinessContinuity #Resilience #ICT #CITSGlobal

