SLA, Uptime & Downtime Calculator
Calculate maximum allowed downtime and error budget across daily, weekly, 30-day monthly, quarterly, and yearly windows for any availability target.
How Error Budgets Work in Practice
If your service targets 99.9% uptime, your allowed downtime budget is 0.1% of total time. That gives you 43.2 minutes in a 30-day month or roughly 8.76 hours over a 365-day year before the error budget is exhausted.
- Customer Checkout / Auth Paths: Often target 99.95%–99.99%, requiring multi-AZ redundancy, automated health checks, and fast canary rollbacks.
- Internal or Asynchronous Workers: Often run cleanly at 99.5%–99.9%, letting engineers deploy features and run maintenance without artificial alert fatigue.
Frequently Asked Questions
How much downtime does 99.9% allow in a 30-day month?
99.9% allows 0.1% downtime, which equals 43 minutes and 12 seconds in a 30-day month (about 8.76 hours in a 365-day year).
What is the difference between an SLA, SLO, and SLI?
An SLI is the live measured metric (such as successful HTTP requests or latency under threshold), an SLO is your team's target reliability threshold, and an SLA is a formal agreement with customers or stakeholders.
Should planned maintenance count against downtime?
In customer-facing availability tracking, any period when real users cannot complete requests typically counts against uptime unless explicitly excluded under defined maintenance windows in your SLA.