Hosting · Explainer
What a Hosting SLA Covers (And What It Doesn't)
Short answer
A hosting SLA is a written promise in your hosting contract that sets an uptime target, such as 99.9%, and states what you get if the host misses it. The payment is usually a small account credit, not cash, and you often must claim it within 30 days. Scheduled maintenance, your own code and traffic above your plan limits are normally excluded.
Key takeaways
- An SLA is a contract term, not a marketing line: the uptime figure and the credit sit in the legal terms.
- 99.9% uptime allows about 43 minutes of downtime per month before credits apply.
- Credits are account credit toward future bills, not cash refunds, and are capped at one month.
- Most SLAs require you to claim within 30 days; missing the window forfeits the credit.
- Scheduled maintenance, your own code and traffic beyond your plan are excluded.
What is a hosting SLA?
A hosting SLA is a written promise in your hosting contract that sets an uptime target and a remedy if the host misses it.
SLA stands for service level agreement. It is part of the terms of service, not a line on a sales page. Kinsta's SLA, updated 25 September 2025, is an addendum to its terms of service and defines downtime, the uptime guarantee and the credits that apply.
The SLA matters because it is the only uptime promise you can hold the host to. A sales page can claim any figure, but only the SLA states how uptime is measured, what counts as downtime and what you receive. Read it before you pay, not after an outage.
What does the uptime percentage actually mean?
The uptime percentage is the share of a billing month your site must stay reachable, and each extra 9 cuts the allowed downtime sharply.
A 99.9% guarantee allows about 43 minutes of downtime in a 30-day month. ServerPoint's SLA shows the maths: a 30-day month has 43,200 minutes, so 0.1% of it is about 43 minutes. Kinsta uses the same figure, since its credits only start once downtime passes 43 minutes.
The table below shows what each common guarantee allows per month. The figures come from host SLA pages checked in November 2026.
| Uptime guarantee | Allowed downtime per month | Allowed downtime per year |
|---|---|---|
| 99.9% | About 43 minutes | About 8 hours 45 minutes |
| 99.95% | About 21 minutes | About 4 hours 22 minutes |
| 99.99% | About 4 minutes | About 52 minutes |
Note that uptime is measured by the host's own monitoring in most SLAs. Kinsta states downtime is calculated from its monitoring, and Hostinger judges downtime by its own records too. Your own uptime monitor may disagree, and the host's figure is the one that counts for a claim.
What do SLA credits pay?
SLA credits are small account credits toward future bills, not cash refunds, and they are capped at one month of fees.
Kinsta pays 5% of the monthly subscription value for 43 to 59 minutes of downtime, 10% for 60 to 119 minutes, 15% for 120 to 179 minutes and 20% for 180 to 239 minutes.
The credit is scaled by the share of your sites that were affected, and the maximum credit is one full month of fees.
WP Engine pays 5% of the monthly fee for each full hour of downtime beyond its 99.95% target. Its enhanced 99.99% tier pays 3% for each half hour beyond target. Hostinger pays a flat 5% of the monthly fee when its 99.9% guarantee is missed.
On a $50 monthly plan, a 2-hour outage under Kinsta's table earns 15% of $50, which is $7.50 in credit. The money stays on your account and cannot be cashed out. Kinsta states its credits have no cash value, are nonrefundable and expire when the plan ends.
How do you claim an SLA credit?
You must ask for it in writing, usually within 30 days, or you lose the credit.
Kinsta requires a written request within 30 days of the downtime, sent through the chat system in its platform. Missing that window forfeits the right to a credit, even if the outage is clear. WP Engine and Hostinger use the same 30-day window.
ServerPoint is stricter and asks for a support ticket within 3 days of the event. Its credits are 10% of the monthly fee when uptime falls to 99.0 to 99.9%, 20% at 95.0 to 98.99% and 30% below 95%.
Keep your own outage log with times and screenshots, so you can file the claim while the window is open.
What does an SLA not cover?
An SLA covers the host's network and servers, not your site, your code or planned work.
Kinsta excludes its daily maintenance period, 2 am to 5 am local data center time, plus emergency maintenance and scheduled outages. It also excludes force majeure events such as fire, flood, war and government action. Traffic that exceeds what your plan can handle is excluded too.
Your own mistakes are excluded as well. Kinsta lists customer breaches, customer-authored code or configuration, and changes made by anyone other than Kinsta. A broken plugin update, a bad theme change or a database you filled up will not earn a credit, even if the site was down for hours.
Hostinger excludes scheduled maintenance, DDoS attacks and downtime caused by the user. The pattern is the same across hosts: the SLA pays when the host's own systems fail, and nothing else.
If your site is slow rather than down, that is not downtime either. Our guide to what a good uptime percentage looks like explains how to judge the figure itself.
How do SLAs differ between hosts?
The guarantee, the credit and the claim window all differ, so two hosts with the same percentage can pay very different amounts.
The table below compares four published SLAs, all checked in November 2026. The guarantee is only the first column; the credit and the deadline decide what you actually receive.
| Host | Uptime guarantee | Credit for missing it | Claim window |
|---|---|---|---|
| Kinsta | 99.9%, or 99.99% on higher tiers | 5% to 20% of monthly value by downtime length | 30 days, via chat |
| WP Engine | 99.95%, or 99.99% enhanced | 5% per full hour beyond target | 30 days, via support |
| Hostinger | 99.9% per calendar month | 5% of the monthly fee | 30 days |
| ServerPoint | 99.9% network and shared platform | 10% to 30% of monthly fee by uptime band | 3 days, via ticket |
Some hosts publish no SLA at all on their cheapest plans, and some promise 100% uptime only on cloud or managed tiers. The absence of an SLA does not mean the host is unreliable, but it does mean you have no written remedy.
Compare the SLA next to the price when you choose WordPress hosting, since a cheap plan with no SLA can cost more after one bad month.
Does an SLA prove a host is reliable?
No, an SLA proves the host will pay a small credit when it fails, not that it fails rarely.
The credit is capped at one month of fees on every SLA above, and most outages earn 5% to 15%. A host can miss its target every month, pay the credit and still keep your money. The SLA is a safety net, not a quality badge.
Real reliability shows in independent uptime records, status pages and how fast support answers during an outage. A host with a 99.9% SLA and a public status page tells you more than a host with a 100% claim and no records.
What should you check before you sign up?
Check the guarantee, the credit table, the claim window and the exclusions, all in the SLA document itself.
Start with the guarantee and the billing period it applies to. Kinsta measures per monthly billing period, while some hosts measure per calendar month or per year. An annual figure can hide a terrible month, since one bad month can be offset by eleven good ones.
Then check whether the credit is automatic or must be claimed, and how many days you have. A 3-day window is easy to miss during a launch week, while a 30-day window gives you time. Read the exclusions last, since they decide whether your most likely outage even counts.
What mistakes should you avoid?
Do not treat the SLA percentage as a promise your site will stay up, and do not skip the claim deadline.
The biggest mistake is reading 99.9% as a promise about your site. The SLA covers the host's network and platform, and your site can still go down from a plugin conflict, a full disk or a traffic spike.
A 503 error from an overloaded plan is not an SLA event on most hosts.
The second mistake is forgetting to claim. Credits are rarely automatic, and the window closes fast.
Set a reminder to check uptime at the end of each billing month, and file the claim the same day you spot a miss.
Frequently asked questions
Is 99.9% uptime good enough for a WordPress site?
Yes, for most small sites. It allows about 43 minutes of downtime a month, which is enough for routine maintenance and rare faults. What matters more is the credit behind it and whether the host publishes real uptime records. A 99.9% figure with a 5% credit is a weak promise.
Do I get money back if my host goes down?
Almost never. SLA credits are account credit toward future hosting bills, not cash. Kinsta, WP Engine and Hostinger all state this in their terms. The credit is also capped, usually at one month of fees, so even a long outage pays back at most one month.
Does the SLA cover my site being slow?
No. Downtime means the site is unreachable, not slow. A site that loads in 10 seconds is up by the SLA definition, even if visitors leave. Slow performance is a hosting quality issue, not an SLA event, and it is fixed by caching or a better plan.
What if my host has no SLA?
Then you have no written remedy for downtime. Some hosts only offer an SLA on cloud or managed plans, not on shared hosting. You can still switch hosts, keep your own uptime monitor, and ask the host in writing what compensation it offers before you sign up.
Can I claim an SLA credit months after the outage?
Usually no. Most SLAs give you 30 days from the downtime to file a written claim, and some give only 3 days. After the window closes, the right to a credit is forfeited. Keep an outage log with dates and times so you can claim quickly.
Sources
- Service Level Agreement Kinsta
- Pantheon vs. WP Engine: A Complete Comparison Guide WP Engine
- Next-Generation Web Hosting Technology Hostinger
- Service Level Agreement ServerPoint
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
