99.999% uptime downtime & error budget
99.999% uptime allows about 26s of downtime per 30-day month, roughly 5m 15s a year. Here is the full ladder, the error budget in requests, and how fast you can burn it.
allowed_downtime
Allowed downtime at 99.999%, by window
| window | allowed downtime |
|---|---|
| per day | 864ms |
| per week | 6.0s |
| per 30 days | 26s |
| per 90 days | 1m 18s |
| per 365 days | 5m 15s |
burn_rate
How fast the monthly budget burns
At 1x you spend the whole 30-day budget exactly over 30 days. 14.4x is Google's fast-burn alert threshold, the rate that drains the month in about two days.
| burn rate | budget gone in |
|---|---|
| 1x | 30d |
| 2x | 15d |
| 5x | 6d |
| 10x | 3d |
| 14.4x (fast-burn page) | 2d 2h |
what_it_takes
What it takes to hold 99.999% (five nines)
Recovery has to be fully automated, because no human can react inside this budget. It means redundancy at every layer, tested regional failover, and an organization built around reliability. Very few products truly need it, and chasing it usually slows delivery more than the rare outage it prevents would, so confirm the business actually requires it before committing.
Lighter need? 99.99% uptime is cheaper to hold.
every_tier
The full uptime ladder
New to the terms? What availability and the nines mean, plus error budgets and burn rate.
faq
Questions & answers
- How much downtime does 99.999% uptime allow?
- 99.999% uptime allows about 26s of downtime per 30-day month, which works out to roughly 5m 15s a year. Go past that in a window and you have missed the target for that window.
- What is the error budget for 99.999% uptime?
- Over 5M requests in a month, 99.999% permits about 50 failed requests before the budget is spent. The budget is 0.001% of whatever volume you serve, so it scales with traffic.
- Is 99.999% uptime good enough?
- It depends on what your users need and what the next tier costs to hold. Recovery has to be fully automated, because no human can react inside this budget. The breakdown below shows what it takes to hold 99.999% and whether the next nine is worth it.
Picking a target is easy. Holding it in production is the work.
I review where a system actually spends its error budget and what the next nine really costs. Book a call, or leave your email and I'll reach out.
Prefer proof first? See how this plays out in real case studies →