What this suite is for
Reliability talk fails when it stays abstract. “We need more nines,” “the SLA looks fine,” and “RTO is four hours” sound serious — until someone asks what that means in minutes or money. The Reliability Money Toolkit is the public map of every TechImpact tool that answers those questions without a black box.
You type your numbers. The page calculates in the browser. You can share a URL so finance, SRE, and product argue about the same scenario. We show formulas in guides. We label examples as examples. We do not pretend a service credit equals your full business loss.
This hub is the “god page” for the suite: start paths, the full calculator map, a worked money walkthrough, shareable URL parameter cheat sheets, and links into living outage briefs and open methodology. Built by DynamicDisorder.co. Written in simple English for mixed teams and non-native speakers.
1. Start here (pick your role)
You do not need every calculator on day one. Use a short path, write the result in one slide, then deepen only where the decision is stuck.
Budget & risk story
Open Downtime Cost with a realistic peak-hour rate. Then open Cost of Nines to see what the next nine buys in minutes. Bring both numbers to the investment talk — not a slogan.
Time budgets & recovery
Convert the promised % with Allowed Downtime. Set or challenge targets with RTO/RPO Impact and the decision matrix. After a real incident, re-run duration into Downtime Cost while memories are fresh.
Vendor & customer promises
If you buy cloud, estimate credits with the SLA Penalty Calculator and learn the claim steps in how to file a credit claim. If you sell uptime, model what you would owe customers before you market “99.99%.”
Suggested 30-minute path (any role):
- Write last month’s revenue and the hours you were open → revenue per hour.
- Pick a duration you actually fear (or a recent outage length).
- Run Downtime Cost → copy the share URL into the ticket or doc.
- Check Allowed Downtime for your SLA % this month.
- If recovery design is the debate, run RTO/RPO Impact once with today’s targets and once with the proposed targets.
2. If you ask this → open that
Use this table when the meeting question is clear but the tool name is not. One question, one primary tool, one optional follow-up.
| You are asking… | Open first | Then (optional) |
|---|---|---|
| “What did this outage cost us?” | Downtime Cost | Recent outages brief (for public duration context) |
| “How many minutes does 99.9% allow this month?” | Allowed Downtime | Calendar-month tables |
| “Is the next nine worth the spend?” | Cost of Nines | Downtime Cost with the minute delta as duration |
| “What credit might the contract produce?” | SLA Penalty | How to file a credit claim |
| “Is our RTO / RPO affordable?” | RTO/RPO Impact | Decision matrix |
| “Where do I start on this whole site?” | This page (Toolkit hub) | Open methodology |
3. Calculators grid
Five specialized tools. Each has one job. Use the primary button when you know which question you are answering.
SLA Penalty Calculator
Estimate service credits when actual uptime falls short of a promised percentage and tiered credit table — useful for vendor claims and for understanding what you might owe if you sell an SLA.
Website Downtime Cost Calculator
Estimate business impact from revenue rate, outage length, refunds, conversion drop, and idle staff cost — the default tool after any incident review.
RTO / RPO Impact Calculator
Translate Recovery Time Objective and Recovery Point Objective into yearly exposure so failover and backup spend have a money story.
Allowed Downtime Calculator
Convert an uptime percentage into allowed seconds, minutes, and hours for day, week, month, or year — the time budget behind the marketing number.
Cost of Nines Calculator
Compare two availability targets (for example 99.9% vs 99.99%) and see how the tighter target changes downtime budget and rough cost exposure.
How the tools fit together (one sentence each):
Allowed Downtime / Cost of Nines → “How many minutes does this % allow?”
Downtime Cost → “What does that minute budget cost if we burn it?”
RTO/RPO Impact → “What does our recovery design imply per year?”
SLA Penalty → “What credit might the contract produce?”
4. Worked walkthrough (CloudFront-length window)
This is a teaching scenario, not a claim about any vendor’s P&L. Public reports put the 16 Jul 2026 AWS CloudFront VPC Origins disruption near 3 hours 33 minutes. Use that duration to practice the suite end-to-end.
-
Money impact. Open
Downtime Cost with the illustrative $10k/hour scenario
.
Replace
revwith your peak-hour revenue. Copy the share link into the ticket. - Time budget. Open Allowed Downtime at 99.9% / 30 days. Ask: does 3h33m already burn the whole month (yes — about 43 minutes allowed at 99.9%)?
- Next nine debate. Open Cost of Nines (99.9 vs 99.99) and decide if tighter availability is the investment story — or multi-AZ / origin design is.
- Recovery design. If the real failure mode was “CDN path dead while app servers healthy,” RTO may be about failover of the edge path, not VM restore. Still price current targets with RTO/RPO Impact.
- Credits (separate column). If a paid AWS support / enterprise credit path applies to you, estimate with SLA Penalty using your contract table — never mix that number into the business-loss total without labeling it.
Full source notes for this and other July 2026 incidents live in the Recent outages → money impact brief.
5. References & briefs
Calculators answer “what if.” References answer “what is the table / the claim process / what just happened.” Cite these pages in tickets and RFCs when you need a stable URL.
| Page | Use it when… |
|---|---|
| SLA uptime → downtime reference | You need definitive tables and open formulas (day / week / month / year). |
| Calendar-month SLA tables | Your vendor uses a real calendar month (28–31 days), not a fixed 30-day month. |
| RTO / RPO decision matrix | You are choosing recovery targets by system type in plain English. |
| How to file an SLA credit claim | You have logs and a deadline, and you need a clean evidence pack. |
| Recent outages → money impact | You want a living brief of major incidents (last 14 days) with illustrative calculator links. |
Deeper reading also lives on All guides (SLA penalties, downtime cost why-it-matters, real-world examples, disaster recovery basics, and more) and the older Resources hub.
6. How sharing works (scenario URLs)
Calculators write inputs into the query string so a colleague opens the same scenario. That is better than screenshots: people can edit one field and see the new total immediately. Use the Share Link / Copy share link button on each tool, or copy the address bar after you change inputs.
Example — illustrative downtime at $10,000/hour for 3 hours 33 minutes:
Parameter cheat sheet
| Tool | Keys |
|---|---|
| Downtime Cost | rev h m refund conv emp cost inc cur |
| SLA Penalty | cv up dt au pd cpd cur |
| RTO / RPO Impact | rto rpo freq rev data cur |
| Allowed Downtime | up upc pd pdc idt ipd |
| Cost of Nines | a b ac bc rev exp cur |
Always replace illustrative values with yours before a board decision. Paste the link into the incident ticket or the postmortem “Impact” section. If two teams disagree, they should disagree on an input — not on silent spreadsheet versions.
7. Common mistakes (and the fix)
- Using average revenue for a peak outage. Fix: use the same hour-of-day revenue band as the incident when you can.
-
Treating a partial outage as 100% site-down.
Fix: scale
revby the affected share of traffic or revenue. - Mixing SLA credit into business loss. Fix: two columns — credit estimate vs business impact — never one blended fantasy number.
- Assuming the next nine is the only fix. Fix: Cost of Nines shows minute budgets; architecture (multi-AZ, origin type, tested failover) often moves risk more than a marketing nine.
- Setting RTO without a drill. Fix: price the target with RTO/RPO Impact, then time the slowest restore step in a real exercise.
- Citing “official vendor losses” from illustrative links. Fix: our outages brief labels scenarios ILLUSTRATIVE. Your numbers only become yours after you edit them.
8. Open methodology
Every serious estimate needs a method you can rebuild in a spreadsheet. Our canonical explanation of allowed downtime math and related calculator formulas is:
SLA Uptime → Downtime Reference + Open Methodology
Allowed downtime (core idea):
allowed_minutes ≈ period_minutes × (1 − uptime_target/100)
Example: 30-day month ≈ 43,200 minutes. At 99.9%, downtime budget ≈ 43.2 minutes.
Honest limits we keep repeating:
- Estimates support planning; they are not legal or accounting advice.
- Contract text and monitoring evidence beat any calculator output in a credit dispute.
- We do not claim official vendor financial losses on incident briefs.
- Partial outages need a reduced revenue rate (affected share), not a fake full-site zero.
9. FAQ
What is the Reliability Money Toolkit?
The public hub for TechImpact calculators and guides that turn SLA promises, outage minutes, and RTO/RPO targets into money and time budgets a meeting can use.
Which calculator should I open first after an outage?
Downtime Cost with the real duration and a realistic revenue-per-hour rate. Then Allowed Downtime for the period budget. SLA Penalty only if a contract credit may apply.
Can I share the same scenario with my team?
Yes. Use Share Link / Copy share link on each calculator so finance, SRE, and product open the same query-string inputs.
Is an SLA credit the same as downtime cost?
No. Credits are usually capped invoice reductions. Downtime cost is your business impact. Keep two columns.
Do you claim official vendor outage losses?
No. The recent outages brief links public sources and shows illustrative scenarios for your numbers only.
10. About / contact
TechImpact.online is a free public toolkit from DynamicDisorder.co. Core calculators run in your browser; we do not need your contract numbers on our servers to compute a result.
Read who we are and how we write: About TechImpact.online. Questions, corrections, or partnership notes: Contact (contact@techimpact.online).
Prefer a full inventory of URLs? Site map. Prefer pricing / free access notes? Get started.
Practice: one page, three numbers
If you only take one habit from this hub, take this. After any meaningful incident — or before any reliability spend — write three numbers in the same document:
- Time burned (minutes) vs time allowed this period (from Allowed Downtime or calendar-month tables).
- Business impact estimate (from Downtime Cost), with inputs listed.
- Contract credit estimate (from SLA Penalty), if a vendor or customer SLA applies — kept separate from #2.
Those three lines stop most confused debates. They also make the recent outages brief useful: you can compare your modeled impact to public incident lengths without pretending the vendor’s P&L is your P&L.
When leadership asks “should we buy another nine?”, open Cost of Nines and answer with minutes and dollars, not with fear. When leadership asks “is our RTO real?”, open RTO/RPO Impact and the decision matrix, then schedule a drill for the slowest restore step.