StatusCake

7 stats about website downtime that will blow your mind

uptime

We believe that data speaks volumes and that’s why we’ve put together the most shocking 7 stats that we’ve found from our uptime monitoring report. You have to see them to believe them!

How many people experience website downtime

If we had £1 for every time someone said that website downtime wasn’t going to affect them, we’d each be millionaires hundreds of times over (and what a life that would be!). But unfortunately for these people, downtime doesn’t work like that, it doesn’t discriminate and will catch you out when you least expect it. 

Our latest statistic found that:

71% of companies experienced unplanned partial website downtime, as well as full unplanned website downtime. 100% of companies experienced planned downtime. Partial downtime where individual pages or areas of a website are unavailable and full downtime whereby all pages are completely unavailable (StatusCake survey 2021)

What happens if I don’t have an uptime or website monitoring solution

It’s easy to think that a short amount of website downtime will have little or no effect on your revenue or your customers. Wrong. We’ve found time and time again that there is a significant impact on a multitude of different areas in your business when your website goes down. But that’s not all, domain issues, server outages, slow page speed and outdated SSL certificates can all cause significant damage too.

Take this statistic for example:

79% of websites we surveyed experienced one or more of the following:

  • Lost domain, either through domain hijackers or expiry
  • Loss of customers due to an unsecure website (lack of SSL certificate)
  • Loss of revenue due to unforeseen downtime
  • Loss of trust from customers due to server downtime
  • Loss of customers to competitors due to low page speed
  • Loss of SEO rankings due to all of the above

How do people find out about website downtime

It can be easy to think that you’ll “just know” when your website goes down, like a sixth sense. Unfortunately, this is never the case and the likelihood of your team picking up on it before anyone else is also very slim. 

See why we know this here:

8/10 people who weren’t using an uptime monitoring tool, said that they found out about website downtime through customers emailing them, or @’ing them on social media

But what does website downtime actually mean?

If you’ve read all of the stats and are sat there wondering what on earth we actually mean by website downtime, you’re not the online one:

According to our recent survey of 1500 people, 32% of people didn’t know what website downtime meant.

Website downtime can mean partial or full “downtime” that causes your website to go offline or be inaccessible. 

What do customers think of this?

We are all customers online, whether it’s for online banking, grocery shopping, or endless Just Eat deliveries (not me, of course). So what do we as customers think of website downtime? Ultimately, do we care?

When we surveyed 1500 people on how likely they are to revisit a website after they couldn’t access it just one time, only 11% said they would return, stating that trusting the website would be difficult after. 

How often does website downtime really happen?

Out of our 140,000 customers that use our uptime monitoring tool, 32% consider themselves to be a small company, 41% a medium company, and 27% a large company. Of those 32% of small companies, they experience downtime, on average, at least 18 times a month

What’s one example of an outage that affected global companies?

There are plenty that we could use as an example, especially with the likes of Facebook experiencing regular downtime and causing companies that use their paid ads feature to lose millions in revenue. But let’s take Fastly’s outage as an example, StatusCake saw 58% more websites go down during this time compared to the previous week, proving how heavily reliant websites are on CDNs.

Share this

More from StatusCake

Alert Noise Isn’t an Accident — It’s a Design Decision

3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.

The Incident Checklist: Reducing Cognitive Load When It Matters Most

4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already

When Things Go Wrong, Systems Should Help Humans — Not Fight Them

3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,

When AI Speeds Up Change, Knowing First Becomes the Constraint

5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things

Make Your Engineering Processes Resilient. Not Your Opinions About AI

4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development.  For some teams, it’s an obvious productivity multiplier.  For others, it’s viewed with suspicion.  A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes

Blog

How to monitor IPFS assets with StatusCake

3 min read IPFS is a game-changer for decentralised storage and the future of the web, but it still requires active monitoring to ensure everything runs smoothly.

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

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.