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
Downtime, how much does it really ‘cost’ you? Well Benjamin Franklin first coined the phrase “time is money”. So when your website goes down, even if only for an hour, do you really know how much it has ‘cost’ you?
In 2008 online retailer Amazon.com had a two hour downtime. In this not time not only did it lose around $29,000 – $31,000 per minute (total loss estimated at $3.6 million) but the share price fell by 4.1% on the day – wiping around $3.12 billion off their stock market value.
Amazon isn’t alone in falling prey to website downtime. eBay reportedly lost around $4 million in revenues from one of its many infrastructure fall-downs; perhaps its worst episode coming back in January 2001 when the auction site was down for over ten hours after its both its main servers and back-up systems failed.
But as we saw in an earlier blog post – “The Importance of Website Monitoring” it’s not just lost revenues that you should be concerned about when your website goes down.
During the downtime at Amazon and eBay where did their customers go? Whilst some may argue that Amazon customers simply came back later, knowing it to be a temporary fault, is this really the case? Isn’t it far easier for customers in that “ready-to-purchase” frame of mind to simply click away to another website and buy that book, CD or DVD they’ve been looking for?
When UK food retailer Sainsburys experienced its own downtime in 2008, the big-data company Experian noted that 8.36% of Sainsburys’ traffic went to its main competitor Tesco.com and a further 1.38% went to ASDA. And of that 10% or so of traffic that went to competitors, did they ever go back to shop at Sainsburys online again – or at least to the save extent?
There seems little doubt then that unless you’re in an online business where you are truly the only player in the market, or your brand is really that strong and dominant, you cannot afford to allow your website to go down.
Yes in part – however big your infrastructure nothing is fool-proof and 100% uptime cannot be guaranteed. But perhaps the bigger lesson – eBay’s 2001 downtime was reportedly due to the company failing to upgrade its hardware as had been recommended. By cutting corners you’re only damaging the long-term success and stability of your business.
But most of all make sure you use website monitoring. This way the moment there is a problem with your website you’re on to it, getting the problem solved before you’ve lost your customers and your reputation!
James Barnes
Share this
More from StatusCake
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
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
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
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,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
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
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
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
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
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,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
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
James Barnes
March 18, 2026