99.9% vs 99.99% Uptime: What Hosting Uptime Guarantees Really Mean
A 99.9% uptime guarantee still allows 43 minutes of downtime a month. The math behind each nine, what SLAs exclude, how credits work and how to monitor.
"99.9% uptime guaranteed" appears on almost every hosting sales page. It sounds close to perfect. It isn't, and the word "guaranteed" is doing a lot of work.
An uptime guarantee is really a promise of a partial refund if the host misses a target. It doesn't stop your site going down. Here's what the numbers actually allow, what the fine print usually leaves out, and how to keep your host honest.
The math behind each "nine"
Uptime percentages translate directly into allowed downtime. A 30-day month has 43,200 minutes, and a year has 525,600.
Allowed downtime per 30-day month. Bars on a log scale.
Uptime
Downtime per month
Downtime per year
99%
7 h 12 min
3 days 15 h 36 min
99.5%
3 h 36 min
1 day 19 h 48 min
99.9%
43 min 12 s
8 h 45 min 36 s
99.95%
21 min 36 s
4 h 22 min 48 s
99.99%
4 min 19 s
52 min 34 s
Compare hosts the community actually votes for
Real customers rank providers by speed, support and value — no paid placements.
You can check any of these yourself: multiply the downtime percentage (100% minus the uptime) by the minutes in the period. For 99.9% that's 0.1% × 43,200 = 43.2 minutes a month.
Two things jump out:
Each extra nine cuts allowed downtime by a factor of ten. Going from 99.9% to 99.99% isn't a small upgrade. It needs redundant hardware, failover and a lot more engineering, which is why it costs more.
99.9% still allows almost nine hours of downtime a year. For a hobby site that's fine. For a store doing steady sales, it might not be.
What an uptime SLA actually promises
The guarantee lives in a document called a Service Level Agreement (SLA). Read it, because the details vary a lot between hosts. Most share the same structure.
Credits, not compensation
If the host misses its target, you get service credit: a discount on future bills, usually a percentage of that month's fee. It's not compensation for lost sales.
Real examples show how modest this can be. One managed services provider's SLA offers a 10% credit when uptime falls below 99.9% but stays above 99.0%, rising to 25% and 50% at lower levels (Gotekky SLA). Kinsta's SLA says downtime must exceed 43 minutes in a month before a 99.9% guarantee pays anything, and caps credits at that month's fee (Kinsta SLA).
If your hosting costs $10 a month and an outage costs your business $2,000, a $1 credit is not insurance. Plan accordingly.
Exclusions
SLAs typically exclude some or all of the following from the downtime count (example terms):
Scheduled maintenance, if it was announced in advance.
Emergency maintenance done for security or stability.
Problems you caused, such as a broken plugin, a bad config change or going over your plan limits.
Third-party failures, such as DNS, CDN or upstream network outages.
Attacks and force majeure, like DDoS attacks, natural disasters and other events outside the host's control.
Take those out and the guarantee covers a narrower set of failures than the headline suggests.
You have to claim it
Credits are rarely automatic. You usually have to open a ticket, often within a fixed window. Ghost's hosting SLA, for example, requires a written request within 30 days of the incident (Ghost SLA). Miss the window and you get nothing.
How the host measures it
Ask how uptime is measured. Is it your site responding to an HTTP request, or the server answering a ping? Checked from where, and how often? A server can respond to pings while your site returns errors. Hosts measure from their side, which is exactly why you should measure from yours.
Monitor your host yourself
Independent monitoring is cheap or free and gives you the data you need to claim credits or justify leaving.
Set up an external uptime monitor. Many services check your site every minute or few minutes from several locations and alert you by email, SMS or chat. Free tiers are plenty for most sites.
Check a real page, not just the homepage. Monitor a page that loads from the database, and look for a specific word in the response. That catches the "server is up but the site shows an error" case.
Keep a log of incidents. Note start time, end time and what you saw. When you claim a credit, your evidence beats "it felt slow".
Watch response time too. Pages that crawl at 8 seconds are technically up and practically broken. Google considers a Time to First Byte of 0.8 seconds or less good.
Use a status page. If you run a business site, a public status page tells customers you know about an issue, which cuts down the "is your site down?" emails.
How much uptime do you actually need?
Be honest about what downtime costs you.
Type of site
Reasonable target
Why
Personal blog or portfolio
99.5%–99.9%
A short outage is an inconvenience, not a loss
Small business brochure site
99.9%
Customers mostly need contact details and opening hours
Online store or SaaS
99.95%–99.99%
Every minute down is lost revenue and trust
Payment or critical infrastructure
99.99%+
Requires redundancy across servers or regions, not just a good host
Past about 99.95%, uptime stops being something you buy from a host and becomes something you design: load balancers, replicated databases, multiple regions and tested failover. A single server, however good, can't promise four nines on its own.
Questions to ask a host before you sign
What's the guaranteed uptime, and where's the SLA document?
What exactly counts as downtime, and what's excluded?
How is uptime measured, from where and how often?
What credit do I get, and how do I claim it?
Do you have a public status page with incident history?
How long were your last few major incidents, and what caused them?
A host that answers these clearly is usually a host that runs a tight ship. Evasive answers tell you something too.
Frequently asked questions
Is 99.9% uptime good?
It's the industry baseline for shared and VPS hosting, and it's fine for most sites. Just know it allows about 43 minutes of downtime a month without breaking the promise.
Does 100% uptime exist?
Not really. Some hosts advertise it, but networks, hardware and software all fail eventually. A "100%" guarantee simply means credits are available for any downtime the SLA counts, so read what it counts.
Does downtime hurt SEO?
Brief, occasional outages generally don't cause lasting ranking damage. Extended or frequent downtime can, because search engines may struggle to crawl your pages and visitors bounce. Monitoring helps you catch problems early.
What's the difference between uptime and availability?
They're often used interchangeably. Strictly, uptime is whether the server is running, and availability is whether users can actually use the service. Availability is the one you care about.
Want hosts with a proven track record? Read real customer reviews on HostingVotes, where reliability is one of the first things members write about.
