How do I track remaining downtime budget?

Subtract all incident and maintenance durations from the total allowed downtime for the period. Many monitoring tools provide SLA burn-down dashboards that track this automatically.

Should I use calendar months or rolling windows?

Rolling windows provide a more consistent measurement. Calendar months can create perverse incentives — for example, depleting the budget early in the month and deferring fixes. Choose the method that aligns with your SLA contracts.

What happens if I exceed my downtime budget?

Exceeding the downtime budget means an SLA breach. Depending on your contract, this may trigger service credits, penalty payments, or contract renegotiation. The financial impact varies by agreement.

How do partial outages affect downtime calculations?

Partial outages can be prorated. If 50% of users are affected for 10 minutes, some SLAs count this as 5 minutes of downtime. Define how partial degradation is measured in your SLA terms.

Does network latency count as downtime?

Depending on your SLA definition, severe latency that renders the service effectively unusable may count as downtime. Define specific latency thresholds in your SLA (e.g., response time exceeding 5 seconds equals downtime).

How do I handle time zone differences in SLA measurement?

Use UTC as your standard measurement time zone. Document this clearly in your SLA to avoid disputes about when downtime occurred and which measurement period it falls into.

Downtime Duration Calculator

Calculate exact downtime duration from uptime percentage and time period. Convert availability to hours, minutes, and seconds of downtime.

Quick Period

Common SLOs

Total Period (hours)

Uptime Percentage

SLO Period

Allowed Downtime (hours)

0.7200

720h period

Allowed Downtime (minutes)

43.20

📊 SLO Comparison Table

SLO Target	Downtime (minutes)	Downtime (seconds)	Status
99.9% (three 9s)	43.20	2,592	✓ Meets SLO
99.99% (four 9s)	4.32	259	✗ Below SLO
99.999% (five 9s)	0.43	26	✗ Below SLO
99.9999% (six 9s)	0.04	2	✗ Below SLO

⏱️ Multi-Period Downtime Breakdown

Period	Hours	Downtime (min)	Downtime (sec)	Tolerance
Daily	24	1.44	86	🟢 Very strict
Weekly	168	10.08	605	🟢 Very strict
Monthly	720	43.20	2,592	🟢 Very strict
Quarterly	2,190	131.40	7,884	🟡 Moderate
Annually	8,760	525.60	31,536	🟡 Moderate

Uptime Visualization

99.90% UP

0.10% DOWN

Green = Available TimeRed = Error Budget / Downtime

💡 Tip: At 99.90% uptime, you have 43.2 minutes of allowed downtime per month. Plan maintenance windows within this budget.

Planning notes, formulas, and examples

About the Downtime Duration Calculator

Knowing your exact downtime allowance is critical for planning maintenance windows, incident response targets, and SLA compliance. This calculator converts an uptime percentage and a specified time period into the precise amount of allowed downtime in days, hours, minutes, and seconds.

Unlike a simple nines calculator, this calculator lets you specify any custom time period — a month, a quarter, a sprint cycle, or a fiscal year. This flexibility makes it useful for SLA compliance tracking, maintenance planning, and incident retrospectives where you need to know exactly how much of your downtime budget remains.

When This Page Helps

Translating uptime percentages into real-world time values helps teams plan maintenance windows without breaching SLA commitments. It gives granular breakdowns that are directly usable in operational planning and incident response playbooks.

How to Use the Inputs

Enter the total time period in hours (e.g., 720 for a 30-day month).
Enter the uptime percentage your SLA requires.
View the calculated downtime in hours, minutes, and seconds.
Use the result to plan maintenance windows within your allowed budget.
Compare multiple scenarios by adjusting the uptime target.

Formula used

Downtime = Total Period − (Total Period × Uptime% / 100). For 720 hours at 99.9%: Downtime = 720 − (720 × 0.999) = 0.72 hours = 43.2 minutes.

Example Calculation

Result: 43.2 minutes of allowed downtime

In a 30-day month (720 hours), a 99.9% uptime SLA allows 0.72 hours or 43.2 minutes of downtime. This means you have just over 43 minutes total for all incidents and planned maintenance combined.

Tips & Best Practices

A 30-day month has 720 hours; a 31-day month has 744 hours — adjust accordingly.
Track downtime budget consumption in real time to avoid SLA breaches.
Reserve a portion of your downtime budget for unplanned incidents.
Consider using rolling windows rather than calendar months for SLA measurement.
Document whether planned maintenance is excluded from your SLA measurement.
Alert when 50% and 75% of monthly downtime budget is consumed.

Calculating Downtime for Different Periods

Downtime budgets vary significantly based on the measurement period. A quarterly SLA gives more flexibility than a monthly one, allowing you to absorb occasional longer outages without breaching your commitment.

Maintenance Window Planning

Scheduled maintenance should be carefully planned within your downtime budget. If your monthly budget is 43 minutes, scheduling a 30-minute maintenance window leaves only 13 minutes for unplanned incidents. Many teams reserve at least 50% of their budget for emergencies.

Incident Budget Tracking

Modern SRE teams track downtime consumption in real time using dashboards that show remaining budget. When the budget drops below a threshold, teams may implement change freezes or increase review rigor for deployments.

SLA Measurement Best Practices

Define exactly what constitutes downtime, how partial outages are measured, whether planned maintenance is included, and what the measurement window is. Ambiguity in these definitions leads to disputes and misaligned expectations.

Sources & Methodology

Last updated: February 8, 2026

Frequently Asked Questions

Subtract all incident and maintenance durations from the total allowed downtime for the period. Many monitoring tools provide SLA burn-down dashboards that track this automatically.