Mux Outage History

Started Apr 22, 2026, 06:10 PM UTC· resolved Apr 22, 2026, 07:46 PM UTC

1. investigating Apr 22, 2026, 06:10 PM UTC

   We are investigating increased startup times, re-buffering, and playback errors from 429 errors on some live streams and on-demand assets.

2. monitoring Apr 22, 2026, 06:52 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 22, 2026, 07:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 21, 2026, 05:36 PM UTC· resolved Apr 22, 2026, 12:06 AM UTC

1. investigating Apr 21, 2026, 05:36 PM UTC

   We are investigating an issue causing delays in processing for some assets.

2. investigating Apr 21, 2026, 05:52 PM UTC

   We are investigating an issue causing delays in processing for some assets. Additionally, the generation of static renditions, masters, and captions may be delayed.

3. identified Apr 21, 2026, 06:14 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Apr 21, 2026, 06:20 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Apr 22, 2026, 12:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 09, 2026, 02:20 PM UTC· resolved Apr 09, 2026, 03:49 PM UTC

1. investigating Apr 09, 2026, 02:20 PM UTC

   We are currently investigating an issue where dashboard.mux.com is unavailable and may be showing an exception when loaded. All Data and Video services aside from dashboard.mux.com are unaffected.

2. monitoring Apr 09, 2026, 02:27 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 09, 2026, 03:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 06, 2026, 10:57 PM UTC· resolved Mar 07, 2026, 01:57 AM UTC

1. identified Mar 06, 2026, 10:57 PM UTC

   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.

2. resolved Mar 07, 2026, 01:57 AM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 05:29 AM UTC· resolved Mar 03, 2026, 08:35 AM UTC

1. investigating Mar 03, 2026, 05:29 AM UTC

   We are currently investigating an issue with our Mux Data Monitoring collection pipeline. Data may be delayed or missing beginning 05:14 UTC

2. investigating Mar 03, 2026, 05:56 AM UTC

   We are continuing to investigate and are seeing significant latency in our collection pipeline.

3. investigating Mar 03, 2026, 06:36 AM UTC

   We are continuing to investigate and will post as soon as we know more.

4. identified Mar 03, 2026, 07:42 AM UTC

   The issue has been identified and we are implementing a fix. Latency in the system is reduced, but still remains for some customers.

5. monitoring Mar 03, 2026, 07:55 AM UTC

   A fix has been implemented and we are monitoring the results. Latency has returned to normal.

6. resolved Mar 03, 2026, 08:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 24, 2026, 08:06 PM UTC· resolved Feb 25, 2026, 12:32 AM UTC

1. investigating Feb 24, 2026, 08:06 PM UTC

   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.

2. identified Feb 24, 2026, 08:37 PM UTC

   Our teams identified the cause of the delays and are actively working on recovery.

3. monitoring Feb 24, 2026, 09:08 PM UTC

   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.

4. resolved Feb 25, 2026, 12:32 AM UTC

   After monitoring the fix we have confirmed full resolution.

Read the full incident report →

Started Feb 23, 2026, 02:28 PM UTC· resolved Feb 23, 2026, 03:57 PM UTC

1. investigating Feb 23, 2026, 02:28 PM UTC

   We are investigating an issue causing uploads to direct upload endpoints to fail for some customers. URL based ingest is not affected.

2. monitoring Feb 23, 2026, 02:47 PM UTC

   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.

3. resolved Feb 23, 2026, 03:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 01, 2026, 09:56 PM UTC· resolved Feb 01, 2026, 11:20 PM UTC

1. investigating Feb 01, 2026, 09:56 PM UTC

   We are investigating an issue where monitoring data is significantly delayed

2. investigating Feb 01, 2026, 10:17 PM UTC

   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.

3. monitoring Feb 01, 2026, 10:25 PM UTC

   We've taken corrective action and are monitoring the results. Tail latencies have fully recovered.

4. resolved Feb 01, 2026, 11:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 29, 2026, 06:07 PM UTC· resolved Feb 02, 2026, 02:00 AM UTC

1. investigating Jan 29, 2026, 06:07 PM UTC

   We are investigating an issue that causes some audio or video segments to be corrupt, causing playback quality degradation on affected assets.

2. identified Jan 29, 2026, 08:40 PM UTC

   We have identified the cause of this issue and our team is working on a fix.

3. identified Jan 30, 2026, 06:59 PM UTC

   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.

4. monitoring Feb 01, 2026, 04:59 PM UTC

   We have completed the remediation steps for impacted assets and will be monitoring.

5. resolved Feb 02, 2026, 02:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 25, 2026, 10:42 AM UTC· resolved Jan 25, 2026, 01:09 PM UTC

1. investigating Jan 25, 2026, 10:42 AM UTC

   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.

2. monitoring Jan 25, 2026, 12:08 PM UTC

   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.

3. resolved Jan 25, 2026, 01:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 23, 2026, 12:57 AM UTC· resolved Jan 23, 2026, 06:06 AM UTC

1. investigating Jan 23, 2026, 12:57 AM UTC

   We're experiencing an elevated level of Livestream connection errors and are currently looking into the issue.

2. monitoring Jan 23, 2026, 01:34 AM UTC

   The issue has been identified and a fix has been implemented. We will continue to monitor.

3. monitoring Jan 23, 2026, 01:50 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 23, 2026, 06:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 09, 2026, 10:51 PM UTC· resolved Jan 09, 2026, 11:57 PM UTC

1. investigating Jan 09, 2026, 10:51 PM UTC

   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.

2. identified Jan 09, 2026, 11:15 PM UTC

   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.

3. monitoring Jan 09, 2026, 11:25 PM UTC

   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.

4. resolved Jan 09, 2026, 11:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 12:34 AM UTC· resolved Dec 05, 2025, 02:16 AM UTC

1. investigating Dec 05, 2025, 12:34 AM UTC

   Beginning 00:07 UTC, we are seeing the monitoring page take a very long time to load and are investigating

2. investigating Dec 05, 2025, 12:46 AM UTC

   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.

3. monitoring Dec 05, 2025, 01:15 AM UTC

   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 UTC

4. resolved Dec 05, 2025, 02:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 02, 2025, 06:50 PM UTC· resolved Dec 02, 2025, 09:06 PM UTC

1. identified Dec 02, 2025, 06:50 PM UTC

   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.

2. monitoring Dec 02, 2025, 06:59 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Dec 02, 2025, 09:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 20, 2025, 05:44 PM UTC· resolved Nov 20, 2025, 09:26 PM UTC

1. identified Nov 20, 2025, 05:44 PM UTC

   The team have identified an issue causing an increase in error rates for image delivery, and are working on a fix.

2. identified Nov 20, 2025, 06:54 PM UTC

   The team is currently deploying a fix for this issue.

3. resolved Nov 20, 2025, 09:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 31, 2025, 07:16 AM UTC· resolved Oct 31, 2025, 07:59 AM UTC

1. investigating Oct 31, 2025, 07:16 AM UTC

   We are investigating networking issues resulting in Data collection issues for EU ingest customers from 6:41 UTC until 7:00 UTC.

2. resolved Oct 31, 2025, 07:59 AM UTC

   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.

Read the full incident report →

Started Oct 23, 2025, 02:16 PM UTC· resolved Nov 05, 2025, 11:47 PM UTC

1. investigating Oct 23, 2025, 02:16 PM UTC

   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.

2. identified Oct 23, 2025, 06:49 PM UTC

   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.

3. identified Oct 23, 2025, 11:05 PM UTC

   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

4. identified Oct 24, 2025, 09:29 PM UTC

   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.

5. identified Oct 30, 2025, 08:00 PM UTC

   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

6. resolved Nov 05, 2025, 11:47 PM UTC

   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.

Read the full incident report →

Started Oct 20, 2025, 09:39 AM UTC· resolved Oct 20, 2025, 10:04 PM UTC

1. identified Oct 20, 2025, 09:39 AM UTC

   From 07:30 UTC, Mux Player embeds are were experiencing increased error rates caused by an outage with an underlying cloud vendor.

2. identified Oct 20, 2025, 09:46 AM UTC

   We are continuing to investigate the issue.

3. identified Oct 20, 2025, 09:54 AM UTC

   We're seeing signs of recovery, and continue to monitor the service health.

4. monitoring Oct 20, 2025, 10:40 AM UTC

   Recovery continues and service has returned to operational. We will continue to monitor.

5. monitoring Oct 20, 2025, 03:12 PM UTC

   We are continuing to monitor for any issues while the underlying cloud vendor continues to investigate the root cause.

6. monitoring Oct 20, 2025, 06:21 PM UTC

   We are continuing to monitor our systems, as our underlying cloud providers continue to investigate the root cause.

7. resolved Oct 20, 2025, 10:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 07, 2025, 08:47 PM UTC· resolved Oct 07, 2025, 10:13 PM UTC

1. identified Oct 07, 2025, 08:47 PM UTC

   We are seeing latency for some customers between 20:26-20:40 UTC

2. identified Oct 07, 2025, 08:53 PM UTC

   In addition to latency monitoring latency, We have identified some potential loss of view data for customers between 20:30:00 - 20:44:00 UTC

3. monitoring Oct 07, 2025, 09:03 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 07, 2025, 10:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 03, 2025, 12:55 PM UTC· resolved Oct 03, 2025, 03:02 PM UTC

1. investigating Oct 03, 2025, 12:55 PM UTC

   We are investigating an issue causing increased error rates for video ingest and playback for on-demand assets.

2. identified Oct 03, 2025, 01:24 PM UTC

   We have identified the issue causing an increase in errors, and are working to resolve the issue as soon as possible.

3. identified Oct 03, 2025, 02:11 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Oct 03, 2025, 02:27 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Oct 03, 2025, 03:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2025, 03:23 PM UTC· resolved Oct 02, 2025, 09:04 PM UTC

1. investigating Oct 02, 2025, 03:23 PM UTC

   We are investigating an issue where monitoring data is delayed for many customers

2. investigating Oct 02, 2025, 03:51 PM UTC

   We are continuing to investigate this issue. Customers affected will see artificially depressed CCV counts and percentages.

3. investigating Oct 02, 2025, 04:21 PM UTC

   We are continuing to investigate this issue.

4. identified Oct 02, 2025, 04:46 PM UTC

   The issue has been identified and a fix is being implemented.

5. monitoring Oct 02, 2025, 05:06 PM UTC

   A fix has been implemented and we continue to monitor the results. Customers should see monitoring data and CCV counts return to normal.

6. resolved Oct 02, 2025, 09:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 22, 2025, 04:44 PM UTC· resolved Sep 22, 2025, 09:36 PM UTC

1. investigating Sep 22, 2025, 04:44 PM UTC

   The previous status update was marked resolved unintentionally. Our systems are still experiencing elevated error rates, and our team is actively investigating.

2. identified Sep 22, 2025, 05:40 PM UTC

   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.

3. monitoring Sep 22, 2025, 06:56 PM UTC

   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.

4. monitoring Sep 22, 2025, 07:25 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Sep 22, 2025, 09:36 PM UTC

   This Incident has been Resoled.

Read the full incident report →

Started Sep 22, 2025, 02:54 PM UTC· resolved Sep 22, 2025, 04:38 PM UTC

1. investigating Sep 22, 2025, 02:54 PM UTC

   The Mux engineering team are investigating.

2. monitoring Sep 22, 2025, 03:25 PM UTC

   Error rates have returned to normal, and the team are continuing to investigate and address the root cause of this error spike.

3. resolved Sep 22, 2025, 04:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 18, 2025, 04:37 PM UTC· resolved Sep 18, 2025, 07:46 PM UTC

1. investigating Sep 18, 2025, 04:37 PM UTC

   We are seeing increased error rates for playback and thumbnails in one of our regions. Currently investigating.

2. identified Sep 18, 2025, 05:08 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Sep 18, 2025, 05:23 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Sep 18, 2025, 05:40 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Sep 18, 2025, 07:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 05, 2025, 05:20 PM UTC· resolved Sep 05, 2025, 08:08 PM UTC

1. investigating Sep 05, 2025, 05:20 PM UTC

   We are seeing intermittent drops in monitoring data starting 15:13 UTC that then fill in over time. We are currently investigating.

2. investigating Sep 05, 2025, 05:53 PM UTC

   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.

3. identified Sep 05, 2025, 06:23 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Sep 05, 2025, 07:25 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Sep 05, 2025, 08:08 PM UTC

   This incident has been resolved.

Read the full incident report →