What Your Hosting Uptime SLA Actually Promises (and What It Doesn't)
A 99.9% uptime guarantee sounds close to perfect until you do the arithmetic: it allows roughly 43 minutes of downtime every month, or about 8.76 hours across a year, before a provider has even technically broken their promise. Reviews of actual SLA documentation from major hosts consistently find the same pattern, these contracts are written to protect the provider, not to compensate you for what an outage actually costs. Here’s what the number really means and how to read the fine print that surrounds it.
Key takeaways
- Every additional "nine" cuts allowed downtime by roughly 10x 99.9% allows ~43 minutes/month; 99.99% allows under 5 minutes/month, the jump between tiers matters far more than the percentages suggest at a glance.
- Compensation is a service credit, not reimbursement for lost business Standard SLA remedies are 3-10x the excess downtime applied as account credit, capped at 50-100% of your monthly fee, never your actual lost revenue.
- You usually have to file a claim yourself, with evidence, within a short window Most providers require a written claim within 5-30 days of the incident, or you forfeit the credit entirely, it is rarely automatic.
The Math Behind the Percentage
99.9% uptime, the industry-standard figure on most shared and mid-tier hosting plans, permits roughly 43 minutes of downtime in any given month, or about 8.76 hours spread across a year. 99.95% cuts that to around 21 minutes a month. 99.99%, the tier typically reserved for premium managed hosting, allows under five minutes a month. The jump from 99.9% to 99.99% isn't a small refinement, it's a roughly 10x reduction in tolerated downtime, which is exactly why premium managed WordPress hosts price that tier meaningfully higher than standard shared plans.
How the provider measures that percentage matters as much as the percentage itself. A host that measures uptime annually can absorb one very bad afternoon, a full nine-hour outage in a single incident, and still technically stay within their yearly 99.9% commitment, triggering little or no compensation. The same outage, on a host that measures uptime monthly, would blow straight through that month's 43-minute allowance and trigger a real credit. All else equal, a monthly-measured SLA holds a provider to a meaningfully tighter standard than an annual one, even at the identical headline percentage.
A provider’s own uptime dashboard has an obvious incentive problem. External monitoring tools checking every 1-5 minutes give you timestamped, independent records, which you’ll need anyway if you ever have to file an SLA claim.
What Compensation Actually Looks Like
When a provider does miss their SLA, the standard remedy is a service credit applied to a future invoice, not cash, and never compensation for the revenue or leads an outage actually cost you. Typical credit structures run somewhere between 5% of your monthly fee per hour of excess downtime and a formula giving 3-10x the excess downtime as credit, usually capped at 50-100% of that month's hosting fee. A few providers offer more generous terms, one mainstream host's terms promise a full month's credit for falling below 99.9% specifically, but even the more generous structures stop at your hosting bill, not your business impact.
The part most site owners miss entirely: compensation is rarely automatic. Most providers require you to actively submit a written claim, typically through a support ticket, within a specific window after the incident, commonly somewhere between 5 and 30 days. Miss that window and you forfeit the credit regardless of how clearly the provider missed their SLA. Filing a credible claim generally means showing exactly when the downtime started and ended and what was affected, which is precisely why independent, timestamped monitoring matters, your own evidence, not the provider's word about their own performance.
Read the Exclusions Before You Trust the Headline Number
What to actually check in an SLA before you trust the percentage
This single detail changes how tightly the provider is actually held to the promised percentage.
Most SLAs cover only network/infrastructure availability, not your application actually working correctly.
Planned maintenance windows are commonly excluded from the downtime count entirely.
Credits are rarely automatic and are commonly forfeited if not claimed within a short window.
Even a favorable per-hour credit formula is capped, usually at 50-100% of one month’s fee.
Who Should Weight This Most Heavily
- Understanding SLA math takes minutes and costs nothing to check before buying
- Independent monitoring is cheap or free and gives you real leverage in a dispute
- Monthly-measured SLAs with clear claim processes are a genuine, checkable differentiator between hosts
- Compensation never covers actual lost revenue, only hosting-fee credit
- Most SLA exclusions are broad enough to cover the majority of real-world outage causes
- Claim windows are short and rarely publicized prominently
Comparing hosting providers directly
See our full hosting guide for shared, VPS, cloud and WordPress-specific hosting comparisons.
Our Sources
Where this comes from
The downtime-minute figures and credit-structure patterns here are drawn from published 2026 comparisons of actual SLA documentation across major WordPress and general web hosting providers, cross-checked across multiple independent sources for consistency given how much SLA terms vary by provider.
-
SLA documentation comparisons reviewed
Published 2026 analyses of actual SLA contract terms across major hosting providers, not vendor marketing summaries.
-
Downtime-minute math independently verified
The 43-minutes/month and 8.76-hours/year figures for 99.9% uptime are a direct mathematical calculation, cross-checked across multiple sources.
-
No claims of our own outage testing
This article explains how to read SLA terms; it does not present our own live uptime monitoring data for specific providers.
Frequently Asked Questions
Frequently asked questions
How much downtime does 99.9% uptime actually allow?
Roughly 43 minutes per month, or about 8.76 hours across a year, the provider hasn’t technically broken their SLA until downtime exceeds that amount within the measurement period.
Will my hosting provider automatically credit me if they miss their uptime SLA?
Usually not. Most providers require you to actively submit a claim, typically through a support ticket, within a defined window (commonly 5-30 days), missing that window generally forfeits the credit.
Does an SLA credit cover the revenue I lost during an outage?
No. Standard SLA remedies are service credits applied to your hosting bill, not compensation for lost revenue, leads, or customer trust, that distinction is explicit in nearly every hosting SLA.
Is annual or monthly uptime measurement better for me?
Monthly measurement holds the provider to a tighter, more consistent standard, since it can’t be offset by good months elsewhere in the year the way annual measurement can absorb one very bad period.
What's excluded from most uptime SLAs?
Scheduled and emergency maintenance windows are commonly excluded entirely, and most SLAs cover only server/network response, not your actual application or website working correctly, read the specific exclusions before assuming full coverage.
Final take
- 99.9% uptime allows ~43 minutes of downtime a month before the SLA is even broken
- Compensation is a hosting-fee credit, never lost-revenue reimbursement
- Claims are rarely automatic, you must file within a short window with evidence
An uptime SLA is a contract clause, not a reliability guarantee, it tells you the compensation floor if a provider fails, not how often they actually will. The percentage matters less than how it’s measured, what’s excluded, how compensation is calculated, and how narrow the claim window is. None of that shows up in a marketing badge; it only shows up if you actually read the SLA document itself, which takes about the same ten minutes as comparing headline prices, and tells you considerably more about what you’re actually buying.
