Estimate the cost of downtime. Compare annual cost at your current SLA vs upgrading to the next tier.
Built from your revenue/min, affected users, support surge and a reputational drag of 1.5×. That's the downtime budget your current SLA tier permits.
Cost = (revenue/min × affected %) × minutes + (support surge × hours), multiplied by reputational factor.
| SLA tier | Downtime / year | Downtime / month | Cost impact | Annual $ |
|---|---|---|---|---|
99% 2 nines | 3.7d 5,256 min | 7.3h 438 min | $954.0k | |
99.9% 3 nines | 8.8h 526 min | 44m 44 min | $95.4k | |
99.99% 4 nines | 53m 53 min | 4.4m 4 min | $9.5k | |
99.999% 5 nines | 5.3m 5 min | 26s 0 min | $954 | |
99.9999% 6 nines | 32s 1 min | 3s 0 min | $95 |
A 1-hour outage during peak load costs 2.5× a quiet-hour outage. Weight your risk accordingly when scheduling deploys / maintenance.
| Industry | $/min | Note |
|---|---|---|
| Retail (e-commerce) | $3,200 | cart-abandonment sensitive |
| Finance / trading | $8,800 | missed transactions |
| Healthcare | $9,300 | regulatory + clinical impact |
| SaaS / software | $5,600 | Gartner average |
| Manufacturing | $4,200 | halted production lines |
| Media / streaming | $2,500 | ad-revenue loss |
| Telecommunications | $7,900 | — |
| Logistics | $3,800 | — |
Source: Gartner 2024 Downtime Cost Study + ITIC 2024 Cost of Downtime report. Averages across mid-enterprise orgs.
Assumes downtime is evenly distributed. Real-world outages cluster — use Gartner's 80/20 heuristic (80% of cost from top 20% of outages) as a second data point.
Service level math. Pick an uptime target and a measurement window — see allowed downtime, or enter actual downtime and find out if you breached.
Structured PIR generator. Severity, timeline, impact, root cause, action items, lessons — exports as markdown or prints for the all-hands.
Generate a rotation from a team list. Daily or weekly shifts, custom handoff time, ICS calendar export. Team mode shares the schedule across the workspace.
Estimate the cost of downtime. Compare annual cost at your current SLA vs upgrading to the next tier.
Built from your revenue/min, affected users, support surge and a reputational drag of 1.5×. That's the downtime budget your current SLA tier permits.
Cost = (revenue/min × affected %) × minutes + (support surge × hours), multiplied by reputational factor.
| SLA tier | Downtime / year | Downtime / month | Cost impact | Annual $ |
|---|---|---|---|---|
99% 2 nines | 3.7d 5,256 min | 7.3h 438 min | $954.0k | |
99.9% 3 nines | 8.8h 526 min | 44m 44 min | $95.4k | |
99.99% 4 nines | 53m 53 min | 4.4m 4 min | $9.5k | |
99.999% 5 nines | 5.3m 5 min | 26s 0 min | $954 | |
99.9999% 6 nines | 32s 1 min | 3s 0 min | $95 |
A 1-hour outage during peak load costs 2.5× a quiet-hour outage. Weight your risk accordingly when scheduling deploys / maintenance.
| Industry | $/min | Note |
|---|---|---|
| Retail (e-commerce) | $3,200 | cart-abandonment sensitive |
| Finance / trading | $8,800 | missed transactions |
| Healthcare | $9,300 | regulatory + clinical impact |
| SaaS / software | $5,600 | Gartner average |
| Manufacturing | $4,200 | halted production lines |
| Media / streaming | $2,500 | ad-revenue loss |
| Telecommunications | $7,900 | — |
| Logistics | $3,800 | — |
Source: Gartner 2024 Downtime Cost Study + ITIC 2024 Cost of Downtime report. Averages across mid-enterprise orgs.
Assumes downtime is evenly distributed. Real-world outages cluster — use Gartner's 80/20 heuristic (80% of cost from top 20% of outages) as a second data point.
Service level math. Pick an uptime target and a measurement window — see allowed downtime, or enter actual downtime and find out if you breached.
Structured PIR generator. Severity, timeline, impact, root cause, action items, lessons — exports as markdown or prints for the all-hands.
Generate a rotation from a team list. Daily or weekly shifts, custom handoff time, ICS calendar export. Team mode shares the schedule across the workspace.