Website Downtime Cost Calculator

Estimates what a single outage costs a SaaS or online business in lost revenue, response labor and credits, so you can put a real number on uptime.

Your estimate

Revenue lost during the outage...

Incident response labor...

Total estimated outage cost...

Cost per minute of downtime...

Estimates only. Assumptions are listed below, and you can change every input.

Most teams know downtime is expensive, but very few can say what one outage actually costs them. That makes it hard to justify a monitoring budget, decide how fast an on-call rotation needs to respond, or explain to a founder why a 90 minute incident matters. This calculator turns the vague feeling into a dollar figure you can defend.

The estimate spreads your monthly online revenue evenly across the month to get a revenue-per-minute rate, applies the share of that revenue that actually stops during an outage, and multiplies by the outage length. It then adds the loaded cost of the people who responded and any fixed costs you enter, such as SLA credits or refunds. It does not try to guess churn or reputation damage, because no formula can do that honestly for your business.

How to use this tool

Enter your typical monthly online revenue and the share of it that genuinely stops when the site or app is down.
Enter the outage length in minutes, how many people worked the incident and their loaded hourly cost.
Add any known fixed costs such as SLA credits, then read the total cost and the cost per minute to compare against your monitoring and on-call spend.

What the math assumes

Revenue is assumed to arrive evenly across a 30 day month (43,200 minutes); if your traffic peaks at certain hours, an outage during a peak costs more than this estimate.
Lost revenue is treated as gone, not delayed. If most customers simply come back later, your true loss is lower.
Response labor is counted for the full outage length for every responder you enter, at the loaded hourly cost you set.
Churn, reputation damage and lost future signups are not estimated; add them to the other fixed costs field if you have a number you trust.
All figures are in US dollars and no taxes or currency conversions are applied.

Frequently asked questions

Why is the revenue loss lower than I expected for a long outage?

Because the calculator spreads revenue evenly across the whole month, including nights and weekends. A 90 minute outage is only about 0.2 percent of a month. If your outage happened during your busiest hours, raise the monthly revenue figure or lower the outage length to model that peak.

What should I count as a responder?

Anyone whose normal work stopped because of the incident: on-call engineers, support staff answering tickets, and managers coordinating updates. Use their loaded hourly cost, which is usually 1.25 to 1.4 times base pay once benefits and overhead are included.

How do I use the cost per minute figure?

Compare it with how long it takes your monitoring to detect an outage. If detection takes 10 minutes and each minute costs 5 dollars, a faster check interval that shaves 8 minutes off detection saves about 40 dollars per incident before anyone even starts fixing it.

Link to this toolhttps://pingcrumb.com/tools/website-downtime-cost-calculator/

Free for readers and publishers alike. If you cite the result in an article, a link to this page helps others find it.

More free tools from PingCrumb

Uptime SLA Error Budget Calculator: Converts an uptime target like 99.9 percent into allowed minutes of downtime, then checks whether your real incident pattern fits inside that budget.
Uptime Check Interval Detection Time Calculator: Shows how long an outage can go unnoticed at a given check interval and confirmation setting, and how many monitoring requests that setup sends per month.

Know before your customers do

Uptime monitoring and hosted status pages.

Start monitoring