Calculate Your Downtime Losses
Estimate how much website, application, or API downtime is costing your business. Calculate potential revenue loss, productivity impact, and customer disruption caused by outages in just a few clicks.
Reduce downtime. Protect revenue.
Prevent costly downtime before it hits your revenue
Statixoup Sentinel checks your websites, APIs, and services every 30 seconds, detecting outages, latency spikes, SSL issues, and server errors before they affect customers or staff notice.
Calculate Your Downtime Cost in Seconds
Enter your revenue, employee costs, and outage duration to see exactly how much every minute of downtime costs your business.
Downtime Cost Terms Explained
What each field in the calculator means, how to work out your own number, and a real example.
- Revenue lost per hour
- The money your business normally earns in one hour that it cannot earn while the website, app, or API is down. For an online store this is lost sales; for a SaaS product it is lost subscriptions, upgrades, and usage-based billing.
- How to calculate
Revenue per hour = Revenue for a period ÷ Hours your business sells in that period - ExampleAn online store makes $180,000 a month and sells 24/7 (30 days × 24 h = 720 h). $180,000 ÷ 720 = $250 per hour. If you only sell during business hours (e.g. 22 days × 8 h = 176 h), divide by 176 instead.
- Employees affected
- The number of staff who cannot do their normal work during the outage, such as support agents without a ticketing tool, sales reps without a CRM, or warehouse staff who cannot process orders. Count only the people who are actually blocked, not the whole company.
- ExampleDuring the store outage, 8 support agents and 4 order-fulfilment staff cannot work. Employees affected = 8 + 4 = 12.
- Avg. wage per employee
- The average hourly cost of one affected employee, including benefits such as insurance, taxes, and paid leave. You pay this cost whether or not the employee can work, so idle time during downtime is a direct loss.
- How to calculate
Hourly wage = Annual salary ÷ 2,080 working hours Wage incl. benefits = Hourly wage × (1 + benefits %) - ExampleAverage salary is $62,400 a year. $62,400 ÷ 2,080 = $30 per hour. Benefits add about 30%: $30 × 1.30 = $39 per hour.
- Recovery team cost
- What it costs per hour to bring the system back: engineers, IT and support staff working on the incident, overtime, on-call pay, and any outside vendors or consultants you bring in.
- How to calculate
Recovery cost per hour = Sum of the hourly cost of everyone fixing the outage - Example2 engineers at $60 per hour work on the fix. 2 × $60 = $120 per hour.
- Hours of downtime
- How long the system was unavailable, from the moment it stopped working until it was fully restored. Use decimals for partial hours: 30 minutes is 0.5 hours, 15 minutes is 0.25 hours.
- How to calculate
Hours of downtime = (End time − Start time) in minutes ÷ 60 - ExampleThe site went down at 10:15 and was restored at 12:45. 150 minutes ÷ 60 = 2.5 hours.
- Total loss
- The estimated direct cost of the outage: lost revenue, plus the wages paid to idle staff, plus the cost of the team fixing it, multiplied by how long it lasted. It does not include indirect costs such as lost customer trust, SLA penalties, or SEO impact, so the real cost is usually higher.
- How to calculate
Total loss = (Revenue per hour + Employees affected × Avg. wage + Recovery cost per hour) × Hours of downtime - ExampleUsing the numbers above: ($250 + 12 × $39 + $120) × 2.5 = ($250 + $468 + $120) × 2.5 = $838 × 2.5 = $2,095 lost in one 2.5-hour outage.