What Web Hosting Uptime Actually Means

Web hosting uptime is the percentage of time your site is reachable, and a host's uptime guarantee is a promise to refund you a small credit if it drops below that figure — not a promise your site never goes down. A 99.9% guarantee, the industry standard, still permits roughly 43 minutes of downtime every month. Understanding what these numbers do and don't promise is the difference between buying on marketing and buying on substance.

What the percentages translate to

The extra nines matter more than they look. 99% uptime sounds high but allows about 7.2 hours of downtime a month — a bad figure. 99.9% ("three nines"), the common shared-hosting guarantee, allows roughly 43 minutes a month, or about 8.7 hours a year. 99.99% ("four nines") allows about 4.3 minutes a month, and 99.999% ("five nines") about 26 seconds — a level realistically reserved for enterprise infrastructure. So when one host advertises 99.9% and another 99.99%, the second is promising roughly ten times less downtime, not a rounding-error difference. That said, these are ceilings the host allows itself before owing you anything, not predictions of how your site will actually perform. A host can sit well inside its guarantee and still have a bad month that costs you sales during the worst possible hour.

The guarantee only pays if you claim it

Here's the part the sales page skips: most uptime guarantees are service-level agreements (SLAs) that refund a pro-rated credit only if you notice the downtime, measure it, and file a claim within a window. The compensation is a slice of your hosting fee — often a day or a month of credit — not compensation for the business you lost while the site was down. As of September 2026, SiteGround publishes a 99.99% SLA and DreamHost a 100% SLA, both backed by credit policies you can claim; InMotion and HostGator publish credit-backed guarantees too. Others, including Bluehost, market a 99.9% figure with no uptime-credit SLA in their terms at all — there, the number is a target, not a promise. The lesson: read whether the guarantee actually pays out, and don't assume a bigger number means a stronger commitment.

Why we don't publish our own uptime tests

You'll see review sites claim "we tested this host at 99.98% over 12 months." Treat those with caution. A credible uptime test needs continuous third-party monitoring of a real site on that host for a long, disclosed period, and most sites quoting a precise figure don't run one — they repeat the host's own number or a single monitor's snapshot. We don't publish uptime figures we didn't measure, because a static page claiming measured uptime it can't back up is exactly the kind of unverifiable claim you should distrust. Instead we cite each host's published SLA and say plainly whether it's credit-backed. If you want to verify a host yourself, sign up, point a free uptime monitor at your site, and watch for a month. For more on spotting inflated claims, see how to read hosting reviews critically.

What to actually optimise for

Since the guarantee decimal is a weak signal, optimise for the things that actually reduce downtime and its cost: a host with a strong independent reputation for reliability, genuinely responsive 24/7 support that resolves incidents fast, and your own recent backups so you can recover quickly if something breaks. A credit-backed SLA is a nice tiebreaker, but responsive support during an outage is worth more than a refund of a few dollars afterward. Our best web hosting ranking lists each host's published uptime figure and notes whether it's credit-backed, but weights support reputation more heavily — because that's what determines how a bad hour actually plays out.

Downtime you cause vs downtime the host causes

A large share of what feels like "downtime" isn't the host's fault at all — it's the site. A plugin conflict, a broken theme update, a PHP error or a traffic spike that blows past your plan's resource limits will take a site offline while the server itself is perfectly healthy, and none of it counts against the host's uptime guarantee. That's why your real-world availability can be worse than the SLA figure suggests, and why jumping to a bigger plan doesn't automatically fix outages that your own code or a rogue plugin is causing.

It's also worth reading the SLA's exclusions, because they're broad. Scheduled maintenance, DDoS attacks, problems with your own code or third-party services, and downtime you fail to report within the claim window are typically carved out — so the guarantee covers a narrower slice of reality than the headline percentage implies. The practical response: keep your site and plugins updated and tested, size your plan for your actual traffic, put a CDN and caching in front to absorb spikes, and keep current backups so a self-inflicted outage is a quick restore rather than a crisis. Then judge the host itself on how fast its support responds to the outages that genuinely are theirs.

Reliability is a system, not a percentage

What actually keeps a site online isn't the SLA number — it's the infrastructure and practices behind it. Quality data centres with redundant power and network, a content delivery network that keeps serving cached pages during a hiccup, and a host with a real incident-response process will deliver better real-world availability than a competitor advertising a bigger percentage and hiding its outages. A telling sign of a reliable host is transparency: a public status page and honest post-incident notes mean the host owns its problems and fixes them, while a host that goes quiet during outages and blames customers is one to avoid. Your own setup carries just as much weight. Caching, a CDN and current backups turn a server hiccup into a blip rather than a crisis, and they're within your control regardless of which host you pick. So read reliability as a whole system — the host's infrastructure, its response when things break, and your own resilience layered on top — and weight a host's reputation for handling incidents far above the single decimal it prints on the pricing page. The number is a ceiling the host allows itself; the system is what determines whether your visitors actually see your site.