Uptime guarantees & what they don't cover

It's the number every host puts on the page: 99.9% uptime, guaranteed. It sounds like a promise that your site will essentially always be there. It isn't quite. An uptime guarantee is a contract with a specific, narrow meaning — and the gap between how reassuring it sounds and how little it actually covers is where the word does its quiet work.

Start with the number itself, because "99.9%" hides its own scale. A percentage that close to 100 feels like rounding error. Translated into time, it's a different story.

That's the headline being honest. The real shrinkage happens underneath, in the part nobody reads: the exclusions. A guarantee only covers what the contract says it covers, and most contracts exclude more than they include.

What the guarantee quietly doesn't count

"Uptime" sounds total, but the SLA defines it narrowly, and these are the common carve-outs that mean real outages you experience often don't count against the promise:

Read those together and a "99.9% guarantee" can describe far less availability than it implies. A guarantee that excludes maintenance, outside dependencies, and slow-but-not-dead performance might, in lived experience, be a fraction of its headline number.

An uptime guarantee measures the host's definition of "up," not your visitor's experience of a working site. Those are not the same thing.

And when they do miss it — the credit

Say the host genuinely breaches the guarantee. What you're owed is usually a service credit — a small slice of your hosting fee, not compensation for what the downtime actually cost you. If you pay a modest monthly fee and an outage costs you a day of sales, the credit might be a few dollars off next month's bill. The guarantee caps the host's risk, not yours.

And the credit rarely arrives on its own. Most agreements require you to notice the outage, document it, and file a claim — often within a tight window like 30 days — with evidence. Miss the window or the paperwork and a real breach pays you nothing. As one plain summary put it: the guarantee only binds the people who actually read it.

What actually protects you

The honest version of reliability isn't a bigger number on the sales page. It's the things that hold up when something breaks:

• Independent monitoring. Your own check on whether the site is up — so you know before your customers do, and you have your own record, not just the host's.
• The track record, not the promise. Ask for actual measured uptime over the last year or two. Past performance tells you more than a contractual minimum.
• Plain answers on the exclusions. How much scheduled maintenance, announced how, and what happens to your site during it.
• A real human when it's down. The fastest path back up isn't a credit form — it's someone who answers and can fix the server.

The questions that test the guarantee

You don't need to decode the SLA's legalese. You need to ask past the headline number:

1. What exactly is excluded — and how much scheduled maintenance does that allow per month?
2. What's your actual measured uptime over the past 12–24 months, not the guaranteed minimum?
3. What do I get if you miss it, and do I have to file a claim to receive it?
4. Does the guarantee cover slow or broken, or only fully offline?
5. When my site goes down, who responds — and how would I know before my visitors do?

If the answers are specific and the track record is real, the guarantee means something. If everything routes back to "99.9%, subject to the SLA," now you know the number was the marketing and the exclusions were the contract. That's not a disaster — it's just the real shape of the promise, finally visible.