Mux

Affected: Mux Video - VOD

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-09 23:04 UTC

   From 22:10 to 22:50 UTC we experience elevated latency for video routes, we are currently investigating the root cause.

2. investigating 2026-10-09 23:04 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-09 23:21 UTC

   The issue has been identified and it was related to our cloud provider hosting our API. API latency has returned to normal levels, and we’re continuing to monitor stability. We apologize for the disruption.

4. resolved 2026-10-10 00:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 19:44 UTC

   We are investigating elevated error rates affecting Direct Uploads, thumbnails, gifs, subtitles, storyboards. Some customers may have experienced failures when creating or uploading to direct upload URLs

2. monitoring 2026-10-05 20:31 UTC

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

3. monitoring 2026-10-05 20:32 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-10-05 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 17:37 UTC

   We are currently investigating elevated webhook delivery times. Beginning at 16:40 UTC, some webhooks are being delivered with a delay of approximately 5 minutes. Video processing, playback, and API requests are not affected, and no webhook events are being dropped — delayed...

2. identified 2026-09-24 17:44 UTC

   We have identified the cause of the elevated webhook delivery times. An issue in one of our internal database clusters introduced a delay in the pipeline that queues webhook events, resulting in delivery delays beginning at 16:40 UTC. Video processing, playback, and API requests...

3. monitoring 2026-09-24 17:51 UTC

   Webhook delivery times have returned to normal. Between 16:40 UTC and 17:36 UTC, webhook events were delivered with delays averaging around 5 minutes, with some events delayed up to 15 minutes. Video processing, playback, and API requests were unaffected, and no events were lost...

4. resolved 2026-09-24 18:21 UTC

   This incident has been resolved. Between 16:40 UTC and 17:36 UTC, webhook events were delivered with delays averaging around 5 minutes, with some events delayed up to 15 minutes. Video processing, playback, and API requests were unaffected, and no events were lost — all delayed...

Excerpts are shortened. Read the full incident on Mux's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-17 14:55 UTC

   We are investigating an issue where CSV exports are delayed beginning 8/13 to today.

2. identified 2026-08-17 15:25 UTC

   The issue has been identified and we have started the process of running delayed exports jobs.

3. identified 2026-08-17 20:17 UTC

   Export jobs are being run for the next 24 hours, beginning with 8/13. We will notify here when the jobs are complete and exports are available.

4. resolved 2026-08-18 16:31 UTC

   This incident has been resolved, export jobs are complete

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-21 00:57 UTC

   We are currently investigating slowness in asset creation that affects limited number of assets in one of our North America cloud locations.

2. monitoring 2026-07-21 01:08 UTC

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

3. resolved 2026-07-21 01:15 UTC

   The fix resolved the issue and asset creation back to operational.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-15 19:13 UTC

   Customers may experience issues with video live and/or playback. Root cause has been identified and fix is being worked on. More updates to come as we have it.

2. monitoring 2026-07-15 21:06 UTC

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

3. monitoring 2026-07-15 21:06 UTC

   We have identified service disruption in underlying cloud infrastructure in a single availability zone, which impacted a portion of video ingestion and playback. We have routed traffic away from the affected infrastructure and are continuing to monitor while we work with the...

4. monitoring 2026-07-16 00:21 UTC

   All customer impact has been mitigated. Traffic remains directed away from the affected infrastructure while we work with our cloud provider on the underlying issue. We will remain in this state until we have fully validated the issue is resolved and we can safely restore normal...

5. resolved 2026-07-16 17:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-14 17:09 UTC

   We are investigating reports of video playback failures. Some customers may experience playback errors or timeouts.

2. identified 2026-07-14 17:13 UTC

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

3. identified 2026-07-14 17:43 UTC

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

4. monitoring 2026-07-14 18:03 UTC

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

5. resolved 2026-07-14 20:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 20:42 UTC

   We are investigating an issue affecting live streams. Some viewers may experience dropped or interrupted live streams. We will provide updates as more information becomes available.

2. investigating 2026-07-13 21:11 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-13 21:33 UTC

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

4. monitoring 2026-07-14 00:43 UTC

   A fix has been implemented and we are monitoring the situation

5. resolved 2026-07-14 08:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 17:29 UTC

   We are investigating an issue affecting live streams. Some viewers may experience dropped or interrupted live streams. Our team has identified the underlying infrastructure issue and is actively working on a resolution. We will provide updates as more information becomes...

2. identified 2026-07-08 17:43 UTC

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

3. monitoring 2026-07-08 19:57 UTC

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

4. monitoring 2026-07-08 19:57 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-07-09 14:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-01 22:35 UTC

   We are investigating an issue with collecting Mux data beacons. Beginning 22:12 UTC, view session data will be delayed.

2. monitoring 2026-07-01 22:50 UTC

   A fix has been implemented and we are monitoring results. Delayed data was for a subset of customers between 22:12 UTC - 22:44 UTC. No data loss.

3. resolved 2026-07-02 01:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-06-26 16:50 UTC

   Between 16:15 and 16:20 UTC a small number of live streams were disconnected. Active live streams were able to reconnect and resume, and there is no long term impact to DVR or VOD content from affected live streams other than resuming on a new Asset ID. All systems are currently...

2. resolved 2026-06-26 18:48 UTC

   No further issues observed during monitoring period. Live streams are operational.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-25 13:56 UTC

   We are investigating an incident which caused the disconnection of multiple live streams at 13:11 UTC.

2. resolved 2026-06-25 16:48 UTC

   A small number of live streams were disconnected around 13:10 UTC, ending the corresponding Asset. Active live streams were able to reconnect and resume, and there is no long term impact to DVR or VOD content from affected live streams other than resuming on a new Asset ID. All...

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-18 10:16 UTC

   We are experiencing increased errors with delivery across Live and VOD in Europe regions and are actively investigating.

2. identified 2026-06-18 10:57 UTC

   We've identified an issue with a CDN provider in the impacted regions. We are seeing recovery, and continuing to monitor.

3. monitoring 2026-06-18 11:31 UTC

   Video delivery for Live and VOD in the impacted region has returned to normal operations. The impacted time frame was 9:30 - 10:30 UTC. We are continuing to monitor.

4. resolved 2026-06-18 13:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 14:04 UTC

   We are investigating an issue causing an increase in errors in the Mux Data dashboard and API.

2. identified 2026-06-10 15:10 UTC

   We have identified the issue and are implementing a fix.

3. monitoring 2026-06-10 16:11 UTC

   A fix has been implemented and we are monitoring.

4. resolved 2026-06-10 18:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-19 23:56 UTC

   From 21:02 UTC to 22:55 UTC some live streams may have experienced elevated rebuffering. We have identified and mitigated the issue.

Excerpts are shortened. Read the full incident on Mux's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-14 20:31 UTC

   We are seeing high webhook delivery latency. We are actively investigating

2. monitoring 2026-05-14 20:33 UTC

   We have identified the issue and have deployed a fix. We are continuing to monitor.

3. resolved 2026-05-14 20:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-08 03:44 UTC

   From 03:08UTC to 03:14UTC we saw increased request error rates and webhook delivery latency increases. The issue is mitigated and systems are operating normally.

Excerpts are shortened. Read the full incident on Mux's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-07 22:32 UTC

   We are currently investigating errors in Mux Data historical metrics beginning at approximately 22:08 UTC. We apologize for the inconvenience and will share an update once we have more information.

2. identified 2026-05-07 22:39 UTC

   Our team has identified the cause of elevated Data Historical metrics errors and is actively working on a fix. We’ll continue to share updates as we have them.

3. monitoring 2026-05-07 23:18 UTC

   Our team has implemented a fix and we are monitoring the results. We’ll post an update as soon as the issue is fully resolved.

4. resolved 2026-05-07 23:41 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 16:36 UTC

   We are currently investigating an issue where playback may experience elevated rebuffering rates and playback failures.

2. identified 2026-05-06 16:41 UTC

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

3. monitoring 2026-05-06 17:42 UTC

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

4. resolved 2026-05-06 18:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-05 18:52 UTC

   We are currently investigating the issue

2. identified 2026-05-05 19:18 UTC

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

3. monitoring 2026-05-05 19:50 UTC

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

4. resolved 2026-05-05 20:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-30 00:22 UTC

   Mux Data Views for EU customers are delayed beginning 22:53 UTC. We are investigating

2. identified 2026-04-30 01:03 UTC

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

3. monitoring 2026-04-30 02:26 UTC

   Our pipeline latency is resolved and we are caught up as of 1:50 UTC

4. resolved 2026-04-30 03:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 16:05 UTC

   We are seeing some latency in both Monitoring and Historical views starting 15:53 UTC for EU customers and are currently investigating

2. monitoring 2026-04-28 16:22 UTC

   We are monitoring for additional latency. EU saw elevated latency 15:50 UTC to 16:04 UTC. Monitoring data was inaccurate during that window and views were delayed. No data was lost.

3. resolved 2026-04-28 17:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-27 20:08 UTC

   Small percentage of static rendition downloads. We are currently investigating this issue.

2. monitoring 2026-04-27 20:09 UTC

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

3. resolved 2026-04-28 03:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-22 18:10 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 2026-04-22 18:52 UTC

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

3. resolved 2026-04-22 19:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-21 17:36 UTC

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

2. investigating 2026-04-21 17:52 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 2026-04-21 18:14 UTC

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

4. monitoring 2026-04-21 18:20 UTC

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

5. resolved 2026-04-22 00:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 14:20 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 2026-04-09 14:27 UTC

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

3. resolved 2026-04-09 15:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-06 22:57 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...

2. resolved 2026-03-07 01:57 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.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard, Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-03 05:29 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 2026-03-03 05:56 UTC

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

3. investigating 2026-03-03 06:36 UTC

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

4. identified 2026-03-03 07:42 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 2026-03-03 07:55 UTC

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

6. resolved 2026-03-03 08:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-24 20:06 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 2026-02-24 20:37 UTC

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

3. monitoring 2026-02-24 21:08 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 2026-02-25 00:32 UTC

   After monitoring the fix we have confirmed full resolution.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-23 14:28 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 2026-02-23 14:47 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 2026-02-23 15:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard, Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-01 21:56 UTC

   We are investigating an issue where monitoring data is significantly delayed

2. investigating 2026-02-01 22:17 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 2026-02-01 22:25 UTC

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

4. resolved 2026-02-01 23:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-29 18:07 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 2026-01-29 20:40 UTC

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

3. identified 2026-01-30 18:59 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 2026-02-01 16:59 UTC

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

5. resolved 2026-02-02 02:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard, Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-25 10:42 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 2026-01-25 12:08 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 2026-01-25 13:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-23 00:57 UTC

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

2. monitoring 2026-01-23 01:34 UTC

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

3. monitoring 2026-01-23 01:50 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-01-23 06:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-09 22:51 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 2026-01-09 23:15 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 2026-01-09 23:25 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 2026-01-09 23:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-05 00:34 UTC

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

2. investigating 2025-12-05 00:46 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 2025-12-05 01:15 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...

4. resolved 2025-12-05 02:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-02 18:50 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 2025-12-02 18:59 UTC

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

3. resolved 2025-12-02 21:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-20 17:44 UTC

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

2. identified 2025-11-20 18:54 UTC

   The team is currently deploying a fix for this issue.

3. resolved 2025-11-20 21:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-31 07:16 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 2025-10-31 07:59 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.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-23 14:16 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 2025-10-23 18:49 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...

3. identified 2025-10-23 23:05 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...

4. identified 2025-10-24 21:29 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,...

5. identified 2025-10-30 20:00 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...

6. resolved 2025-11-05 23:47 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...

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Player - Embeds

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-20 09:39 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 2025-10-20 09:46 UTC

   We are continuing to investigate the issue.

3. identified 2025-10-20 09:54 UTC

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

4. monitoring 2025-10-20 10:40 UTC

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

5. monitoring 2025-10-20 15:12 UTC

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

6. monitoring 2025-10-20 18:21 UTC

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

7. resolved 2025-10-20 22:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard, Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-07 20:47 UTC

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

2. identified 2025-10-07 20:53 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 2025-10-07 21:03 UTC

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

4. resolved 2025-10-07 22:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-03 12:55 UTC

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

2. identified 2025-10-03 13:24 UTC

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

3. identified 2025-10-03 14:11 UTC

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

4. monitoring 2025-10-03 14:27 UTC

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

5. resolved 2025-10-03 15:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Dashboard, Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-02 15:23 UTC

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

2. investigating 2025-10-02 15:51 UTC

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

3. investigating 2025-10-02 16:21 UTC

   We are continuing to investigate this issue.

4. identified 2025-10-02 16:46 UTC

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

5. monitoring 2025-10-02 17:06 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 2025-10-02 21:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-22 16:44 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 2025-09-22 17:40 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 2025-09-22 18:56 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 2025-09-22 19:25 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-09-22 21:36 UTC

   This Incident has been Resoled.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-22 14:54 UTC

   The Mux engineering team are investigating.

2. monitoring 2025-09-22 15:25 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 2025-09-22 16:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - VOD, Mux Video - Live

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-18 16:37 UTC

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

2. identified 2025-09-18 17:08 UTC

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

3. monitoring 2025-09-18 17:23 UTC

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

4. monitoring 2025-09-18 17:40 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-09-18 19:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-05 17:20 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 2025-09-05 17:53 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 2025-09-05 18:23 UTC

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

4. monitoring 2025-09-05 19:25 UTC

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

5. resolved 2025-09-05 20:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Video - Live

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-19 16:14 UTC

   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

2. monitoring 2025-08-19 17:01 UTC

   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...

3. resolved 2025-08-19 20:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mux's status page.

Affected: Mux Data - Data Collection

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-02 02:13 UTC

   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.

2. identified 2025-08-02 02:41 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...

3. monitoring 2025-08-02 03:09 UTC

   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...

4. resolved 2025-08-02 06:16 UTC

   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...

Excerpts are shortened. Read the full incident on Mux's status page.