Mux had 50 outages in the last 2 years totaling 418h 1m of downtime — averaging 2.1 incidents per month.
There were 50 Mux outages since May 15, 2025 totaling 418h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating networking issues resulting in Data collection issues for EU ingest customers from 6:41 UTC until 7:00 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.
From 07:30 UTC, Mux Player embeds are were experiencing increased error rates caused by an outage with an underlying cloud vendor.
We are continuing to investigate the issue.
We're seeing signs of recovery, and continue to monitor the service health.
Recovery continues and service has returned to operational. We will continue to monitor.
We are continuing to monitor for any issues while the underlying cloud vendor continues to investigate the root cause.
We are continuing to monitor our systems, as our underlying cloud providers continue to investigate the root cause.
This incident has been resolved.
We are seeing latency for some customers between 20:26-20:40 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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue causing increased error rates for video ingest and playback for on-demand assets.
We have identified the issue causing an increase in errors, and are working to resolve the issue as soon as possible.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue where monitoring data is delayed for many customers
We are continuing to investigate this issue. Customers affected will see artificially depressed CCV counts and percentages.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we continue to monitor the results. Customers should see monitoring data and CCV counts return to normal.
This incident has been resolved.
The previous status update was marked resolved unintentionally. Our systems are still experiencing elevated error rates, and our team is actively investigating.
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.
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.
We are continuing to monitor for any further issues.
This Incident has been Resoled.
The Mux engineering team are investigating.
Error rates have returned to normal, and the team are continuing to investigate and address the root cause of this error spike.
This incident has been resolved.
We are seeing increased error rates for playback and thumbnails in one of our regions. Currently investigating.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are seeing intermittent drops in monitoring data starting 15:13 UTC that then fill in over time. We are currently investigating.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
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.
This incident has been resolved.
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.
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.
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.
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 expected
We are currently investigating an issue where views not showing up in the API or dashboard beginning 21:42:30 UTC
This issue has been identified as latency in our processing pipeline. There is no data loss and a fix is being implemented.
A fix has been implemented. Views were delayed from 2025-08-01 21:42:00 to 2025-08-01 22:06:00, and are now available in the system. Some monitoring metrics were inflated/misreported during this time.
This incident has been resolved.
We are currently investigating this issue.
Currently observing degraded video delivery and elevated ingestion times.
We are continuing to investigate this issue.
Systems are recovering and we are being monitored
We are continuing to monitor for any further issues.
This incident has been resolved.
We're investigating an issue causing live health data not to appear in the live health dashboard. The processing and delivery of live streams is not affected.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating the issue.
Mux Data reported 0 views and 0 viewers for all customers between 18:46 - 19:02UTC. Select customers have been affected since July 7th 18:30UTC and continue to be affected. We are investigating the issue for those customers.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue where audio with high bit depth (24 bit audio) and mono regardless of bit depth is corrupted on ingest in some cases. We have identified the cause and are preparing a fix. We will share updates as progress is made.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
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.
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.
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.
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.
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.
We are currently experiencing a service disruption affecting Mux Data Livestream Health Stats API and Real-Time engagement metrics. The issue is related to an ongoing outage with one of our underlying infrastructure providers. Our engineering team is actively monitoring the situation and working to mitigate impact where possible. We will continue to provide updates as we learn more.
Update: We continue to see a significant portion of traffic experiencing degraded performance across Livestream Health Stats API and Real-Time Engagement Metrics (stats.mux.com). The issue remains linked to an ongoing incident with one of our infrastructure providers. We are closely monitoring the situation and will provide further updates as we receive them from the provider. Thank you for your continued patience.
As of 20:03 UTC, we are beginning to see recovery on Real-Time Engagement Metrics. We continue to see degradation on Livestream Health Stats API. Our team is continuing to monitor service restoration.
As of 20:20 UTC, we are seeing signs of recovery for the Livestream Health Stats API. Both the Livestream Health Stats API and Real-Time Engagement Metrics at stats.mux.com are now beginning to serve traffic. Our team is continuing to work closely with our infrastructure providers and will provide updates as we move towards service restoration.
Mux infrastructure providers have confirmed full recovery of services as of 20:57 UTC and our monitoring confirms that no service degradation remains at this time. Livestream Health Stats API and Real-Time Engagement Metrics at stats.mux.com are operating normally.
Beginning UTC 18:43, we are seeing incomplete data for some customers and are investigating
We are continuing to investigate this issue. CCV and other percentage metrics on the monitoring dashboard are degraded.
The issue has been identified and we are implementing a fix to stabilize.
We have a fix in place and are monitoring the system. Overall impact to data collection was between 18:43 and 19:39 UTC, with severe impact taking place between 18:43 and 19:00 UTC. Some of the data from this period will fill in, but we expect some amount of view data loss during this period.
We are continuing to monitor closely over the next hour for any issues.
This incident has been resolved.
We are currently investigating an issue where we're seeing elevated error rates delivering individual segments for HLS playback of videos. We will provide updates as we have them.
As well as increased error rates delivering segments for HLS playback for some assets, we are seeing delays in ingest for some assets as well. Our team continues to investigate all issues.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Around 16:50 UTC, Mux experienced a brief disruption due to network connectivity issues affecting some webhook events and dashboard sessions. During this period: - Some customers may have experienced delayed webhook event delivery. - Attempts to access the Mux Dashboard may have resulted in errors. - API requests to endpoints such as /video/v1/assets and /video/v1/live-streams may have intermittently failed or taken longer to complete. - Some beacon collection for Data may be interrupted, causing errors making network requests on clients. The SDKs will retry these requests, resulting in no data loss. At this time, all systems have recovered and operating normally. However, this is the third disruption of this type since ~10:50 UTC, and our team is actively working on ensuring that this does not re-occur.
There was a typo in the original message, which should have read (the key word, "not", was missing): At this time, all systems have recovered and operating normally. However, this is the third disruption of this type since ~10:50 UTC, and our team is actively working on ensuring that this does *not* re-occur.
We have narrowed down these issues to networking issues in an underlying service provider's infrastructure, and are working with them to minimize any impact. Our team continues to actively monitor the systems for any impact.
This incident has been resolved.