The true cost of website downtime is much bigger than the sales lost while the site is offline — it includes missed leads, wasted ad spend, recovery time, and damaged trust that can outlast the outage by months. For a large enterprise, an hour offline can run into six figures. For a small business, the dollar figure is smaller but the proportional hit is often worse, because there’s less cushion to absorb it. This guide breaks down what downtime actually costs, how to estimate your own number, and why most of it is preventable.
What does website downtime actually cost?
It’s tempting to think of downtime as just “lost sales for a few hours.” That’s the visible part, but it’s rarely the biggest part. The real cost has four components:
- Lost revenue. Every minute an e-commerce site or booking page is down, transactions that would have happened simply don’t. For a site that sells or captures leads, downtime is a direct hit to the top line.
- Lost productivity and wasted spend. If your team can’t work because internal tools or the site are down, you’re paying for idle time. And if an ad campaign, email blast, or product launch is driving traffic to a dead page, you’re paying for clicks that bounce.
- Recovery costs. Getting back online isn’t free — emergency developer time, support hours, and sometimes new tooling or cleanup if the outage was caused by a security incident.
- Lost trust. The one that lingers. A visitor who hits a broken or unavailable site doesn’t usually complain — they just leave, and many don’t come back. That damage shows up later in retention, not in the day’s sales report.
The first three are measurable. The fourth is the one businesses underestimate most, and for a small business that runs on reputation and repeat customers, it can be the costliest of all.
How to estimate your own downtime cost
You don’t need a fancy model. A rough, honest estimate beats a vague worry. Start with revenue:
Lost revenue per hour = annual revenue ÷ annual operating hours.
For example, a small online store doing $500,000 a year, available around the clock, averages roughly $57 in sales per hour. That sounds modest — until you remember outages don’t politely wait for quiet periods. If the site goes down during a promotion, a launch, or a peak shopping window, the real loss can be many times the average.
Then add the other components: the hourly cost of any idled staff, the likely recovery expense, and a realistic sense of how many customers you’d lose for good. The total is almost always higher than the “lost sales” figure people start with.
For context on the upper end: in ITIC’s 2024 Hourly Cost of Downtime survey, more than 90% of mid-size and large organizations put a single hour of downtime above $300,000. You don’t need to be anywhere near that size for downtime to hurt — the point is that the cost scales with how much your business depends on its site, and almost every business depends on it more than it thinks.
Why small businesses feel downtime harder
Big companies lose more in absolute dollars, but they also have redundancy, reserves, and brand goodwill to fall back on. A small business usually has none of that cushion:
- A larger share of revenue often flows through a single site.
- There’s no spare team to drop everything and fix it without something else slipping.
- Trust is harder to rebuild when you don’t have a household name protecting you.
So while the headline numbers belong to the enterprises, the proportional damage frequently lands hardest on the smallest businesses.
The hidden cost: trust doesn’t come back on its own
Here’s what makes downtime sneaky. The lost sales during an outage are recoverable — business resumes when the site does. The lost trust is not so simple. When someone tries to buy, book, or contact you and the site is down or broken, their impression of your reliability takes a hit. Most won’t tell you. They’ll just quietly choose someone else next time.
That’s why downtime is a brand problem, not only an IT problem — and why “we were only down for an hour” understates the real cost.
The good news: most downtime is preventable
The encouraging part of all this is that a large share of downtime and the incidents that cause it are preventable with earlier detection and basic discipline. Many outages trace back to issues that gave warning signs — an expiring certificate, a failing server, an unpatched vulnerability — that simply weren’t caught in time.
That’s the case for monitoring in a sentence: the goal isn’t to react faster after a site goes down, it’s to catch the warning signs and fix them before it does. Continuous monitoring is what turns “we found out when a customer emailed” into “we fixed it before anyone noticed.”
For agencies: your client’s downtime is your problem
If you manage client websites, downtime isn’t an abstract risk — it’s the phone call you don’t want. When a client’s site goes down, you’re the one expected to have caught it and fixed it, and an outage can strain or end the relationship even if the root cause wasn’t yours.
That’s exactly why proactive monitoring and care plans exist: they let you spot and resolve issues before clients ever notice, protect the relationships your business depends on, and turn “keeping sites up” into a service clients can see and value.
Frequently asked questions
How much does website downtime cost? It varies by business size and how much revenue depends on the site. Large organizations can lose over $300,000 per hour (ITIC, 2024), while small businesses lose less in absolute terms but often more proportionally. The full cost includes lost revenue, lost productivity, recovery expenses, and damaged customer trust.
How do I calculate my website’s downtime cost? Start with lost revenue per hour (annual revenue ÷ annual operating hours), then add the cost of idled staff, expected recovery expenses, and the value of customers lost to the outage. Outages during peak periods cost far more than the average suggests.
What is the biggest cost of website downtime? For many businesses, the biggest cost isn’t the lost sales during the outage — it’s the lost trust afterward. Customers who hit a broken site often leave quietly and don’t return, which shows up in retention rather than that day’s revenue.
Can website downtime be prevented? Much of it can. A large share of outages stem from issues that give early warning signs, like expiring certificates, failing infrastructure, or unpatched vulnerabilities. Continuous monitoring catches these before they cause an outage.
Catch issues before they become outages
Centry Secure monitors the sites you manage around the clock and alerts you the moment something changes — so problems get caught early, not after a customer notices. Schedule a demo to see how it protects uptime across every site you manage.
Was this article helpful?
Thanks for your feedback.
Have a question about this topic?