Client: StreamVista · Media, Streaming & Gaming · EU OTT streaming provider (120 staff)

Improving Playback Reliability at a Streaming Launch

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team provided reliability engineering for StreamVista’s HLS and DASH streaming launch. During the six-week reporting window, the client’s Datadog records show playback availability rising from 99.72% to 99.97%. Grafana recorded less rebuffering.

Client and engagement facts

Client
StreamVista
Industry
Media, Streaming & Gaming
Business context
EU OTT streaming provider (120 staff)
Delivery model
Streaming launch reliability engineering
Application
OTT streaming with HLS/DASH delivery
Supplied geography
EU
Company size in source
120 staff

Application stack and tools

Application stack

  • Node.js
  • HLS/DASH
  • GKE
  • GCP

Tools used

  • Datadog
  • Grafana
  • PagerDuty

Why Support Was Needed

The launch needed an escalation owner outside the day team. Engineers focused on CDN configuration, Kubernetes node-pool scaling and the runbooks for each.

Technical Work

  • Found a CDN configuration error during launch checks.
  • Identified a GKE node pool that scaled too late at peak.
  • Recorded both failure modes in the launch runbook.

Representative Incident

A CDN outage in week four affected 4% of sessions for 12 minutes. The team handled the incident under the agreed scope and recorded the impact in the launch postmortem.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSample / populationSource and scope
Playback availability99.72%99.97%%6 weeksSix-week platform playback measure; engineering coverage described here was for launch week.Client Datadog; Scope: The playback availability measure excludes the CDN outage.
Rebuffering2.1%0.6%%6 weeksClient Grafana
On-call pages/week3986 weeksClient PagerDuty

Evidence and Limitations

The playback availability measure excludes the CDN outage. Six weeks is the reporting window. The support scope documented for this engagement covers launch week.

CDN Incident Ownership

StreamVista owned the CDN contract. TechSupport Team detected incidents, performed the agreed recovery actions and documented the impact.

Scope a Similar Engagement

Share your launch window, delivery network and who controls CDN and cluster changes. Request a support plan or explore DevOps support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.