Blog · Operations
99.9% uptime: what that figure buys you, and what really breaks
By the Hosting Seller team Published 27 July 2026 7 min read

Three nines gets advertised by every host going. Hardly any of them explain what that figure covers, what falls outside it, or how a hosting platform actually breaks down. We run one. Keeping the number mysterious is good for marketing and no use to customers, so here is the operational view, in plain terms.
Start with the arithmetic. 99.9% uptime leaves room for 43 minutes and 50 seconds of downtime each month. Move to 99.99% and you get 4 minutes and 23 seconds. As for 100%, nowhere has ever managed it. Any host claiming that figure is telling you about an ambition, a hole in its measuring, or a refund policy. Not about its infrastructure.
What genuinely takes websites offline
Ranked, roughly, by how often we see each one on shared platforms. Application failures lead: a plugin update white-screens WordPress, the site goes dark, and the server underneath is in perfect health throughout. Resource exhaustion follows, where either your own traffic spike or a neighbouring account collides with PHP process limits. After that come deployments and maintenance, kernel patches and PHP upgrades among them, which when handled well amount to a few seconds of graceful restart. Hardware sits below that, disks above all, which is the reason RAID and proper backups exist. Network events next: trouble at the upstream provider, plus whatever DDoS weather is blowing. Whole-datacentre incidents come last, and they are the famous ones.
Why does that order matter? Because the advertised figure only covers a slice of it. What an uptime SLA records is whether the server answered, not whether your site worked. Nobody's downtime ledger mentions the plugin that broke your checkout. So daily backups and a staging copy will do more for the uptime your visitors actually feel than the distance between 99.9% and 99.95% ever will.
How to read an uptime guarantee
Any SLA reduces to its substance under three questions. First: who does the measuring? A guarantee scored by the host's own monitoring, with maintenance windows carved out of it, is softer than one you can verify yourself. Spend ten minutes putting free uptime monitoring on your site and the record belongs to you.
Second: what is the remedy? Most SLA credits hand back the downtime pro rata, which for an hour offline works out at pennies. Treat the guarantee as a statement of engineering intent, not as insurance. Judge a host instead on the history sitting in its status page, and on the way it talks to you while something is broken, rather than on the credit formula.
Third: what falls outside it? Scheduled maintenance, emergency maintenance, DDoS, upstream failures, force majeure. Those are the standard carve-outs, and the shorter that list runs, the more the headline number is worth.
What we do about it
So, concretely, where we stand. Storage is NVMe on RAID, which turns a single failed disk into a non-event. LiteSpeed serves cached pages, so most traffic spikes never reach PHP at all. Resources are isolated per account, meaning a neighbour's bad afternoon stays their bad afternoon. External monitoring runs continuously, with alerts that wake a human up. Backups run daily and restores are self-service, which makes the commonest failure of the lot, the application-level kind, a ten-minute fix rather than an outage.
Now the limits, said plainly. Scheduled maintenance happens here: announced beforehand, kept off-peak, measured in seconds. Upstream networks carry us, the same as everyone else. A determined DDoS counts as weather we can lessen, not stop. Our commitment is 99.9% on every plan, because that is the figure we can hold across thousands of accounts, and explaining it beats leaving it on the page as decoration.
Short answers
99.9% uptime works out at how many minutes of downtime?
Around 43.8 minutes a month, which comes to roughly 8 hours 46 minutes across a year. At 99.99% you are allowed 4.4 minutes a month. Engineering away that difference costs far more than the downtime itself costs a small site, and that is why 99.9% paired with fast, honest recovery is the sensible landing spot for shared hosting.
Do uptime guarantees pay out meaningful compensation?
Rarely. The usual credit repays the downtime pro rata, and that comes to pennies. Read an SLA as an engineering promise you can hold your host to. Then check it yourself with a free external monitor, instead of taking the provider's own dashboard at its word.
Read next
Service Status
A board we update by hand listing whatever is going wrong at our end right now.
Monitor Your Own Uptime
Ten minutes is all it takes to add independent monitoring.
Uptime (Glossary)
What uptime means, how the nines work, and the sums.
Also on the blog
Web hosting costs in 2026: the whole bill
That number on the shelf edge is marketing. What you pay from year two onward is the actual deal. Here is the three-year sum, done in public.
“Unlimited” web hosting, and where the ceilings actually sit
A disk has a size. Read 'unlimited' as 'limited by units you have not bumped into yet': inodes, CPU seconds, one fair-use paragraph.
A free domain with your hosting: four things to check before claiming it
That free year is real enough. Year two carries the questions worth asking: what the renewal rate is, whose name sits on the record, what walking away costs you.
The product behind the posts
Flat renewals, limits printed on the tin, free migration and a help desk that replies — everything above, in plan form.
Browse Hosting Plans