Skip to main content
DataOptix

Tools

What does downtime actually cost you?

The cost of a data centre outage is the revenue the affected service would have earned, plus the staff time spent recovering it, across the whole time the service is down. That total is driven mostly by one number you can change: how long it takes to get a competent engineer in front of the rack.

Enter your own figures below. Everything is calculated in your browser from what you type, in whatever currency you work in.

Calculator

Your figures

What the affected service earns in an hour, in your own currency.

Cabinets that need checking once service is restored.

Fully loaded, in the same currency as above.

This is the number a response SLA changes.

An assumption, not a measurement. Change it to match your estate.

Estimated cost of this outage

25,900

Over 5 hours, in the currency you entered.

Lost revenue
25,000
Staff cost
900
Verification after restore
1 hour
Cost of each response hour
5,180

A 2-hour response instead of 4

On these figures, halving the time before an engineer reaches the site avoids 10,360 of this outage, by removing 2 hours of it. Block-hour customers are dispatched on our 2-hour SLA.

This is an estimate built from the numbers you entered, not a quote. We price each request on the city, the urgency and the skills it needs, so tell us the site and we will come back with a real figure.

The address bar holds your figures, so the link reproduces this result.

Method

How this is worked out

Every assumption is on this page and every input is yours to change. A calculator with a hidden coefficient is a persuasion device rather than a tool.

Total downtime is the hours before an engineer reaches the site, plus the time needed to verify each affected cabinet once service is restored. That verification time is the one assumption we supply, at 15 minutes per rack by default, and you can change it to match your own estate.

The cost is then lost revenue over those hours, plus the staff cost of everyone pulled onto the incident. The comparison at the end is simply the same calculation run twice, at a four-hour and a two-hour response, so the difference is expressed entirely in your own numbers.

What this deliberately does not do is compare that figure against what DataOptix would charge. We quote each request on the city, the urgency and the skills it needs, so any number we put here would be invented.

Questions about the calculation

Which currency does this use?

Whichever one you enter. The calculator does no conversion and attaches no currency symbol, because it works purely with the figures you type in.

Why does the rack count matter?

Because restoring power or connectivity is not the end of an outage. Someone still has to check each affected cabinet came back correctly, and on a large estate that verification is a meaningful part of the total time.

Does this tell me what DataOptix costs?

No. It estimates what an outage costs you, using your own numbers. Pricing depends on the city, the service model, the urgency and the skills required, so we quote each request rather than publishing a rate card.

Is the result stored anywhere?

No. The calculation runs in your browser and nothing is sent to us. Your figures appear in the page address so you can share or bookmark the result, which also means you should think before sharing a link containing commercially sensitive numbers.

How accurate is it?

It is exactly as accurate as the figures you put in. Treat it as a way to size the problem and to see how much of the cost is response time, rather than as a precise forecast of any particular incident.

Response time is the part you can change

Tell us the site, the task and the urgency. A coordinator replies within 2 business hours.