Actual Uptime: {{ uptime_percent.toFixed(5) }} %
SLA Target: {{ sla_target }} %
✅ Within SLA
❌ SLA Breached
Period | Allowed Downtime |
---|---|
{{ p.label }} | {{ p.readable }} |
Uptime measures the proportion of time a service remains available to users. Service-level agreements (SLAs) convert that measure into contractual targets, often expressed as 99.9 % or higher. Error budgets represent the permissible downtime within those targets. Clearly understanding how these three metrics connect is essential to quantify reliability obligations.
The Uptime Calculator lets you enter a target availability percentage, operating period, and observed downtime. It instantly calculates allowed downtime, effective uptime, and remaining error budget, then signals whether the service stayed within its SLA target. Advanced options exclude planned maintenance and convert time units, giving SRE teams a sharper focus on incident-driven outages.
Use the results to prioritise remediation, negotiate realistic SLAs, or defend reliability reports during audits. For instance, spotting a 5 % error-budget burn early prompts preventive fixes before contractual penalties or user churn arise. By translating raw downtime into concrete financial and reputational stakes, the calculator aligns engineering efforts with stakeholder expectations and promotes data-driven service management.
This section explains how each metric is derived from your inputs.
Metric | Formula | Example (99.9 %, 30 days) |
---|---|---|
Allowed Downtime (min) | Period min × (100 − Target) / 100 | 43.2 |
Effective Downtime (min) | Observed − Maintenance | 10 − 3 = 7 |
Actual Uptime (%) | (1 − Effective / Period) × 100 | 99.983 |
Error-Budget Burn (%) | Effective / Allowed × 100 | 16.2 |
The calculator applies four linked formulas to determine compliance.
Step | Equation |
---|---|
1. Period Minutes | period_value × unit_factor |
2. Allowed Downtime | Period × (100 − Target) / 100 |
3. Effective Downtime | Observed − Maintenance |
4. Actual Uptime | (1 − Effective / Period) × 100 |
Given a 99.9 % target across 30 days (43 200 min) with 7 min unplanned downtime, allowed downtime equals 43.2 min. Actual uptime is 99.983 %, well within the SLA.
A burn percentage below 100 % indicates remaining error budget. Exceeding 100 % signals a breach requiring incident review.
Track burn trend daily. If usage exceeds 50 % mid-cycle, schedule preventive maintenance and investigate recurring root causes.
Follow these steps to compute uptime metrics.
The answers below address common questions about uptime calculations.
Normalising all time values to minutes keeps rounding transparent and simplifies percentage calculations.
Results display up to two decimal places, which balances readability with precision for most production scenarios.
Open separate browser tabs for each service. Inputs persist per tab, allowing parallel assessments.
Calculations rely solely on duration, not clock time. Therefore, time-zone differences do not affect results.
The bar shows green when error-budget burn is under 100 % and switches to red once the limit is exceeded.