Every web host advertises an uptime guarantee. 99.9 percent uptime. 99.99 percent uptime. 100 percent uptime. The numbers all look impressive in marketing material. They sound like promises of a site that never goes down.
The reality is more complicated. Uptime guarantees are real but they also come with fine print, exclusions, and caveats that change what the numbers actually mean. This piece covers what uptime guarantees actually deliver, how to read the fine print, and what to do if your host falls short.
What Uptime Actually Measures
Uptime is the percentage of time your site is available and responding to requests. Downtime is the percentage of time your site is unavailable for any reason.
The percentages sound similar but the differences matter at scale.
99 Percent Uptime
Sounds great. Means about 3.65 days of downtime per year. Not great. That is more than an hour of downtime per week on average. Hosts that promise only 99 percent uptime are not promising much.
99.9 Percent Uptime
The standard promise. Means about 8.76 hours of downtime per year. Still meaningful if it all happens at once during a high-traffic event. Usually it does not, but a bad outage can eat the whole annual allowance in one bad afternoon.
99.99 Percent Uptime
Means about 52.6 minutes of downtime per year. This is what premium hosts promise. It is genuinely strong reliability.
99.999 Percent Uptime
Means about 5.26 minutes of downtime per year. This is “five nines” reliability. It is the territory of enterprise infrastructure and serious telecom systems.
100 Percent Uptime
Some hosts promise 100 percent uptime. The promise is technically impossible to guarantee in practice (something will eventually go wrong), but the SLA usually covers credits if anything goes wrong, which is what really matters.
How Uptime Guarantees Work
The promise is one thing. The actual contract is another.
What the Guarantee Covers
Most uptime guarantees cover the host’s own infrastructure and services. They cover server outages, network problems on the host’s side, and major incidents at the host’s data centers.
If the host’s servers are down, the guarantee kicks in.
What the Guarantee Does Not Cover
This is where most users get surprised.
Scheduled maintenance is almost always excluded. Hosts can take their servers offline for maintenance for hours at a time, and it does not count against the uptime guarantee.
Issues caused by you are excluded. If you push broken code, install a bad plugin, or misconfigure something, the host will tell you that is your problem.
Issues caused by third-party services are usually excluded. If your CDN goes down, your domain registrar has DNS problems, or an external API you depend on fails, the host’s guarantee does not cover it.
DDoS attacks are sometimes excluded. Some hosts cover them. Others treat them as outside the guarantee. Read the fine print.
Force majeure is always excluded. Natural disasters, fires, earthquakes, internet backbone failures. The host is not on the hook for events outside their control.
How Credits Work
When a host fails to meet the uptime guarantee, the standard remedy is service credits. You get a credit toward your next bill, usually a percentage of the monthly fee.
The credits are usually modest. A typical SLA might give you a 5 percent credit for missing 99.9 percent uptime by a small amount, scaling up to 100 percent of the monthly fee if uptime dropped severely.
Credits do not cover the actual cost of downtime to your business. If your store is down during a sale, the credit toward next month’s hosting bill does not make up for the lost revenue.
How You Claim Credits
This is the part hosts make hard. To claim credits, you usually have to file a formal request within a specific window (often 30 days after the incident), provide proof of downtime, and follow specific procedures.
Most users do not bother claiming credits even when they qualify. The process is annoying enough that the credits often go unclaimed.
What Real Uptime Looks Like in Practice
Independent monitoring tells the real story.
Industry Average
Most well-run hosts hit 99.9 percent uptime over a year. The premium hosts (Kinsta, WP Engine, Liquid Web) typically hit 99.99 percent or better. Budget hosts can run 99.5 percent or worse, depending on the year.
The difference between 99.9 percent and 99.99 percent is the difference between 8.76 hours of downtime per year and 52.6 minutes. For a business site, that is a meaningful gap.
Outage Patterns
Outages are not evenly distributed. A host might run for months without any downtime, then have one bad week with a major incident that eats most of the annual downtime budget.
The pattern matters. A host with one 4-hour outage and no other downtime hits the same uptime percentage as a host with eight 30-minute outages per year. The first feels more reliable even though the math is identical.
The Honest Test
The real test of a host is not the marketing number. It is how they handle outages when they happen. Do they communicate quickly and clearly? Do they fix problems fast? Do they provide credits proactively without making you fight for them? Do they explain what went wrong and what they are doing to prevent it?
Hosts that handle outages well have customers who stay through occasional bad weeks. Hosts that hide problems lose customers fast.
How to Evaluate a Host’s Uptime
Marketing claims are not enough. You need to look at the actual track record.
Independent Monitoring
Services like UptimeRobot, Pingdom, and StatusCake publish uptime data for many hosts. The numbers are usually less rosy than the marketing claims but more accurate.
Hosting review sites also run their own monitoring on hosts and publish the results. The numbers from independent monitoring are the closest to reality you will find.
Status Pages
Look at the host’s status page. If they do not have a public status page, that is a yellow flag. If the status page is full of incidents and outages, that is a red flag. If the status page is clean and the host posts honestly about incidents when they happen, that is a green flag.
Community Reports
Hosting forums, subreddits, and review sites have honest reports from real customers. The patterns there usually match reality better than the marketing.
If you see consistent complaints about outages, slow recovery, or poor communication, take them seriously.
Your Own Monitoring
Once you sign up for a host, run your own monitoring. Tools like UptimeRobot have free tiers that monitor your site from multiple locations and alert you when it goes down. You will see for yourself how the host actually performs.
What to Do When Uptime Falls Short
If your host is not meeting their guarantee, you have options.
Document the Downtime
Keep records of every outage. When it started, when it ended, how long the site was down. Screenshots from monitoring tools are the best evidence.
If you ever need to claim credits or move hosts, this documentation matters.
Claim Credits
If the host missed their SLA, file for the credits. Yes, it is annoying. Yes, the credits are modest. But claiming them sends a signal to the host that you are paying attention, which sometimes affects how they treat your account.
Talk to Support
Sometimes outages are caused by specific issues that affect specific accounts. If you have repeated downtime, talk to support and ask what is happening. Sometimes there are technical issues with your account that they can fix.
Consider Migrating
If a host consistently misses their uptime guarantee, the right move is to switch hosts. The credits do not make up for the lost business, and the pattern usually does not improve.
Migrations are not free in time or effort, but staying with a bad host costs more in the long run.
Closing Thoughts
Uptime guarantees are useful but they are not the full picture. The promise tells you what the host commits to. The track record tells you what they actually deliver. The credit terms tell you what happens when they fall short.
For most sites, 99.9 percent uptime is acceptable. For business sites where downtime costs money, look for 99.99 percent or better. For mission-critical sites, the guarantee should be backed by independent monitoring data and a real history of meeting the promise.
The number on the marketing page is the starting point of the conversation, not the end. Read the fine print. Look at independent data. Talk to current customers if you can. The hosts that quietly deliver consistent uptime are usually different from the ones that advertise the highest numbers.
For a small site, the difference between 99.9 percent and 99.99 percent uptime might not be worth paying for. For a business that loses real money during downtime, the extra reliability is worth the premium. Match the guarantee to your actual needs and you will end up with hosting that fits the stakes of your site.