Downtime Cost Calculator
Downtime cost combines lost revenue, wasted ads, recovery labour and an assumed conversion dip. The calculator estimates hourly revenue as monthly revenue ÷ 730. A ₹1,00,000-a-month store loses about ₹137 per hour offline. At 99.9% uptime, annual downtime is 8.76 hours and direct revenue exposure roughly ₹1,200.
For store owners, agencies and IT heads in India who want a rupee figure for an outage before choosing a hosting plan or SLA.
needed
- Price
- Free
- Signup
- None
- Built by
- WebJi®
- Support
- 24/7 email
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Work out your downtime cost
Runs in your browserFormula: revenue-per-hour × hours down + wasted ads + recovery labour + one week of the post-outage conversion dip. Compare the number with a plan that carries a real 99.9% uptime SLA.
What the downtime cost result means
The downtime cost result is a monthly scenario estimate that adds lost revenue, wasted ads, recovery labour and an assumed conversion dip. With the default inputs — ₹3,00,000 monthly revenue, 2 hours down, ₹15,000 of wasted ads, 3 recovery hours at ₹1,500 and a 10% dip — the total is ₹27,250, or ₹13,625 for each hour offline.
| Cost line | Working | Amount | Share of total |
|---|---|---|---|
| Lost revenue | ₹3,00,000 ÷ 730 × 2 hours | ₹822 | 3% |
| Wasted ads | Entered directly | ₹15,000 | 55% |
| Recovery labour | ₹1,500 × 3 hours | ₹4,500 | 17% |
| Conversion dip | ₹3,00,000 ÷ 4.33 × 10% | ₹6,928 | 25% |
| Total | Sum of the four lines | ₹27,250 | 100% |
Read the shares before the total. If ad spend dominates, the cheapest fix is an alert that pauses campaigns when the site errors. If the dip dominates, the outage is hurting trust, and fewer outages — not faster recovery — is the thing to buy.
How the downtime cost calculator works out each figure
The downtime cost calculator adds four lines: revenue per hour times hours down, entered ad spend, labour rate times recovery hours, and one week of revenue times the assumed dip percentage. Revenue per hour is monthly revenue divided by 730, the average number of hours in a 30.4-day month.
revenue per hour = monthly revenue ÷ 730
lost revenue = revenue per hour × hours down
recovery labour = rate per hour × recovery hours
conversion dip = (monthly revenue ÷ 4.33) × dip %
total = lost revenue + wasted ads + recovery labour + conversion dip
per hour down = total ÷ max(hours down, 1), when hours down > 0The 4.33 divisor models one week as a share of a month (52 weeks ÷ 12 months); it does not measure visitor behaviour. A store earning ₹1,00,000 a month runs at about ₹137 an hour on the 730-hour basis. For outages shorter than one hour, the displayed per-hour result divides by one, not the fractional duration; the total cost remains unchanged.
Downtime cost by uptime percentage: hours and rupees
Every uptime tier allows a fixed number of hours offline, and the direct revenue at risk equals the downtime percentage of your annual revenue. A year has 8,760 hours, so 99.9% uptime permits 8.76 hours down; for a ₹1,00,000-a-month store that is about ₹1,200, or 0.1% of ₹12,00,000.
| Uptime | Down per year | Down per month | Direct revenue at risk per year |
|---|---|---|---|
| 99.5% | 43.8 hours | 3.65 hours | ≈ ₹6,000 |
| 99.9% | 8.76 hours | 43.8 minutes | ≈ ₹1,200 |
| 99.95% | 4.38 hours | 21.9 minutes | ≈ ₹600 |
| 99.99% | 52.6 minutes | 4.38 minutes | ≈ ₹120 |
| 99.999% | 5.26 minutes | 26 seconds | ≈ ₹12 |
The table shows only the lost-revenue line. Ads, labour and the dip are charged per incident, not per minute, so ten short outages can cost more than one long one with the same total hours. Measured history matters more than the promised decimal; the guide to uptime explains how providers count it.
How accurate is a downtime cost estimate?
A downtime cost estimate follows its inputs: ads and labour can come from invoices, while the assumed conversion dip is a judgement call. It also assumes revenue is spread evenly across all 730 hours, which rarely holds for Indian retail.
- Peak hours: a store that books most orders between 7 pm and 11 pm loses far more per hour then. Enter peak-hour revenue scaled to a month if outages tend to hit during sales.
- Lead businesses: a clinic or coaching centre has no checkout. Use enquiries per month × conversion rate × average order value as monthly revenue.
- Dip percentage: start at 5–10% and compare your own conversion rate in the week after a past incident.
- What it leaves out: refunds, SLA credits received, staff idle time and lost organic rankings after repeated long outages.
Reducing the downtime cost once you know it
Downtime cost can be reduced in two ways: fewer or shorter outages, and lower expense per incident. WebJi® hosting carries a 99.9% uptime target measured monthly, with the history published on the network status page, and the SLA terms set out what the commitment covers.
- Watch it: set an external check so you hear about an outage before customers do — see uptime monitoring.
- Shorten recovery: tested restores cut the labour line; server backup solutions keep copies off the server.
- Remove shared risk: if the monthly total is large, a dedicated server or SLA-backed setup is quoted by email before payment, in INR with 18% GST added on the invoice.
Send your result to support@webji.services; the desk replies 24/7 in Hindi and English, with an average first reply under 60 minutes.
Frequently asked questions
Why does the calculator divide monthly revenue by 730?
730 is the average number of hours in a month: 8,760 hours a year divided by 12. It treats the site as open around the clock, which suits online stores. If you only trade 12 hours a day, the true figure while you are open is roughly double — ₹1,00,000 a month becomes about ₹274 an hour.
Should I count GST in the monthly revenue figure?
Use revenue before GST. Tax collected on a sale is passed to the government, so it is not money the outage takes from the business. Ad spend and recovery labour can be entered at what you actually paid, including any GST you cannot claim back as input credit.
Does a short outage hurt Google rankings?
A single short outage is usually absorbed with no lasting effect. Repeated errors or outages lasting most of a day can slow crawling and cost visibility, which is why the calculator leaves rankings out of the total — the effect is real but too uncertain to price per hour.
What uptime should an online store aim for?
99.9% is the practical floor for a store that sells around the clock: 8.76 hours down a year. If the calculator's per-hour figure runs into thousands of rupees, compare 99.95% or 99.99% setups against that number, and judge the provider on measured history rather than the advertised decimal.
Do I need to submit a form to calculate downtime costs?
No form submission is needed: the calculator updates its result in the browser as you change each input. There is no registration requirement. The website also uses analytics and support widgets, so consult the privacy policy before entering sensitive commercial figures; rounded scenario values are enough for planning.
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.