~$5,000+ per minute
Derived from enterprise per-hour benchmarks above $300,000 (ITIC 2024) — roughly $5,000 or more per minute for the median large enterprise.
Cost per minute
Every minute down has a price tag.
Cost per minute is the finest-grained view of downtime cost — the number that makes faster detection and faster acknowledgment pay for themselves. Enter your fleet size, revenue impact, MTTR, incident frequency, and SLA target below.
Scroll for benchmarks
Why minutes matter
Detection speed is a cost lever, not a vanity metric.
Mean time to acknowledge (MTTA) sits upstream of MTTR. Every minute an incident goes undetected is a minute added to the bill at the same marginal rate — which makes the per-minute number the natural unit for justifying monitoring and on-call investment.
Cost per minute
Cost per hour divided by 60 — the base rate every incident-review minute is billed at.
MTTA impact
Shaving five minutes off detection time removes five minutes of direct loss from every incident, compounded across annual incident frequency.
Alert noise cost
Noisy alerting delays acknowledgment indirectly — the minutes lost to triage are the same minutes this rate prices.
Escalation cost
Each escalation hop before the right responder engages adds minutes; at the per-minute rate, on-call routing becomes a budget line, not just a process question.
Benchmarks
What a minute costs at scale.
Per-minute figures are usually derived from per-hour benchmarks. Use them as a sanity check against your own calculated rate above.
$5,600 per minute
The often-cited Gartner benchmark (2014, directional) — still widely referenced despite its age, and a useful upper anchor.
$20–$85 per minute
Typical range for small businesses, translated from the $1,000–$5,000 per hour SMB benchmark.
FAQ
Cost per minute, answered.
Questions that come up when the per-minute framing meets a real incident review.
How do I calculate cost per minute of downtime?
Calculate the cost per hour (servers affected times revenue impact per server hour), then divide by 60.
Why use per-minute instead of per-hour?
Per-minute framing makes the marginal cost of detection delay and escalation time explicit, which is more persuasive in incident reviews focused on MTTA and MTTR than an hourly or annual figure.
Does the per-minute rate change during an incident?
The base rate is usually treated as constant for modeling, though real incidents often have a ramp — the first minutes cost less as traffic fails over, and later minutes can cost more as backlogs and secondary failures build.
How does this relate to cost per hour and per day?
All three are the same underlying rate at different time scales. See the cost per hour and cost per day calculators, or the full annual model.
Share