
Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



At first glance 100% uptime may seem like an amazing promise. After all as we’ve seen in some of our blog posts, the cost of your website going down can be catastrophic to your revenues as well as your reputation.
This week one of North America’s hosting companies announced that it was launching a service level agreement – effectively the promises and terms and conditions by which it agrees to keep your website up – with 100% uptime.
But before anyone rushes in and signs up to a hosting service that offers 100% or the more familiar 99.9% uptime packages that are often seen, be careful. Not all 100% / 99.9% hosting services are born equal.
There are a couple of things to consider here:-
Firstly what’s the actual performance of a hosting company. It’s all very well offering 99.9% uptime but do they actually deliver on this?
Secondly, and we’ll talk about this in a little more detail below, “uptime” within SLAs is often defined differently, and depending on the hosting company they may have numerous “exclusions” from what counts as downtime. For instance the 100% uptime SLA excludes any downtime caused by:
• equipment
• events outside the control of the hosting company
• client error
• scheduled or emergency network maintenance; or
• equipment or facility maintenance.
In other words, pretty much everything any anything that could possible cause downtime is excluded!
Even ignoring the possible wide interpretation of “equipment” (presumably any issue with the servers is excluded!), in this example if the hosting company were to have a 23 hour maintenance window every day, but for the one hour they were up they stayed up, they’d still consider this 100% uptime! This is all set out in the SLA, there for us all to read, but is it really transparent?
Most hosting companies have similar provisions in their SLAs – so they’re all as good, or arguably as bad, as each other.
The other area to look at is in relation to “compensation.” Again hosting company SLAs vary, but you want to be looking to see how much downtime there needs to be before you’re given a refund? The answer for most webmasters is you’ll not be entitled to much.
So what can you do if your website keeps going down and the hosting company argue that it’s beyond their control – and won’t refund you?
Unfortunately not a lot. Your ability to terminate your agreement is likely to be severely restricted.
Your best option, given how cheap and competitively priced hosting is these days, is to simply get a better hosting company. Far better to move your website to a new hosting company where your website stays up and you don’t lose money, rather than stay put with your existing host just to save a few dollars. That could be a false economy. Unfortunately you’ll still need to pay for your old host but it’s a price worth paying.
So don’t get seduced by that 100% or 99.9% uptime guarantee – and do your research thoroughly before you buy. And of course most importantly of all, ensure that you’re using a website monitoring service to monitor, detect and alert you to any downtime. And that you have reports that you can send to your hosting company and demand a refund when they’re in breach of the SLA.
Share this

3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
Find out everything you need to know in our new uptime monitoring whitepaper 2021