Monitoring
Status Pages
Pricing
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!
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
