What an uptime promise actually means, and how to read it

The difference between a good availability promise and a mediocre one is a handful of hours a year; the difference between a promise and a practice may be everything.

Every hosting page carries the same calm number, and buyers read it as certainty. A percentage promise is not a measurement of your site; it is an expectation about a window of time, phrased so precisely that it sounds like one. Reading it well starts with accepting what it is: a forecast about the provider's machinery, not a report about your experience.

The honest framing is almost anticlimactic. A strong promise and a mediocre one are separated by a handful of hours a year, once you do the arithmetic on the decimals. What separates a business that stays online from one that bleeds visitors is rarely that difference. It is the distance between the promise as a sales line and availability as a practiced discipline.

Then read the exclusions, because that is where the promise lives. Scheduled maintenance usually sits outside the counted window. Your own application errors are yours, not the provider's. And the parts of the chain the provider does not run, your domain, your DNS, your code, the third-party services your site calls, were never covered at all. A site can be genuinely down while the promise is genuinely intact.

Which leads to the part almost nobody does: watch your own address. The provider monitors its infrastructure; nobody monitors your experience except you. A small external check against your own URL, running from outside your own office, tells you what customers actually feel, and it settles arguments that a contract was never designed to settle.

The credit question follows from the same logic. Promises carry remedies, but remedies do not collect themselves: someone has to notice, log, and ask. A promise you never measured is a promise you never collected on, and the quiet habit of keeping your own record of downtime is what turns a marketing line into something with edges.

We run infrastructure ourselves and hold our own addresses to this standard, which is why we would rather teach the reading than repeat the number. Ask a provider what the promise excludes, and keep your own log. The number on the page is the beginning of the conversation, not the end of it.