Monitoring
Status Pages
Pricing
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!
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)
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:
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
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.
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.
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
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
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
