Definition
Uptime is the percentage of time a system is working and available to users, and an SLA, Service Level Agreement, is the contract in which a vendor commits to a minimum level of uptime and other measures, such as response times for support, along with what the customer gets back if the promise is broken. Uptime is usually expressed in "nines": 99.9% means roughly 8.8 hours of downtime per year, 99.99% means under an hour.
In a company, uptime and SLA appear in two directions. As a buyer, you read the SLA of every critical vendor to know what happens when their service fails and how much credit you are owed. As a SaaS provider, you publish an SLA to enterprise customers and back it with monitoring, on-call engineers, redundant infrastructure and a public status page. Each extra nine costs disproportionately more, so the target should match what customers actually need.
A common misconception is that an SLA guarantees uptime. It does not; it prices downtime. The typical remedy is a service credit worth a small fraction of the monthly fee, which rarely covers the customer's real loss. Another is that 100% uptime is a sensible goal. It is not achievable and chasing it wastes money. The useful question is which parts of the product must never fail and which can tolerate a short outage.
In practice
A B2B platform promised 99.9% uptime to enterprise customers and built for it: redundant servers in two regions, automated failover and an on-call rota. When a cloud region failed for two hours, customers barely noticed, and the SLA became a sales argument against a cheaper competitor.
Why it matters
Uptime is a promise you make to customers and an SLA is the fine print on that promise. Know your real number, know what you have committed to in contracts, and make sure the gap between the two is not a surprise you discover during an outage.
Frequently asked questions
- What does 99.9% uptime mean in practice?
- About 8 hours and 45 minutes of downtime per year, or roughly 43 minutes per month. 99.99% allows about 52 minutes per year, and 99.999% about 5 minutes. Each additional nine requires significantly more redundancy and engineering, so the cost rises steeply.
- What should a SaaS SLA include?
- A defined uptime commitment and how it is measured, exclusions such as scheduled maintenance, support response times by severity, the remedy when the commitment is missed (usually service credits), and how to claim it. Good SLAs are specific and backed by a public status page and incident reports.