Your inputs
Your error budget
Healthy — ship with confidencePer day
1.4m
Per week
10m
Per month
44m
Per quarter
2.2h
Per year
8.8h
Remaining budget
24m
Cost of downtime so far
—
The SRE rule of thumb
An error budget isn't a downtime goal — it's permission to move fast. While budget remains, ship boldly. When it runs dry, freeze features and spend engineering on reliability. Teams that track this number deploy more often AND stay up longer.
How it works
How the Error Budget Calculator works
The Error Budget Calculator is a free SLO calculator for SREs and cloud engineers. Pick an availability target and it shows the downtime you are allowed per day, week, month, quarter and year, how much of this month's budget is gone and what that downtime cost.
- 01
Set your SLO
Choose a preset from 99% to 99.99% or type a custom availability target.
- 02
Enter downtime so far
Add the minutes of downtime you have had this month and, if you like, your revenue per hour.
- 03
Read your budget
The numbers update as you type: allowed downtime per period, budget consumed, time remaining and the cost of the downtime.
What you get
What the calculator gives you
Allowed downtime
Your error budget per day, week, month, quarter and year.
Budget consumed
The share of this month's budget already spent, with a warning from 60% and an exhausted state at 100%.
Time remaining
How much downtime you can still absorb this month.
Cost of downtime
Downtime so far multiplied by your revenue per hour.
FAQ
Error Budget Calculator: common questions
What is an error budget?
An error budget is the amount of unreliability your service level objective (SLO) allows. A 99.9% availability target leaves a 0.1% budget: the downtime you can spend on releases, experiments and incidents before you miss the target.
How much downtime does 99.9% uptime allow?
About 43.8 minutes per month, 10.1 minutes per week and 8.77 hours per year.
How much downtime does 99.99% uptime allow?
About 4.4 minutes per month and 52.6 minutes per year.
How is an error budget calculated?
Error budget = total minutes in the period × (1 − SLO). The calculator uses an average month of 30.44 days, which is 43,830 minutes.
What should a team do when the error budget runs out?
The usual policy in site reliability engineering is to pause risky releases and spend engineering time on reliability until the service is back inside its target.
Is my data sent anywhere?
No. All of the math runs in your browser.
DevOps & Cloud at JSXDOM
Budgets get exhausted. Great pipelines don't.
CI/CD, observability, SLO design and incident-proof infrastructure — an elite reliability practice without the elite hires.
Talk reliability with us