Downtime Cost Calculator from Sandglass helps you estimate the business impact of an outage. Use the result to decide what to monitor continuously.
Reach for this when you need to estimate the business impact of an outage during setup, debugging, or an incident review. A one-off check is useful for diagnosis, but production systems need continuous monitoring once the immediate question is answered.
Use the estimate to prioritize monitoring for the services where downtime carries real revenue, support, or contractual cost, and to justify tighter check intervals where they pay off.
A downtime number is only as good as its inputs. Treat it as a way to rank what to protect first, not as an exact figure to quote in a contract.
Use the output to confirm the current state, and treat anything surprising as a starting point for diagnosis rather than a verdict.
Write down which results count as healthy, degraded, or failed before you automate anything.
Recreate the same check in Sandglass on an interval so the next change is caught automatically.
Send failures to email, a Slack webhook channel, or a generic webhook owned by whoever will fix them.