Downtime is usually discussed as a percentage — three nines, four nines — which is a number that means nothing at 9pm when the store is down and you are trying to decide how much to care. This calculator converts your own revenue into the two figures that do mean something: what an hour offline costs, and what the delay before you find out costs on top of it.
An ordinary month, not your best one.
Stores don't sell evenly around the clock. This multiplies the average hourly rate.
The half you can actually shorten.
One incident, 5 hours total
$547.95
$109.59 per hour during the outage, from an average of $54.79 per hour.
4 hours before you find out
1 hour of repair
If detection took 5 minutes
$429.22 saved per incident
$1,717 across 4 incidents a year. Same repair time — only the delay before you knew is different.
An estimate, not an invoice. It excludes sales you recover afterwards, which makes the real figure lower, and excludes ad spend wasted during the outage and the support cost that follows, which make it higher. Nothing you type here is submitted or stored — it all runs in your browser.
The maths is deliberately simple, because a complicated model built on numbers you had to guess is not more accurate — it is just harder to argue with.
Your revenue is converted to an average hourly rate. If you enter monthly revenue, that is divided across the hours in an average month. If you enter orders per day and average order value, the two are multiplied and spread across a day. The peak-hours multiplier accounts for the fact that stores do not sell evenly around the clock — an outage during your busiest hours costs more than the average hour does.
Lost revenue per incident is the hourly rate multiplied by the total outage duration, where duration is the time before you notice plus the time it takes to fix. That second half is why detection speed shows up as money rather than as a feature: on a two-hour repair, finding out in five minutes instead of four hours removes roughly two-thirds of the cost.
An honest calculator says what it does not know. Three effects are excluded on purpose, and they push in opposite directions.
Most owners cannot shorten their repair time much — a broken app or an expired certificate takes as long as it takes. Detection time is the part that is entirely within your control, and it is usually the larger half.
If you check the store manually a few times a day, your average detection delay is several hours. A monitor checking every 5 minutes brings that to under 3 minutes on average. On the same repair time and the same revenue, that difference is the majority of the cost of a typical incident.
Free scan, results in minutes. No account needed.
What Cassian™ actually does
Cassian Sentinel™ checks your store every 5 minutes on Protector and Guardian, and every minute on Prime and Enterprise — so the detection half of an outage is measured in minutes, not hours.
Protector and above.
Cassian™ also catches the outages that return a 200 OK: when orders stop arriving in a period that historically has them, it raises a critical alert.
Every plan, including free.
Incidents carry their own duration: Cassian™ records when the outage opened, when it recovered, and how long it lasted — so next time this calculator can use your real numbers instead of an estimate.
Protector and above.
FAQ
Free scan, results in minutes. Zero-order alerts on every plan, including the free one.
We use cookies to keep you signed in and improve your experience. See our Cookie Policy for details.