Blog · Operations
99.9% uptime: what that number allows, and what actually breaks
By the HostingFast team Published 27 July 2026 7 min read

Three nines sits on the homepage of every host going. Hardly any of them spell out what the figure covers, what it excludes, or the ways a hosting platform actually falls over. We run one. The murk around that number serves marketing better than it serves customers, so here is the operations view, in plain language.
Do the arithmetic first. 99.9% uptime buys you 43 minutes and 50 seconds of downtime in a month. 99.99% buys 4 minutes and 23 seconds. As for 100%, it has never existed anywhere. Any host claiming it is telling you about an ambition, a blind spot in its monitoring, or a refund policy. Not about its platform.
What actually knocks websites offline
Ranked, near enough, by how often we see them on shared platforms. Application faults come first: a plugin update white-screens WordPress, the site goes dark, and the server beneath it hums away untroubled. Resource exhaustion follows, where your own traffic surge or a neighbouring account runs headlong into PHP process limits. After that, planned work such as kernel patches and PHP upgrades, which when handled properly cost you seconds of graceful restart. Then hardware, disks mostly, which is what RAID and real backups exist for. Then network events: upstream carrier trouble, DDoS weather. Last, and by far the most famous, whole-datacentre incidents.
The order matters because the advertised figure covers only a slice of it. An uptime SLA records whether the server responded, not whether your site worked. The plugin that broke your checkout registers in no one's downtime column. Which is why daily backups and a staging environment do more for the uptime your visitors actually feel than the distance between 99.9% and 99.95% ever will.
Reading an uptime guarantee properly
Three questions cut any SLA down to its substance. First, who keeps score? A guarantee graded by the host's own monitoring, with maintenance windows carved out, is weaker than one you can audit yourself. Add free uptime monitoring to your site in ten minutes and the scorecard becomes yours.
Second: what lands in your account when it does fail? The usual SLA credit refunds downtime pro rata, and an hour offline works out at pennies. Read the guarantee as a declaration of engineering intent, never as insurance. Judge the host on its status-page history and on how it talks to you mid-incident, rather than on the credit formula.
Third: what has been carved out? Scheduled maintenance, emergency maintenance, DDoS, upstream failures, force majeure. Those are the standard exclusions. A shorter list means a headline number that is worth more.
How we run our end of it
Concretely, here is how ours is built. NVMe RAID storage, so one dead disk changes nothing at all. LiteSpeed serving cached pages, which keeps most traffic spikes away from PHP entirely. Per-account resource isolation, so a neighbour having a rough afternoon does not drag you into it. External monitoring running non-stop, wired to alerts that wake a real person. Daily backups with self-service restores, which turns the commonest failure class of the lot, the application kind, from an outage into a ten-minute rollback.
And the limits, stated plainly. We run scheduled maintenance, announced, off-peak and measured in seconds. We depend on upstream networks like every other host. A determined DDoS is weather we absorb and mitigate rather than something we can abolish. We commit to 99.9% on every plan because that is the level we can sustain across thousands of accounts, and we would rather walk you through the number than leave it on the page as decoration.
Quick answers
How much downtime does 99.9% uptime allow?
About 43.8 minutes in a month, which stacks up to roughly 8 hours 46 minutes over a year. 99.99% permits 4.4 minutes a month instead. Engineering that gap away costs a great deal more than the downtime ever costs a typical small site, so 99.9% paired with quick, honest recovery is the sane target for shared hosting.
Does an uptime guarantee actually pay out anything useful?
Almost never. A standard credit hands back the downtime pro rata, and that comes to pennies. Read the SLA as an engineering commitment you can hold a host to. Then check it yourself with a free external monitor, rather than trusting the dashboard the host built.
Up next
Service Status
A hand-maintained log of anything broken on our side at this moment.
Monitor Your Own Uptime
Outside monitoring pointed at your own site, live inside ten minutes.
Uptime (Glossary)
A definition of uptime, how the nines work, and the arithmetic underneath.
More from the blog
What web hosting really costs in 2026
That opening price is the hook. What renews is the thing you signed up for. Below, the three-year arithmetic, worked out in the open.
“Unlimited” web hosting: the ceilings nobody puts on show
Hardware runs out. 'Unlimited' really translates to capped in units nobody ever counts: inodes, CPU seconds, and a single fair-use clause.
Free domain with hosting: run these four checks before you claim one
Nothing to pay in year one. That much is true. Year two is where you start reading: renewal price, registrant name, terms for leaving.
The hosting platform behind these posts
Flat renewals, limits stated up front, free migration and support that actually writes back — all of it bundled into a plan.
Browse Hosting Plans