Your CDN has good metrics.
Your end-customer still hits bad QoE.
The Streamwake reliability relay layered above the partner CDN / cloud video platform — applied to the four failure modes the partner cohort inherits: good-metrics / bad-QoE misattribution on a joint-customer cohort, regional egress affinity drift on a partner POP, cross-CDN failover brownout at the partner boundary, and OEM / reseller QoE billing-wrap gaps. Detected, classified, fixed, verified, and written up before the joint-customer support queue fills.
Four failure modes
a partner-tier cohort inherits.
The same joint-customer delivery that makes a CDN / cloud video-platform partnership the highest-margin channel on streaming also concentrates the failure modes between two dashboards that do not share a single signal. Four of them show up only on a partner-tier cohort — and each one has a known playbook the Streamwake agent owns.
Detect. Classify. Fix. Verify. Report.
The same five-act loop the Streamwake reliability agent runs on every cohort, tuned for the four pain points above — and the joint-customer, partner-border traffic they all hit on a CDN / cloud video platform partnership.
Surface the joint-customer pain as a single incident on the partner-tier cohort, regroup regional egress to a warm peer whose peering contract fits the partner policy, split the cross-CDN failover policy primary vs warm so the cohort lands warm, and tighten the OEM / reseller QoE billing-wrap so the white-label envelope holds through incident close-out — written up in Slack and Linear with a partner-tier cohort envelope before the joint-customer support queue fills.
How the loop runs on your partner cohort.
Each use case shows what the agent sees on the partner-border edge, how it ranks the hypotheses, what the fix branch looks like, how the recovery is verified, and where the write-up lands — followed by the postmortem that proves it ran in production on a partner-tier cohort.
What the agent does on a joint-customer cohort when the partner's CDN-side metrics read clean but the end-customer QoE is still red — the partner never sees the joint-customer pain on the single signal they trust.
- DetectJoint-customer cohort · CDN egress green · QoE red
The per-CDN-PoP probe pattern joins CDN egress to end-customer QoE on the joint-customer cohort and reads the egress green / QoE red split — the partner's own metrics on the partner edge do not, on their own, surface the join.
- Classifypartner_cdn_metrics_qoe_misattribution at 90%
Top hypothesis: partner_cdn_metrics_qoe_misattribution; the regional_egress_affinity_drift_partner_pop and cross_cdn_failover_brownout_partner_boundary lanes are ruled out from the per-CDN-PoP join probe.
- FixSurface the joint-customer pain as a single incident + pin the cohort
Join CDN egress to QoE on the affected cohort, surface the joint-customer pain as a single incident in the partner ops queue with the partner's metrics as one signal among several, and pin the cohort until the QoE return-to-baseline check confirms parity.
- VerifyJoint-customer QoE returns to baseline + partner metrics remain green
A joint-customer cohort probe confirms the end-customer QoE has snapped back to baseline while the partner-side CDN egress on the partner edge stays inside target; the misattribution does not migrate back to the player at the morning replay.
- ReportPostmortem in Slack + Linear (partner-tier cohort envelope)
Structured write-up with the joint-customer cohort envelope, the partner-tier cohort rate, and the agentic-act split lands in the partner channel with the joint-customer cohort flagged so the partner ops team can walk it back into the partner runbook.
What the agent does on a joint-customer cohort when a regional egress envelope drifts adjacent to a partner POP and the warm-peer reconvergence collides with the partner's BGP / peering-session policy.
- DetectRegional egress drift on a partner-adjacent POP + peering-policy collision
The probe pattern reads a regional egress envelope drift adjacent to a partner POP and pegs the warm-peer reconvergence to a peer that violates the partner's BGP / peering-session policy; cohort QoE on the affected region lags while the partner's own metrics on the partner edge read clean.
- Classifyregional_egress_affinity_drift_partner_pop at 88%
Top hypothesis: regional_egress_affinity_drift_partner_pop; the partner_cdn_metrics_qoe_misattribution lane is ruled out from the regional probe result, and the peering-policy collision is read directly off the BGP session state.
- FixRegroup to a partner-policy warm peer + pin the cohort
Regroupe regional egress to a warm peer whose contract fits the partner's peering policy on the affected joint-customer cohort, raise the regional egress-budget tolerance within the partner peering envelope, and pin the cohort until the affinity heuristic confirms parity on the partner-policy warm peer.
- VerifyRegional QoE returns to baseline on the partner-policy warm peer
A cohort-aligned regional QoE probe confirms the buffer-cliff frequency has snapped back to baseline on the joint-customer cohort using the partner-policy warm peer; the regional egress envelope inside the partner peering envelope is back inside target.
- ReportPostmortem in Slack + Linear (partner-tier cohort envelope)
Structured write-up with the regional egress envelope, the partner peering-policy state, the warm-peer regroup, and the agentic-act split lands in the partner channel with the affected joint-customer cohort and the partner peering envelope flagged.
What the agent does on a partner-tier cohort when a cross-CDN failover at the partner boundary lands cold, the warm-failover hand-off collapses on the cohort, and the partner's own warm-side metrics hide the carrier-side brownout.
- DetectCross-CDN failover brownout at partner boundary + warm-side metrics green
The probe pattern reads the partner-failover envelope at the partner boundary and sees the warm-failover hand-off collapse on the joint-customer cohort; the partner's failover metrics on the warm side read green because the warm side is not the side carrying the cohort at the failover.
- Classifycross_cdn_failover_brownout_partner_boundary at 89%
Top hypothesis: cross_cdn_failover_brownout_partner_boundary; the partner_cdn_metrics_qoe_misattribution and oem_reseller_qoe_billing_wrap_leak lanes are ruled out from the partner-failover envelope probe.
- FixRe-key cohort into the warm side + split failover policy primary vs warm
Re-key the joint-customer cohort into the warm-failover side, split the partner failover policy primary vs warm on the partner boundary, and raise the warm-side failover probe threshold so the next cross-CDN failover lands warm within the partner envelope.
- VerifyCohort recovers on the warm side + partner boundary holds inside target
A partner-tier cohort probe on the warm side confirms the joint-customer cohort has snapped back inside target and the partner boundary is reading a stable warm-side failover; the cold-side brownout does not re-trigger on the next cross-CDN failover.
- ReportPostmortem in Slack + Linear (partner-tier cohort envelope)
Structured write-up with the partner-failover envelope, the warm-side re-key, the primary-vs-warm policy split, and the agentic-act split lands in the partner channel with the affected joint-customer cohort and the partner boundary flagged.
What the agent does on a partner-tier cohort wrapped under a reseller or OEM partner brand when QoE data leaves the partner wrap without the wrap visible on the customer's invoice line — a direct miss against the partner's go-to-market wrap.
- DetectQoE envelope data leave + white-label wrap invisible on invoice
The probe pattern reads QoE-envelope state on the partner-tier cohort and sees the QoE envelope leave the partner wrap ahead of an invoice line that should carry the wrap; the data leave is invisible to the partner ops team and the customer support flow has nowhere to triage it.
- Classifyoem_reseller_qoe_billing_wrap_leak at 87%
Top hypothesis: oem_reseller_qoe_billing_wrap_leak; the cross_cdn_failover_brownout_partner_boundary and partner_cdn_metrics_qoe_misattribution lanes are ruled out from the QoE-envelope / invoice-line join probe.
- FixJoin QoE-envelope to partner billing wrap + tighten the wrap on the cohort
Join QoE-envelope state to the partner billing wrap on the partner-tier cohort, surface the white-label data leave in the partner ops queue, and tighten the wrap on the cohort so the QoE envelope data leave does not repeat on the next reseller / OEM-routed invoice line.
- VerifyWrap stays intact through close-out + invoice carries the wrap
A close-out reread of the partner-tier cohort confirms the QoE envelope and the partner billing wrap are aligned through incident close-out and the invoice line carries the wrap the partner ops team expected; the data leave does not recur on the next reseller / OEM cohort.
- ReportPostmortem in Slack + Linear (partner-tier cohort envelope)
Structured write-up with the QoE-envelope / billing-wrap join, the wrap-tightening branch, and the agentic-act split lands in the partner channel with the affected reseller / OEM cohort flagged so the partner ops team can rebuild the wrap audit trail for the next go-to-market review.
The partner surfaces
your reseller / OEM motion runs on.
The CDN / cloud video platform partner motion is supported by a set of partner surfaces that already ship in the repo. Walk the partner marketplace for third-party vendor tooling, open the Streamwake-for-streaming-partners pitch, run the walkthrough script with a sourcing counterpart, and start with the FAQ.
Medians across the current Streamwake cohort, refreshed on the quarterly streaming-reliability benchmark — the relationship to fix-branch selection holds at CDN / cloud-partner scale, with the largest effects seen when the partner-tier cohort shares POPs with the end-customer's edge infra, and every write-up includes a partner-tier cohort envelope by default.
Fewer 3 a.m. pages.
A team that sleeps.
Streamwake is in early access for CDN vendors and cloud video platforms evaluating the reliability relay above their edge — reseller, OEM, or co-sell. Run the Free Stream Check on any production partner-tier cohort, or pull up the ROI calculator to model your joint-customer incident load and MTTR curve on the partner-tier cohort. Pair it with the partner surfaces on the partner marketplace, the Streamwake-for-streaming-partners pitch, the walkthrough script, and the partner FAQ.