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



Website downtime happens to the best of us, even the likes of mammoth websites like Amazon, Facebook, and Twitter all experience it. Luckily for these big companies, they’re so established and have such a huge customer base that downtime is unlikely to make them lose a large proportion of them. It will, however, cost them larger amounts of money for every second that their website is down. Take Amazon as a prime example. It suffered major downtime back in 2018, costing them an estimated $99 million in lost sales, and an even greater loss on share prices.
But if you’re not as big as Amazon, how does website downtime affect your brand?
Trust is such a big thing when it comes to customers’ purchasing decisions online, especially since there are now so many malicious threats known to us lurking in the deep depths of the internet. That’s why the majority of us will look for signs of a trustworthy site before we willy nilly add in our personal information like our most sacred credit card details.
Trust can take time to build, but it can be lost in just seconds. For example, if your website is down for an hour and your customers/potential customers have no idea what’s happening or why, they’re likely to draw their own conclusions about the safety of your website and move onto your competitor whose website is up and running and looking like this shiny, secure haven of a website.
If you’re not sure if this is truly the case, ask yourself the question: would I go back to a website that has continuously gone down and willingly load my personal data into their system?
With so many companies all claiming to be the “best in the business”, it’s hard to know which one can actually deliver on that promise. Once you’ve drudged through all the marketing hype, you might find what you consider to be a company that is fully able to give you the product or service that they claim.
Then you see that their website goes down consistently. Not just for 1 minute but for hours on end. With no communication from the company as to why this keeps happening. Every time you try to access their website they either have partial or full downtime.
Ask yourself, if you’re buying a SaaS product off of a company’s website that experiences regular website downtime, for example, would you then trust that they can deliver as good of a product as you once thought that they could?
It’s important to remember that all websites experience downtime, but if a website is consistently down or inaccessible, it can be hugely damaging to a brand.
Companies are in constant battles with their competitors, so when one of them goes down, it’s only normal that you’d swoop in and try to nab those customers looking for an alternative. But what about if they do that to you when your website goes down?
Your brand could be the best of the bunch, but your website is essentially your shop window so if your website isn’t working to the expectations of prospective customers then there’s a big problem. In this day and age, customers don’t spend time waiting for websites to load, they’ll simply jump onto the next. The biggest thing to note? Ease of use is a key selling point when it comes to customers on your website.
In a recent StatusCake LinkedIn survey, 98% of people said that their biggest bugbear for cruising the web is a website that won’t load or is down.
There’s nothing more damaging to your brand than an influx of negative comments on social media, especially in an age where things can go viral. So when your website experiences downtime for a prolonged period of time, it’s more than likely that you’ll start to get customers @’ing you on your social media platforms with complaints and questions. The result? Prospective customers see this and think to stay well clear of your brand.
These are just a few of the ways website downtime can affect your brand. The solution? StatusCake of course. Low budget? We have a free for life product. Need a more comprehensive website monitoring solution? Book a demo! We are one of the most cost-effect uptime monitoring tools on the market but don’t take our word for it, head over to Alternative to StatusCake.
We don’t just offer you uptime monitoring either, you’ll get page speed monitoring, server monitoring, domain monitoring, and SSL monitoring all in one product.
Share this
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
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.
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
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,
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
Find out everything you need to know in our new uptime monitoring whitepaper 2021