What does one outage
actually cost your stream?

Minutes down, concurrent viewers in flight, CPM or refund rate per viewer-hour, and live vs VOD. Outputs the revenue lost per incident, viewer-impact minutes, and one framed line per Streamwake stage — what the agent would have caught at each step of the loop. The URL updates with every change so you can drop it into Slack or Linear and your teammate's browser reproduces the same view.

Open the calculator Jump to the stage lines

Live estimate

Drag the sliders. Share the URL.

One incident at a time — the math is deterministic and doesn't touch a server. Defaults match a mid-sized live broadcast; replace anything that doesn't apply. The share URL already lives in your address bar; click Copy share link in the panel below to send it to a teammate.

One incident

Tell us about the last outage.

Defaults match a mid-sized live broadcast — drag a slider, type a value, or pick a broadcast type; the URL updates with every change so you can paste it into a teammate's channel and reproduce the same result on their machine.

Minutes of downtime

min

Length of one incident from first detection to recovery.

Concurrent viewers during the incident

viewers

Audience in flight when the outage overlapped a stream.

CPM (or refund rate per viewer-hour)

$/vhr

$0.05 ≈ $50 CPM for ad-funded live. For a refund-driven VOD, set this to your platform's per-viewer-hour refund rate.

Incidents per month

/mo

Rate your team logs — annualises the per-incident figure.

Broadcast type

Live streamCPM exposure over the affected viewer-hours.

VOD playbackRefund-driven — same formula, refund rate instead of CPM.

Nothing leaves this page until you hit Copy share link.

Per-incident cost

One outage

$3,750lost per incident

Over the year at 4/mo that's $180,000 — same formula, but if you'd rather season this with more or fewer outages the slider sits at the bottom of the input column.

Estimated $ / incident$3,750

Viewer-impact minutes75,000vmin

Estimated $ / month$15,000/mo

Estimated $ / year$180,000/yr

Directional

Single-formula model — viewer-impact minutes × rate per viewer-hour. Same math for live and VOD; the radio above tells you which interpretation to apply.

What Streamwake would have caught

One line per stage.

Same agent loop the rest of the site references — Detect, Classify, Fix — reframed against the inputs you just entered.

01
Detect
Streamwake would have caught this within 30s of the encoder/edge divergence — your 15-minute window shrinks to the agent's probe latency.
02
Classify
Classified as a live stream interruption and matched to a known remediation playbook — no paged interpretation time.
03
Fix
Smallest safe action; verified recovery before the incident closes — your viewer-impact minutes flatline here.

Shareable

The URL in the address bar is the snapshot.

Every input change rewrites the URL — paste that link into Slack, Linear, or email and your teammate sees the same numbers on their machine, with their URL replaced by the same one when they tweak a value.

Current URL reflects all five inputs.

Loading inputs… (15 min · 5,000 viewers · $0.05/vhr · 4/mo · live)

One incident at a time — the math is deterministic and doesn't touch a server. Defaults match a mid-sized live broadcast.

Per-incident cost

What does one outageactually cost your stream?

Drag the sliders. Share the URL.

Tell us about the last outage.

Per-incident cost estimate

One line per stage.

The URL in the address bar is the snapshot.

Tell us about the last outage.

Per-incident cost estimate

One line per stage.

The URL in the address bar is the snapshot.

What does one outage
actually cost your stream?