The Cost of Website Downtime: How to Calculate Yours

The cost of website downtime is the revenue you lose while the site is unavailable, plus the hidden costs that follow: staff time, support load, wasted advertising and customers who do not come back. For a business that sells online, a useful starting point is simple: divide your online revenue per hour by 60 to get the direct cost of each minute offline. The rest of this guide shows how to build a fuller estimate and what it tells you about where to invest.

All figures below are example numbers chosen to illustrate the calculation. Use your own.

The basic formula

Direct cost per minute = online revenue per hour ÷ 60

Use the revenue for the hours when outages are likely to matter. Average revenue over a whole day understates the cost of an outage at peak time and overstates one at 04:00.

Then estimate the total cost of an incident:

Incident cost = (direct cost per minute × minutes down) + hidden costs

Hidden costs

Direct revenue is only part of it. Add what applies to you:

• Staff time. Developers and operations staff who drop their work to fix the issue, often outside working hours.
• Support load. Tickets, calls and chat messages from customers asking what is going on.
• Wasted marketing. Ads, newsletters and campaigns that keep sending paid traffic to an error page.
• Churn and trust. Some customers try once and leave for good. For subscription products, repeated incidents lead to cancellations.
• Contract penalties. If you promise availability to your customers, outages can trigger credits.
• Search visibility. Long or frequent outages can make it harder for search engines to crawl your pages.

These are harder to measure, but even a rough figure makes the estimate more realistic.

Example 1: an online store

*Example numbers.* A store makes €2,400 per hour online on a typical afternoon.

• Direct cost per minute: €2,400 ÷ 60 = €40.
• The checkout fails for 45 minutes before anyone notices and 15 minutes to fix: 60 minutes, €2,400 in direct revenue.
• Two people spend an hour each on the incident and the follow-up, and support handles 30 extra contacts.
• A newsletter sent that morning keeps driving traffic to the broken checkout.

The direct loss alone is €2,400. Of the hour, 45 minutes were spent not knowing about the problem. With alerts within a minute or two, the same fix would have taken about 17 minutes and cost about €680 in direct revenue.

Example 2: a SaaS product

*Example numbers.* A SaaS company has 400 customers paying €80 per month on average. Customers do not pay per minute, so the direct revenue loss during an outage is small. The real cost is elsewhere:

• Support receives a wave of tickets within minutes.
• Customers’ own work stops, and some lose confidence.
• If 1% of customers cancel after repeated incidents, that is 4 customers × €80 × 12 months = €3,840 in yearly revenue.

For SaaS, the measure that matters is often trust, and the best protection is fast detection plus clear communication on a status page.

What uptime percentages mean

Uptime targets sound similar, but the downtime they allow is very different. Over a year:

• 99%: 3 days, 15 hours and 36 minutes.
• 99.9%: 8 hours, 45 minutes and 36 seconds.
• 99.99%: 52 minutes and 34 seconds.

Multiply those minutes by your cost per minute to see what each level is worth to you. Using the store example above, 99.9% uptime would allow 525.6 minutes per year, or about €21,000 in direct revenue if all of it happened at a typical afternoon rate.

Where the time goes in an outage

Every outage has three phases:

1. Detection: the time until someone knows.
2. Response: the time to find the cause.
3. Recovery: the time to fix it and confirm it is fixed.

Detection is often the longest phase, especially at night and at weekends, and it is the cheapest to shorten. A check every minute, confirmed by a second check and sent to a team chat or a phone, reduces detection from hours to a minute or two. Uptime monitoring and alerts address exactly this phase.

Response and recovery get shorter with good information: which check failed, from where, with which status code, and what the server’s CPU, memory and disk looked like at the time. Server monitoring helps here.

Using the number

A cost estimate is only useful if it changes decisions. Three ways to use it:

• Prioritise monitoring. Pages with the highest cost per minute get one-minute checks, content validation and SMS alerts. Low-impact pages can use simpler checks.
• Justify infrastructure spending. If one hour of downtime costs more than a year of a second server, the second server pays for itself after a single incident.
• Set response expectations. If a night-time outage costs €40 per minute, someone should be reachable at night, or the business should accept that cost knowingly.

Revisit the estimate once a year or when your revenue changes significantly. A number that was right for a small store can be badly wrong after a successful season.

Measuring your actual downtime

Estimates need real data. Monitoring history gives you the inputs: how many incidents you had, how long each lasted and at what time of day they happened. Monthly email reports collect this automatically, so you can multiply real minutes by your cost per minute instead of guessing.

Reducing the cost of downtime

1. Calculate your cost per minute for your busiest hours.
2. Monitor what earns money: checkout, signup, login and APIs, not just the homepage.
3. Check every minute for business-critical pages.
4. Alert where people will see it, including at night.
5. Watch what silently expires or stops: SSL certificates, domains and cron jobs.
6. Communicate: a status page reduces support load during incidents.
7. Review incidents monthly and fix the causes that repeat.

Summary

Downtime cost = cost per minute × minutes down + hidden costs. For most businesses, the minutes spent not knowing about an outage are the most expensive and the easiest to remove. Calculate your number, then compare it with what monitoring costs. For the wider business case, see why uptime monitoring is essential for a business website.

Uptimecheck starts at €9 per month billed yearly. See pricing, or try it free for 14 days, no credit card required.