Downtime Cost Calculator

Estimate the cost of an outage from hourly revenue, conversion rate and downtime duration.

If your service goes down for an hour, how much revenue do you lose? This downtime cost calculator takes your monthly revenue and an outage duration (in minutes), converts it to an hourly revenue figure, and estimates the lost revenue for that outage, the per-minute cost, and an annualized figure if the same outage recurred every month. Amounts are shown as plain numbers with no currency symbol, so you can apply them to any currency you like.

It is handy for prioritizing incident response, justifying investment in redundancy and monitoring, and backing the cost section of a postmortem with a number. To see how much downtime an availability target allows, pair it with the SLA availability calculator, and for bandwidth spend as traffic grows use the bandwidth cost calculator.

Monthly revenueEnter a plain number with no currency symbol (in your own currency). Hourly revenue = monthly ÷ 730.Outage duration (minutes)How long this outage lasted, in minutes. E.g. 1 hour = 60.Affected traffic (%)Use 100 for a full outage, or the affected share for a partial outage.

Estimated loss

Hourly revenue	41,096
Cost per minute	685
Outage revenue loss	41,096
Annualized (assuming once per month)	493,151

Figures are in the same currency as the monthly revenue you entered.

This is an estimate. It excludes reputation, SLA credits, recovery labor, and churn.

How it is calculated

Hourly revenue is estimated by dividing your monthly revenue by the average hours in a month (about 730 = 365 days × 24 hours ÷ 12). That is multiplied by the outage duration and the share of traffic affected.

hourly revenue = monthly revenue ÷ 730
outage loss = hourly revenue × (outage minutes ÷ 60) × (affected % ÷ 100)
per-minute cost = hourly revenue ÷ 60 × (affected % ÷ 100)
annualized = outage loss × 12 (assumes one such outage each month)

Why the affected-traffic percentage?

A partial outage (one region, one feature, checkout only) does not lose all revenue. If only the payment path was broken and 60% of purchases were affected, enter 60% for a more realistic estimate. For a full outage, leave it at 100%.

Frequently asked questions

Why divide by 730 hours?

There are 8,760 hours in a year; divided by 12 months that is about 730 hours per month on average. Using the yearly average instead of 30 days (720h) or 31 days (744h) keeps comparisons stable across months.

Is this number my total loss?

No. This is a simple model that estimates lost revenue only. It excludes reputation damage, SLA-breach credits, recovery labor, and the lifetime value of churned customers, so the real total cost can be higher.

Can I enter an hourly revenue directly?

Enter (your hourly revenue × 730) in the monthly revenue field for the same effect. The tool only takes monthly revenue and converts it to hourly internally.

What currency is used?

None is assumed. Only numbers are shown, so interpret the result in the same currency as the revenue you entered (USD, EUR, KRW, etc.).

Are my inputs sent to a server?

No. All calculations run entirely in your browser, and the revenue and outage values you enter are never transmitted or stored anywhere.