SLA and uptime: what hosts promise
An SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.
An SLA (Service Level Agreement) is the part of the contract in which a host promises a certain level of availability and describes what happens if it fails to deliver. Uptime is the share of time the service was working. Below is how to turn percentages into minutes, what hosts actually promise, what exactly an SLA compensates and why you will not get compensation without your own monitoring.
What the percentages mean in minutes
The difference between 99.9% and 99.99% looks like rounding, but in minutes it is tenfold. For a 30-day month and a year, not counting planned maintenance:
| Availability | Allowed downtime per month | Per year |
|---|---|---|
| 99% | 7 h 12 min | 87 h 36 min |
| 99.5% | 3 h 36 min | 43 h 48 min |
| 99.9% | 43 min 12 s | 8 h 46 min |
| 99.95% | 21 min 36 s | 4 h 23 min |
| 99.99% | 4 min 19 s | 52 min 34 s |
| 99.999% | 26 s | 5 min 15 s |
A single three-hour outage in a 30-day month brings availability down to 99.58%. Rebooting a host to update its kernel takes several minutes, so 99.99% for a single physical server is an almost impossible promise: it becomes realistic when machines run on several hosts and are moved between them without stopping. Mind the length of the month too: in a 31-day month, 99.9% already means 44 minutes 38 seconds.
What hosts promise
According to the accsly.io catalog as of November 2026, 1,479 of 2,242 VPS hosts state their availability, and 1,409 of them give a specific percentage. Taking the highest figure each host names, the picture is as follows:
- 99.9%: 720 hosts, or 51%;
- above 99.9% but below 99.99% (usually 99.95% or 99.98%): 161, or 11%;
- from 99.99% to 99.999%: 327, or 23%;
- 100%: 86, or 6%;
- below 99.9%: 115, or 8%.
At 150 hosts the description contains two or more different figures: one on the home page and another on the plan page or in the terms, sometimes a different one for the network and for the servers. Only 62 hosts mention compensation in the terms recorded in the catalog. That does not mean the others have none, but it does mean you will not find it on the visible pages of their site: you need the document itself.
What an SLA actually pays
An SLA almost never covers your losses; it returns part of the fee for the service, and most often not as money but as a discount. This is easy to see in the documents of large cloud platforms that publish their SLAs in full.
- The SLA of one international cloud platform promises 99.9% for a single virtual machine and, if this is breached, gives a credit of 10% of the monthly bill for that machine when availability was between 95% and 99.9%, 25% between 90% and 95%, and 100% below 90%. The credit goes towards future payments and cannot exceed the monthly bill for the service.
- The SLA of the largest international platform promises only 99.5% for a single machine, and 99.99% for machines deployed across several availability zones. The credits are 10%, 30% and 100% on similar steps, and they are not paid out as money.
- A large Russian cloud's agreement states plainly that compensation is a discount that reduces the cost of services, not a cash payment, and that it cannot exceed the cost of the service for the billing period.
Let us work through an example. A VPS at $21 a month was down for three hours, so availability was 99.58%. Under the first scheme you are entitled to 10%, that is a $2.10 discount on next month. Under the second, with a 99.5% threshold, you get nothing: three hours fit within the promise. If an online shop lost orders during those three hours, the SLA will not cover them. So an SLA is a lever on the host and a signal of how confident it is in its infrastructure, not business insurance.
Exclusions and claim deadlines
The key part of an SLA is not the percentage but the list of what does not count as downtime. Typical items appear in almost every document:
- Planned maintenance. In the Russian cloud's agreement from the example above, maintenance announced three days in advance is not counted as an interruption, and downtime caused by preventive and emergency work of up to 8 hours per billing period is not compensated.
- Customer actions. A misconfigured firewall, a full disk or a crashed application is not the host's downtime.
- External causes. Force majeure, orders from government authorities and often DDoS attacks. What changes during an attack is covered in the article DDoS protection at hosts.
- Rule violations and unpaid bills. If the server was suspended for breaking the terms of use or the invoice is overdue, there will be no compensation.
- What exactly is measured. Some SLAs measure the availability of the data centre network, others that of the host, others that of your machine. Under the international cloud's document, downtime means losing external connectivity or access to the disk, and only periods of one minute or longer count.
Compensation is almost never applied automatically: you have to claim it. The deadline is limited: 30 calendar days from the incident in the Russian cloud's agreement, 60 days at one international platform, and the end of the second billing cycle at the other. The claim must include the date and time of each incident, and the international documents explicitly require logs that show the downtime. Miss the deadline and you lose the right to compensation.
Uptime without an SLA document
"99.99% uptime" on the home page and an SLA are different things. The figure in an advert promises nothing unless there is a section of the contract or a separate document behind it. Before buying, find that document and check:
- over what period availability is measured: a month, a quarter or a year;
- what counts as downtime and from what minimum duration;
- which work and events are excluded and how planned maintenance is announced;
- how much is compensated at each availability step and whether there is a cap;
- in what form: money, account credit or extra days;
- how and by when to file a claim and what evidence is needed.
If there is no such document, ask support in writing. An answer like "everything is stable here" without a reference to the terms means there is no availability commitment. That does not necessarily make it a bad host, but comparing it by percentage is pointless. A promise of 100% is also worth a question: what will the host give back when that percentage is inevitably missed?
How to check availability yourself
The host measures availability with its own data, and the customer's data often settles a dispute. You need an external check that does not run on the same server, and preferably not at the same host: an HTTP or ping probe once a minute, a log with the exact start and end time of every failure, and an alert to a messenger or email. How to set this up for free is described in the article Server monitoring: uptime, load, alerts, and plans for a monitoring server are collected in the selection VPS for monitoring.
If an outage happens, save the log and file the claim straight away rather than at the end of the month: state the start and end time, the server's address and what exactly was unavailable. A month with several short outages is also worth adding up, as the total may cross the SLA threshold.
If availability really matters
No SLA makes a single server more reliable: it only distributes responsibility. If an hour of downtime costs more than the monthly fee for the server, build failure into the architecture:
- keep a backup on another server and test restoring it, see the article VPS backups;
- for an important service, run a second server in another location or at another host and switch traffic via DNS or a load balancer;
- on a physical machine, put the disks in RAID and find out how quickly hardware is replaced; the differences from a VPS are covered in the article Dedicated server or VPS.
Two 99.9% servers at different hosts, with independent failures, together give more than one server promised at 99.99%, and they usually cost less than one server with real guarantees at that level.