Mux incident

Investigating Issues with Multi-Track Audio on Newly Ingested Assets

Minor Resolved View vendor source →

Mux experienced a minor incident on June 14, 2025 affecting Mux Video - VOD, lasting 4h 24m. The incident has been resolved; the full update timeline is below.

Started
Jun 14, 2025, 03:00 PM UTC
Resolved
Jun 14, 2025, 07:25 PM UTC
Duration
4h 24m
Detected by Pingoru
Jun 14, 2025, 03:00 PM UTC

Affected components

Mux Video - VOD

Update timeline

  1. investigating Jun 14, 2025, 03:00 PM UTC

    We are currently investigating an issue affecting multi-track audio on newly ingested assets. Our engineering team is actively working to identify the root cause and will provide updates as we learn more.

  2. identified Jun 14, 2025, 03:15 PM UTC

    We’ve identified the cause of the issue affecting multi-track audio on newly ingested assets. The team is actively working on a fix and we’ll share updates as progress is made.

  3. identified Jun 14, 2025, 03:54 PM UTC

    Update: The team is actively completing a fix for the issue affecting multi-track audio on newly ingested assets. We expect to deploy the update shortly and will provide another update when we have an ETA for full resolution.

  4. identified Jun 14, 2025, 04:43 PM UTC

    Update: The team is currently rolling out a fix for the issue affecting multi-track audio on newly ingested assets. We expect the deployment to complete within the next 90 minutes. We’ll provide an update once the rollout has finished.

  5. monitoring Jun 14, 2025, 06:08 PM UTC

    The fix has been fully deployed in all regions, and we believe functionality for multi-track audio on newly ingested assets has been restored. We are continuing to monitor the system to ensure stability. Please note that impacted assets with multi-audio tracks will require deleting and re-ingesting the additional audio tracks to restore proper functionality.

  6. resolved Jun 14, 2025, 07:25 PM UTC

    The issue affecting multi-track audio on newly ingested assets has been fully resolved. All systems are operating normally. Assets that were ingested with multi-track audio between June 13 at 18:23 UTC and June 14 at 18:00 UTC are most likely to be impacted, though in certain scenarios, assets ingested prior to this window may also be affected. Impacted assets will require deleting and re-ingesting the additional audio tracks to restore proper functionality.