What an SLA at a data center actually means
An SLA (Service Level Agreement) is the data center's written commitment to infrastructure availability: power, cooling, and network. In a dedicated server contract the SLA is usually expressed as a percentage, for example 99.9% or 99.99%, and tied to a financial credit for downtime beyond the limit.
The availability percentage alone tells you little until you convert it into hours and minutes of downtime per year. Below we show how to do that and what to check first in a data center SLA.
Tier I-IV levels: what is the difference
The Uptime Institute classification splits data centers into four tiers based on redundancy of engineering systems: power, cooling, and connectivity inputs.
| Tier | Redundancy | Guaranteed availability | Downtime per year |
|---|---|---|---|
| Tier I | No redundancy | 99.671% | 28.8 hours |
| Tier II | N+1 | 99.741% | 22.0 hours |
| Tier III | N+1, maintainable without shutdown | 99.982% | 1.6 hours |
| Tier IV | 2N+1, fault tolerant | 99.995% | 0.4 hours |
Providers rarely state the Tier explicitly in marketing, but almost always publish the SLA percentage — it reveals the real level of power redundancy, which is covered in a separate article.
How much downtime that is in minutes
Converting a percentage into an absolute number is simple: (100% − SLA%) × minutes in a year.
| SLA | Downtime per year |
|---|---|
| 99% | 3.65 days |
| 99.9% | 8.76 hours |
| 99.95% | 4.38 hours |
| 99.99% | 52.56 minutes |
| 99.999% | 5.26 minutes |
The gap between 99.9% and 99.99% is the difference between a full workday of downtime and a single lunch break. For an online store or billing system that difference matters.
What a data center SLA does not cover
A data center SLA covers the building infrastructure and the link up to your rack. It does not cover:
- Operating system and application failures on the server itself.
- A failed drive or memory module inside your own hardware.
- Configuration mistakes made by the server administrator.
- Application-layer DDoS attacks — a separate protection layer handles those.
A high SLA percentage from the data center does not remove the need for monitoring the server itself and backing up its data.
How to check server availability yourself
Do not rely only on the provider's reports — keep an independent uptime record.
uptime
# 10:14:02 up 214 days, 3:41, 2 users, load average: 0.12, 0.09, 0.05
For external checks use a third-party availability monitor polling every 30-60 seconds with an alert to a messenger. This complements hardware monitoring over IPMI, which watches temperature, drives, and power inside the server itself.
Checklist before choosing a data center
- Get the stated Tier and SLA percentage in writing, not just verbally.
- Check that the SLA credit does not turn into symbolic bonus days.
- Ask about power redundancy and the data center location relative to regional risks.
- Run your own availability monitoring alongside the provider's reports.