Cost of Downtime Calculator

Estimate how an IT outage could affect your business. Enter your best estimates below to see potential productivity losses, additional expenses, and the impact of recurring downtime.

1. Business impact

Start with the employees and business activity affected by the outage.

Number of employees whose work is disrupted.

Use an average for the affected employees.

For example, 75 means employees lose about three-quarters of their productive capacity.

Use fractions of an hour if needed (e.g., 1.5 = 90 minutes).

Optional business-impact assumptions

Optional employer taxes and benefits as a percentage of wages. Added to the productivity-cost estimate.

Only include other hourly losses not entered elsewhere. Do not duplicate lost sales below.

Enter individual employee wages (up to 5)

Enter hourly wages for up to five employees. The calculator averages the wages you provide and uses that average instead of the manual average above. Leave unused fields blank.

No individual wages entered. The average hourly wage above is used.

2. Additional financial losses

These incident-level costs are added once per outage, not once per downtime hour. Leave any unknown or inapplicable item at $0.

Emergency support, troubleshooting, restoration, or replacement costs.

Additional expense to catch up after service is restored.

Enter either estimated unrecoverable revenue or estimated lost profit; choose one basis and label it in your own assumptions. Do not include losses already entered above.

SLA penalties, refunds, credits, or late-delivery fees.

Costs to recover data or recreate lost records.

Other one-off costs not included in another field.

Additional recovery time (optional)

Systems may be restored before the team returns to normal productivity. Estimate only the extra labor cost here; don't count the same overtime in both fields.

For example, the loaded hourly cost of staff working on recovery.

3. Downtime patterns

Estimate the cost of one incident or project the impact of similar incidents over a year.

Assumes each outage has roughly the same duration and cost.

Compare outage durations

See how estimated cost changes for 1-hour, 4-hour, and 8-hour outages. Other assumptions stay the same; one-off incident costs are counted once per scenario.

1-hour outage$—
4-hour outage$—
8-hour outage$—

Cost of Downtime Calculator

Estimate how an IT outage could affect your business. Enter your best estimates below to see potential productivity losses, additional expenses, and the impact of recurring downtime.

1. Business impact

Start with the employees and business activity affected by the outage.

Number of employees whose work is disrupted.

Use an average for the affected employees.

For example, 75 means employees lose about three-quarters of their productive capacity.

Use fractions of an hour if needed (e.g., 1.5 = 90 minutes).

Optional business-impact assumptions

Optional employer taxes and benefits as a percentage of wages. Added to the productivity-cost estimate.

Only include other hourly losses not entered elsewhere. Do not duplicate lost sales below.

2. Additional financial losses

These incident-level costs are added once per outage, not once per downtime hour. Leave any unknown or inapplicable item at $0.

Emergency support, troubleshooting, restoration, or replacement costs.

Additional expense to catch up after service is restored.

Enter either estimated unrecoverable revenue or estimated lost profit; choose one basis and label it in your own assumptions. Do not include losses already entered above.

SLA penalties, refunds, credits, or late-delivery fees.

Costs to recover data or recreate lost records.

Other one-off costs not included in another field.

Additional recovery time (optional)

Systems may be restored before the team returns to normal productivity. Estimate only the extra labor cost here; don't count the same overtime in both fields.

For example, the loaded hourly cost of staff working on recovery.

3. Downtime patterns

Estimate the cost of one incident or project the impact of similar incidents over a year.

Assumes each outage has roughly the same duration and cost.

Compare outage durations

See how estimated cost changes for 1-hour, 4-hour, and 8-hour outages. Other assumptions stay the same; one-off incident costs are counted once per scenario.

1-hour outage$—
4-hour outage$—
8-hour outage$—