
Every hosting company sells uptime, and almost every hosting company sells it with a number: 99.9%, 99.99%, occasionally five nines. The number is presented as the answer to a question, and it is worth being precise about what question it actually answers. It answers: how often did our server respond to a request? The question a business owner is actually asking is: how often was my website working? Those are not the same question, and the gap between them is where most real downtime lives. A WordPress site can return a clean HTTP 200 response with a white screen where the content should be. It can serve a homepage perfectly while the checkout throws a fatal error. It can load in two seconds for a visitor in Toronto and time out for a visitor in Halifax. It can look entirely healthy while the contact form has been silently failing to send for eleven days. Under every uptime SLA in the industry, all four of those sites were up. This article is about the difference. What actually takes WordPress sites offline — which is almost never a hardware failure — what a managed environment genuinely prevents, what it demonstrably cannot prevent no matter what the sales page says, and how to monitor your own site in a way that catches the failures the uptime number is blind to. It is written for Canadian business owners and the people who look after their sites: the ones who have been told managed WordPress hosting is more reliable, and want to know specifically what that buys and where the limits are. What an uptime SLA actually measures Start with the arithmetic, because most people have never done it. SLA figure Downtime allowed per month Per year 99.0% 7 hours 18 minutes 3 days 15 hours 99.5% 3 hours 39 minutes 1 day 19 hours 99.9% 43 minutes 8 hours 46 minutes 99.95% 21 minutes 54 seconds 4 hours 23 minutes 99.99% 4 minutes 19 seconds 52 minutes 36 seconds 99.999% 26 seconds 5 minutes 15 seconds Two things jump out. First, the difference between 99.9% and 99.99% is not a rounding detail — it...









