Client: WaveCast · Media, Streaming & Gaming · US podcast hosting platform (40 staff)

Reducing Failures in a Podcast Publishing Pipeline

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

TechSupport Team supported WaveCast’s FFmpeg and AWS podcast publishing pipeline. Over four months, client Datadog records show publishing failures falling from 27 to 4 per week. Upload-to-live time fell from 11 to 4 minutes in Jira.

Client and engagement facts

Client
WaveCast
Industry
Media, Streaming & Gaming
Business context
US podcast hosting platform (40 staff)
Delivery model
DevOps support
Application
Podcast hosting and distribution
Supplied geography
US
Company size in source
40 staff

Application stack and tools

Application stack

  • Rails
  • S3
  • FFmpeg
  • AWS

Tools used

  • Datadog
  • Jira
  • AWS storage records

Why Support Was Needed

Encoding ran serially, and an S3 bucket policy blocked uploads in one region. Engineers parallelized encoding and gave stuck uploads a retry path.

Technical Work

  • Parallelized the FFmpeg encoding pipeline across regions.
  • Fixed the S3 bucket policy in the affected region.
  • Added a retry queue for stuck uploads.

Representative Incident

An S3 regional outage interrupted uploads for 40 minutes in month two. The engineers documented the requirement for cross-region failover and implemented it in month three.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Publishing failures27/wk4/wk/wk4 monthsClient Datadog
Upload-to-live11 min4 minmin4 monthsClient Jira
Storage cost—-18%Result: %4 monthsClient AWS

Evidence and Limitations

The four-month comparison excludes one regional S3 outage. AWS storage cost is shown as a relative change, with no absolute baseline supplied.

Creator Communication During Incidents

WaveCast handled creator communication. TechSupport Team paged the on-call engineer.

Scope a Similar Engagement

Share the stages between upload and publication and where retries or failover are needed. 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.