Downtime cost calculator
Uptime percentages feel abstract; invoices don't. This turns your revenue and an uptime level into the money that downtime budget represents.
- revenue per hour
- —
- allowed downtime / year
- —
- revenue at risk / year
- —
How much does downtime cost per year?
The table assumes revenue arrives evenly around the clock (year = 365.25 days, month = one twelfth). If your traffic peaks hard — a store, a weekday B2B tool — an outage at the wrong hour costs a multiple of these averages.
| Revenue | Per hour down | at 99% | at 99.5% | at 99.9% | at 99.99% |
|---|---|---|---|---|---|
| $1,000/mo | $1.37 | $120 | $60.0 | $12.0 | $1.20 |
| $10,000/mo | $13.7 | $1,200 | $600 | $120 | $12.0 |
| $50,000/mo | $68.4 | $6,000 | $3,000 | $600 | $60.0 |
| $100,000/mo | $137 | $12,000 | $6,000 | $1,200 | $120 |
| $500,000/mo | $684 | $60,000 | $30,000 | $6,000 | $600 |
What should you do with this number?
Two things. First, size your uptime target honestly — theuptime calculator converts each level into minutes, and each extra nine costs roughly ten times more to achieve than the last. Second, notice that the number only counts known downtime: an outage nobody detects for three hours costs three hours, whichever monitoring plan you didn't have.
Detection is the cheap half of the equation.YoPingMe watches 10 monitors free, from three regions, and yells on email, webhook, or Slack the moment all three agree your site is down.