Mux: Investigating Issues with Multi-Track Audio on Newly Ingested Assets
Timeline of updates
- resolved
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.
From Mux’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.mux.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Mux, started 2025-06-14 15:00 UTC, resolved after 4.4 h, 1 update(s).
- Title
- Investigating Issues with Multi-Track Audio on Newly Ingested Assets
- Vendor
- Mux
- Date
- URL
- https://rewindex.com/company/mux/incidents/043f0486bgm4
Mux profileRecent Mux incidentsAll outages on June 14, 2025Mux in June 2025MarkdownJSON