Update - Google Chrome 142 is actively rolling out with native HLS enabled by default. However, the patch for the Chrome bug has not yet been included in this release. We will update this page as soon as we have confirmation that the bug has been fixed and is being released in a future version of Chrome.

During testing of Chrome 142, we found that the Mux Player v3.7.0 logic used to detect affected Chrome versions was not sufficient in all cases for Chrome 142.

We have released Mux Player v3.8.0, which includes improved detection for Chrome 142.

If you are using Mux Player, we strongly recommend upgrading to v3.8.0 as soon as possible. This update also allows you to remove any previously added preferPlayback or prefer-playback settings.

Updated Mux Player packages:
https://www.npmjs.com/package/@mux/mux-player
https://www.npmjs.com/package/@mux/mux-player-react

Implementation details:
https://github.com/muxinc/elements/pull/1221

Oct 30, 2025 - 20:00 UTC
Update - The Google Chrome team has identified the root cause of the playback issue and is preparing a fix. The patch is expected to be merged and released in Chrome 142, which is scheduled to land next week.

Additionally, we’ve released Mux Player v3.7.0 and Mux Player React v3.7.0, which automatically apply a graceful fallback to MSE playback for the affected Chrome version.

If you’re using Mux Player, we recommend upgrading to v3.7.0 as soon as possible. This update also allows you to remove any previously added preferPlayback or prefer-playback settings.

You can find the updated Mux Player packages at:
https://www.npmjs.com/package/@mux/mux-player
https://www.npmjs.com/package/@mux/mux-player-react

You can find details about the implementation here: https://github.com/muxinc/elements/pull/1221.

If you have any questions about upgrading your Mux Player version or encounter playback issues after updating, please reach out with details and we’re happy to help.

For users not on Mux Player, the following mitigations remain available:
• Configure your player (e.g., HLS.js) to prefer MSE playback as described in the HLS.js documentation: https://github.com/video-dev/hls.js?tab=readme-ov-file#using-hlsjs
• Alternatively, detect affected Chrome versions and selectively fall back to MSE using this reference implementation: https://codesandbox.io/p/sandbox/lntnr2?file=%2Findex.html


We’ll continue to monitor Chrome’s rollout and will update this post once the patch in Chrome 142 becomes generally available.

Oct 24, 2025 - 21:29 UTC
Update - Our team continues to work with Google to find a resolution for this issue and will provide updates as they become available.

In the meantime, if you are impacted, we recommend updating your player to prefer MSE for playback.

For customers using Mux Player, you can opt into MSE playback for affected devices by setting the preferPlayback or prefer-playback option, depending on your implementation and player version.

If you’re using another player, such as HLS.js, you should configure it similarly, as described here:
https://github.com/video-dev/hls.js?tab=readme-ov-file#using-hlsjs

If you’re unable to update your player to prefer MSE, you can use the following reference JavaScript code to detect Chrome versions with native HLS support and selectively fall back to MSE. You can view that reference implementation here:
https://codesandbox.io/p/sandbox/lntnr2?file=%2Findex.html

Oct 23, 2025 - 23:05 UTC
Identified - We have identified the issue to be specific to versions of Chrome browser at or later than 141.0.7390.123, during which Chrome has started to roll out native support for HLS to select users. For these users, playback may experience elevated error rates when native HLS playback is used. Playback through MSE (Media Source Extensions) is unaffected.

For customers using Mux Player, you can opt Mux Player into using MSE for playback for these devices by setting `preferPlayback` or `prefer-playback` depending on your use of Mux Player and the version you're on. If you're using another player, such as HLS.js, you'll want to use a similar configuration, as explained here: https://github.com/video-dev/hls.js?tab=readme-ov-file#using-hlsjs.

We are escalating the issue to Google to find a resolution to this issue, and will provide updates as we have them.

Oct 23, 2025 - 18:49 UTC
Investigating - We are currently investigating elevated playback errors affecting some viewers using the latest version of Google Chrome. Playback on other browsers and devices appears unaffected. We will provide an update as soon as more information is available.
Oct 23, 2025 - 14:16 UTC

About This Site

System Status for Mux (https://mux.com).

Mux Dashboard ? Operational
Mux Docs ? Operational
Mux Video - VOD ? Degraded Performance
Mux Video - Live ? Degraded Performance
Mux Data - Data Collection ? Operational
Mux Data - Engagement Counts API ? Operational
90 days ago
100.0 % uptime
Today
Mux Player - Embeds ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Nov 1, 2025

No incidents reported today.

Oct 31, 2025
Resolved - We have confirmed a transient issue with our cloud service provider from 6:41 UTC until 7:00 UTC for Mux Data collection in the EU. This issue has been resolved.
Oct 31, 07:59 UTC
Investigating - We are investigating networking issues resulting in Data collection issues for EU ingest customers from 6:41 UTC until 7:00 UTC.
Oct 31, 07:16 UTC
Oct 30, 2025

Unresolved incident: Investigating elevated playback errors on Chrome version 141.0.7390.123 and later.

Oct 29, 2025

No incidents reported.

Oct 28, 2025

No incidents reported.

Oct 27, 2025

No incidents reported.

Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025
Oct 23, 2025
Oct 22, 2025

No incidents reported.

Oct 21, 2025

No incidents reported.

Oct 20, 2025
Resolved - This incident has been resolved.
Oct 20, 22:04 UTC
Update - We are continuing to monitor our systems, as our underlying cloud providers continue to investigate the root cause.
Oct 20, 18:21 UTC
Update - We are continuing to monitor for any issues while the underlying cloud vendor continues to investigate the root cause.
Oct 20, 15:12 UTC
Monitoring - Recovery continues and service has returned to operational. We will continue to monitor.
Oct 20, 10:40 UTC
Update - We're seeing signs of recovery, and continue to monitor the service health.
Oct 20, 09:54 UTC
Update - We are continuing to investigate the issue.
Oct 20, 09:46 UTC
Identified - From 07:30 UTC, Mux Player embeds are were experiencing increased error rates caused by an outage with an underlying cloud vendor.
Oct 20, 09:39 UTC
Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.