Mar <var data-var='date'> 7</var>, <var data-var='time'>01:57</var> UTC Resolved - Engineers have resolved the issue with clips not having audio. Any new clips will function as expected. Impacted clips created during the incident window are not retroactively corrected, but can be re-created from the original asset.Mar <var data-var='date'> 6</var>, <var data-var='time'>22:57</var> UTC Identified - A recent encoding change caused a mismatch in initialization metadata for some clips that were created in the last 24 hours. This would affect clips of assets created before Thursday, March 6 — 15:11 UTC that utilized "basic" or "premium" video_quality. A fix is currently being worked on.

video clips audio loss

Mar <var data-var='date'> 3</var>, <var data-var='time'>08:35</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'> 3</var>, <var data-var='time'>07:55</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Latency has returned to normal.Mar <var data-var='date'> 3</var>, <var data-var='time'>07:42</var> UTC Identified - The issue has been identified and we are implementing a fix. Latency in the system is reduced, but still remains for some customers.Mar <var data-var='date'> 3</var>, <var data-var='time'>06:36</var> UTC Update - We are continuing to investigate and will post as soon as we know more.Mar <var data-var='date'> 3</var>, <var data-var='time'>05:56</var> UTC Update - We are continuing to investigate and are seeing significant latency in our collection pipeline.Mar <var data-var='date'> 3</var>, <var data-var='time'>05:29</var> UTC Investigating - We are currently investigating an issue with our Mux Data Monitoring collection pipeline. Data may be delayed or missing beginning 05:14 UTC

Mux Data Monitoring Issues

Feb <var data-var='date'>25</var>, <var data-var='time'>00:32</var> UTC Resolved - After monitoring the fix we have confirmed full resolution.Feb <var data-var='date'>24</var>, <var data-var='time'>21:08</var> UTC Monitoring - Our teams have implemented a fix to resolve the delays. At approximately 19:53 UTC, customers may have experienced delays in video ingest time and webhook delivery. We will continue to monitor the recovery and will post an update when fully resolved.Feb <var data-var='date'>24</var>, <var data-var='time'>20:37</var> UTC Identified - Our teams identified the cause of the delays and are actively working on recovery.Feb <var data-var='date'>24</var>, <var data-var='time'>20:06</var> UTC Investigating - We are currently investigating delays in video ingestion and webhook delivery. Our teams are investigating and we will share an update once we have more information.

Delayed video ingest and webhook delivery for some customers

Feb <var data-var='date'>23</var>, <var data-var='time'>15:57</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>23</var>, <var data-var='time'>14:47</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Some customers may have experienced a low number of playback failures during the incident.Feb <var data-var='date'>23</var>, <var data-var='time'>14:28</var> UTC Investigating - We are investigating an issue causing uploads to direct upload endpoints to fail for some customers. URL based ingest is not affected.

Direct upload failures and playback failures for some customers

Feb <var data-var='date'> 2</var>, <var data-var='time'>02:00</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'> 1</var>, <var data-var='time'>16:59</var> UTC Monitoring - We have completed the remediation steps for impacted assets and will be monitoring.Jan <var data-var='date'>30</var>, <var data-var='time'>18:59</var> UTC Update - A fix has been implemented to address the issue for new assets, and our team is working through any remaining affected assets. We will post further updates as we have them.Jan <var data-var='date'>29</var>, <var data-var='time'>20:40</var> UTC Identified - We have identified the cause of this issue and our team is working on a fix.Jan <var data-var='date'>29</var>, <var data-var='time'>18:07</var> UTC Investigating - We are investigating an issue that causes some audio or video segments to be corrupt, causing playback quality degradation on affected assets.

Corruption on some segments of some videos

Feb <var data-var='date'> 1</var>, <var data-var='time'>23:20</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'> 1</var>, <var data-var='time'>22:25</var> UTC Monitoring - We've taken corrective action and are monitoring the results. Tail latencies have fully recovered.Feb <var data-var='date'> 1</var>, <var data-var='time'>22:17</var> UTC Update - Elevated latency in the processing of incoming monitoring data began approximately 21:35 UTC. This impacted most customers that have access to monitoring data. Latency has starting improving, and we continue to investigate root cause.Feb <var data-var='date'> 1</var>, <var data-var='time'>21:56</var> UTC Investigating - We are investigating an issue where monitoring data is significantly delayed

Monitoring dashboard data delayed

Jan <var data-var='date'>25</var>, <var data-var='time'>13:09</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>25</var>, <var data-var='time'>12:08</var> UTC Monitoring - Our team has implemented a fix to resolve the issue and is monitoring the situation. We'll post an update as soon as the issue is fully resolved.Jan <var data-var='date'>25</var>, <var data-var='time'>10:42</var> UTC Investigating - We are currently investigating errors in Mux Data, that are impacting some customers' metric collection, beginning at approximately 0935 UTC. We apologize for the inconvenience and will share an update once we have more information.

Delayed data in Mux Data Monitoring dashboard and APIs

Jan <var data-var='date'>23</var>, <var data-var='time'>06:06</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>23</var>, <var data-var='time'>01:50</var> UTC Update - We are continuing to monitor for any further issues.Jan <var data-var='date'>23</var>, <var data-var='time'>01:34</var> UTC Monitoring - The issue has been identified and a fix has been implemented. We will continue to monitor.Jan <var data-var='date'>23</var>, <var data-var='time'>00:57</var> UTC Investigating - We're experiencing an elevated level of Livestream connection errors and are currently looking into the issue.

Elevated Livestream Errors

Jan <var data-var='date'> 9</var>, <var data-var='time'>23:57</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'> 9</var>, <var data-var='time'>23:25</var> UTC Monitoring - Our team has implemented a fix to resolve the delayed historical metrics, and is monitoring the situation. We’ll post an update as soon as the issue is fully resolved.Jan <var data-var='date'> 9</var>, <var data-var='time'>23:15</var> UTC Identified - Our team has identified a cause to delayed historical data and is actively working on a fix. We’ll continue to share updates as we have them.Jan <var data-var='date'> 9</var>, <var data-var='time'>22:51</var> UTC Investigating - We are currently investigating possible delays in Mux Data historical metrics beginning at approximately 19:55 UTC. We apologize for the inconvenience and will share an update once we have more information.

Possible Mux Data historical metrics delays

Dec <var data-var='date'> 5</var>, <var data-var='time'>02:16</var> UTC Resolved - This incident has been resolved.Dec <var data-var='date'> 5</var>, <var data-var='time'>01:15</var> UTC Monitoring - From 2025-12-05 00:07:00 UTC to 2025-12-05 00:36:00 UTC, several Mux Data servers experienced degraded connectivity. This resulted in monitoring dashboards being unable to load, beacon ingestion to slow slightly, and in some instances a small number of missing views at 00:08:50 UTC and 00:35:35 UTCDec <var data-var='date'> 5</var>, <var data-var='time'>00:46</var> UTC Update - We are continuing to investigate the cause of this issue. Customers should now see improved latency in loading the monitoring dashboard. We are assessing potential impact to our collection pipeline.Dec <var data-var='date'> 5</var>, <var data-var='time'>00:34</var> UTC Investigating - Beginning 00:07 UTC, we are seeing the monitoring page take a very long time to load and are investigating

Mux Data Monitoring Failing to Load

Dec <var data-var='date'> 2</var>, <var data-var='time'>21:06</var> UTC Resolved - This incident has been resolved.Dec <var data-var='date'> 2</var>, <var data-var='time'>18:59</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Dec <var data-var='date'> 2</var>, <var data-var='time'>18:50</var> UTC Identified - Starting around 18:17:00 UTC on December 2nd, we noticed elevated error rates for people attempting to start new live streams. Our team has identified the issue and are working on a resolution.

Elevated errors going live

Nov <var data-var='date'>20</var>, <var data-var='time'>21:26</var> UTC Resolved - This incident has been resolved.Nov <var data-var='date'>20</var>, <var data-var='time'>18:54</var> UTC Update - The team is currently deploying a fix for this issue.Nov <var data-var='date'>20</var>, <var data-var='time'>17:44</var> UTC Identified - The team have identified an issue causing an increase in error rates for image delivery, and are working on a fix.

Increase in error rates for image delivery

Nov <var data-var='date'> 5</var>, <var data-var='time'>23:47</var> UTC Resolved - In Google Chrome version 141, Google started rolling out support for native HLS in the browser. However, in this version there is a bug that can result in playback errors of all HLS content (not just Mux content), resulting in errors with error code 3, or sometimes 4. The patch for this bug has been submitted to chromium, and will likely be included in version 143 (and future versions), though that is not guaranteed at this time. The Chrome team is aware of the issue and working on releasing this fix. In the meantime, for Google Chrome we strongly suggest that you configure your player to prefer MSE-based playback rather than native HLS playback. If you're using Mux Player, be sure to update to v3.8.0 or later. If you're using some other player, you can see our implementation details to prefer MSE (including checks for Chrome and versions) here: https://github.com/muxinc/elements/pull/1221. We are resolving this incident, but will keep an eye on Chrome releases, as well as monitor for future issues.Oct <var data-var='date'>30</var>, <var data-var='time'>20:00</var> UTC 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/1221Oct <var data-var='date'>24</var>, <var data-var='time'>21:29</var> 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 <var data-var='date'>23</var>, <var data-var='time'>23:05</var> 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.htmlOct <var data-var='date'>23</var>, <var data-var='time'>18:49</var> 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 <var data-var='date'>23</var>, <var data-var='time'>14:16</var> 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.

Investigating elevated playback errors on Chrome version 141.0.7390.123 and later

Oct <var data-var='date'>31</var>, <var data-var='time'>07:59</var> UTC 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 <var data-var='date'>31</var>, <var data-var='time'>07:16</var> UTC Investigating - We are investigating networking issues resulting in Data collection issues for EU ingest customers from 6:41 UTC until 7:00 UTC.

EU Data ingest collection issues

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

Mux Player embeds increased error rates

Oct <var data-var='date'> 7</var>, <var data-var='time'>22:13</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 7</var>, <var data-var='time'>21:03</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Oct <var data-var='date'> 7</var>, <var data-var='time'>20:53</var> UTC Update - In addition to latency monitoring latency, We have identified some potential loss of view data for customers between 20:30:00 - 20:44:00 UTCOct <var data-var='date'> 7</var>, <var data-var='time'>20:47</var> UTC Identified - We are seeing latency for some customers between 20:26-20:40 UTC

Mux Data Monitoring Latency and Data Loss

Oct <var data-var='date'> 3</var>, <var data-var='time'>15:02</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 3</var>, <var data-var='time'>14:27</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Oct <var data-var='date'> 3</var>, <var data-var='time'>14:11</var> UTC Update - We are continuing to work on a fix for this issue.Oct <var data-var='date'> 3</var>, <var data-var='time'>13:24</var> UTC Identified - We have identified the issue causing an increase in errors, and are working to resolve the issue as soon as possible.Oct <var data-var='date'> 3</var>, <var data-var='time'>12:55</var> UTC Investigating - We are investigating an issue causing increased error rates for video ingest and playback for on-demand assets.

Increased error rates for video ingest and playback for on-demand assets

Oct <var data-var='date'> 2</var>, <var data-var='time'>21:04</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 2</var>, <var data-var='time'>17:06</var> UTC Monitoring - A fix has been implemented and we continue to monitor the results. Customers should see monitoring data and CCV counts return to normal.Oct <var data-var='date'> 2</var>, <var data-var='time'>16:46</var> UTC Identified - The issue has been identified and a fix is being implemented.Oct <var data-var='date'> 2</var>, <var data-var='time'>16:21</var> UTC Update - We are continuing to investigate this issue.Oct <var data-var='date'> 2</var>, <var data-var='time'>15:51</var> UTC Update - We are continuing to investigate this issue. Customers affected will see artificially depressed CCV counts and percentages.Oct <var data-var='date'> 2</var>, <var data-var='time'>15:23</var> UTC Investigating - We are investigating an issue where monitoring data is delayed for many customers

Mux Data monitoring latency

Sep <var data-var='date'>22</var>, <var data-var='time'>21:36</var> UTC Resolved - This Incident has been Resoled.Sep <var data-var='date'>22</var>, <var data-var='time'>19:25</var> UTC Update - We are continuing to monitor for any further issues.Sep <var data-var='date'>22</var>, <var data-var='time'>18:56</var> UTC Monitoring - Our team has implemented a fix to resolve the issue, and is monitoring the situation. Though we believe the issue is resolved for all users, we will be monitoring and will post an update as soon as the issue is fully resolved.Sep <var data-var='date'>22</var>, <var data-var='time'>17:40</var> UTC Identified - Error rates have improved and returning to normal. The team are continuing to investigate the root cause of this error spike. We will continue to provide updates as we have more details.Sep <var data-var='date'>22</var>, <var data-var='time'>16:44</var> UTC Investigating - The previous status update was marked resolved unintentionally. Our systems are still experiencing elevated error rates, and our team is actively investigating.

Elevated error rates for video ingest and playback for assets and live streams

Sep <var data-var='date'>22</var>, <var data-var='time'>16:38</var> UTC Resolved - This incident has been resolved.Sep <var data-var='date'>22</var>, <var data-var='time'>15:25</var> UTC Monitoring - Error rates have returned to normal, and the team are continuing to investigate and address the root cause of this error spike.Sep <var data-var='date'>22</var>, <var data-var='time'>14:54</var> UTC Investigating - The Mux engineering team are investigating.

We are investigating an issue causing increased error rates for video ingest and playback for assets and live streams

Sep <var data-var='date'>18</var>, <var data-var='time'>21:00</var> UTC Completed - The scheduled maintenance has been completed.Sep <var data-var='date'>18</var>, <var data-var='time'>20:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Sep <var data-var='date'>17</var>, <var data-var='time'>19:00</var> UTC Scheduled - In order to improve the reliability of our realtime systems, we will be undergoing scheduled maintenance. During this time, you may see inconsistent or latent data in our realtime monitoring product. This will not affect views or metrics once this window is complete

Mux Data Ingestion Pipeline Maintenance

Sep <var data-var='date'>18</var>, <var data-var='time'>19:46</var> UTC Resolved - This incident has been resolved.Sep <var data-var='date'>18</var>, <var data-var='time'>17:40</var> UTC Update - We are continuing to monitor for any further issues.Sep <var data-var='date'>18</var>, <var data-var='time'>17:23</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Sep <var data-var='date'>18</var>, <var data-var='time'>17:08</var> UTC Identified - The issue has been identified and a fix is being implemented.Sep <var data-var='date'>18</var>, <var data-var='time'>16:37</var> UTC Investigating - We are seeing increased error rates for playback and thumbnails in one of our regions. Currently investigating.

Increased errors in playback

Sep <var data-var='date'> 5</var>, <var data-var='time'>20:08</var> UTC Resolved - This incident has been resolved.Sep <var data-var='date'> 5</var>, <var data-var='time'>19:25</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Sep <var data-var='date'> 5</var>, <var data-var='time'>18:23</var> UTC Identified - The issue has been identified and a fix is being implemented.Sep <var data-var='date'> 5</var>, <var data-var='time'>17:53</var> UTC Update - We are continuing to investigate where in our pipeline the latency is coming from. Customers will continue to see the leading edge of monitoring data be artificially low and fill in over time.Sep <var data-var='date'> 5</var>, <var data-var='time'>17:20</var> UTC Investigating - We are seeing intermittent drops in monitoring data starting 15:13 UTC that then fill in over time. We are currently investigating.

Mux Data monitoring metrics incomplete/latent

Aug <var data-var='date'>19</var>, <var data-var='time'>20:03</var> UTC Resolved - This incident has been resolved.Aug <var data-var='date'>19</var>, <var data-var='time'>17:01</var> UTC Monitoring - For the issue of live streams stalling for playbacks, and the delay of creating static renditions for those assets, we have identified the root cause. Affected assets were created from live streams from 8/18 9:03 PM (UTC) to 8/19 8:29 AM (UTC). The issue has been mitigated as of 8/19 8:34 AM (UTC). We are continuing to monitor the situation and will be reaching out to impacted customers directly.Aug <var data-var='date'>19</var>, <var data-var='time'>16:14</var> UTC Investigating - We are currently investigating an issue where for some live streams, the assets generated from the live streams may stall for playbacks at the very end, and creating static renditions for those assets may be delayed

Some assets generated from live streams stalling at the end

Aug <var data-var='date'> 2</var>, <var data-var='time'>06:16</var> UTC Resolved - Our team is continuing to work with our infrastructure provider to understand the underlying cause of the transient connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time. At this point, all services are operational and operating as expectedAug <var data-var='date'> 2</var>, <var data-var='time'>03:09</var> UTC Monitoring - Our team is working with our infrastructure provider to understand the underlying cause of the connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time.Aug <var data-var='date'> 2</var>, <var data-var='time'>02:41</var> UTC Identified - We've identified the cause of the data collection errors that occurred between August 2, 2025 at 01:48:50 UTC and 02:07:50 UTC. A networking connectivity issue in the Mux Data cluster affected our data processing systems, which may result in missing or incomplete views and monitoring data during the affected period.Aug <var data-var='date'> 2</var>, <var data-var='time'>02:13</var> UTC Investigating - We are currently investigating an issue where customers may see missing data from 2025-08-02 01:48:50 UTC to 2025-08-02 02:07:5 UTC.

Is mux down?

mux status is UP

Lastest published events

video clips audio loss

Mux Data Monitoring Issues

Delayed video ingest and webhook delivery for some customers

mux Services, Components and Regions

Recent mux events

video clips audio loss

Mux Data Monitoring Issues

Delayed video ingest and webhook delivery for some customers

Direct upload failures and playback failures for some customers

Corruption on some segments of some videos

Monitoring dashboard data delayed

Get your FREE account now,
5 monitors included!

Is mux down?

mux status is UP

Lastest published events

video clips audio loss

Mux Data Monitoring Issues

Delayed video ingest and webhook delivery for some customers

mux Services, Components and Regions

Recent mux events

video clips audio loss

Mux Data Monitoring Issues

Delayed video ingest and webhook delivery for some customers

Direct upload failures and playback failures for some customers

Corruption on some segments of some videos

Monitoring dashboard data delayed

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!