Your host promises 99.9% uptime. Here's what that actually allows

Almost every hosting plan advertises a number with a lot of nines in it. Ninety-nine point nine percent sounds like a promise that your website will simply always be there.
Do the math, and it's a little less comforting. A 30-day month has 43,200 minutes. One-tenth of 1% of that is about 43 minutes. So a host can meet a 99.9% uptime promise while your site is unreachable for three-quarters of an hour every month, or close to nine hours over a year.
The gaps grow quickly as the nines disappear. At 99.5%, the allowance is about 3 hours and 36 minutes a month. At 99%, it's more than seven hours a month, or roughly three and a half days a year. Going the other way, 99.99% allows a little over four minutes a month.
None of these numbers is good or bad on its own. What matters is what they mean for your business, and whether the number you're paying for is the number you're getting.
When the downtime happens matters more than how much
Forty minutes at 3 a.m. on a Tuesday may cost a local bakery nothing at all. The same 40 minutes at noon on the Friday after Thanksgiving could cost an online shop a big share of its best sales day.
An uptime percentage tells you nothing about timing. Before you pay extra for a plan with more nines, it's worth asking a plainer question: what does an hour offline cost us, and at what time of day? A booking site for a dentist and a store running a holiday promotion will answer that very differently.
Read what the guarantee actually covers
A hosting uptime guarantee is usually a promise of compensation, not a promise that nothing will go wrong. Before relying on one, read the service agreement and look for a few things.
What counts as downtime? Some agreements exclude scheduled maintenance, problems caused by your own code or plugins, and outages shorter than a set number of minutes. How is it measured, and by whom? If the only record is the host's own, you'll have a hard time arguing with it. And what do you get if the promise is broken? Often it's a credit toward next month's bill, and you may have to request it yourself within a fixed window.
"The server is up" isn't the same as "the site works"
There's a second gap that the percentage hides. The host is measuring its server. Your customers experience the whole chain: the domain name has to resolve, the security certificate has to be valid, and the page has to actually load.
A site can be "up" by the host's definition while visitors see a database error, a blank page after a broken plugin update or a full-screen browser warning because the certificate expired. To the customer, all of these look the same as an outage. To the host's statistics, none of them may count.
Measure it yourself
The fix is to keep your own record, from the outside, the way your customers see the site. An external uptime monitor loads your website every few minutes from a server that has nothing to do with your host, and alerts you when it stops answering properly. A good one confirms a failure before alerting you, so a single dropped connection doesn't send you a false alarm.
This gives you two things. You find out about problems before your customers mention them. And you build up a history of every incident, with when it started and when it ended, which is exactly what you'll want in hand if you ever need to ask your host for that credit.
There are free and paid options. A service like uptimewire.com, for instance, also checks the certificate, the domain and DNS for each site it watches, and its free plan covers one website. After a few months, you'll know your real uptime number, not the one on the hosting plan's pricing page.


