M
Outage recap · Mux

Mux outage — October 21, 2026

On October 21, 2026, Mux had 2 reported incidents on Mux's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded VOD playback

major
Started
Oct 21, 5:30 PM EDT
Resolved
Oct 21, 6:04 PM EDT
Duration
34 min

Mux's updates (5)

  1. investigating · Oct 21, 5:30 PM EDT

    We’ve identified an issue tha is affecting on-demand (VOD) video playback for some customers. Some viewers may see failed or slow playback. Live streaming is not affected.

  2. identified · Oct 21, 5:31 PM EDT

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

  3. monitoring · Oct 21, 5:40 PM EDT

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

  4. monitoring · Oct 21, 5:40 PM EDT

    We are continuing to monitor for any further issues.

  5. resolved · Oct 21, 6:04 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Mux 6 times from Mux's start time to its resolution, once every five minutes. Every one of them reached Mux's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 178 ms, against 112 ms over the 24 hours before. Mux posted the incident at Oct 21, 5:30 PM EDT.

Updates are Mux's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Mux Data Collection Latency

major
Started
Oct 21, 6:21 PM EDT
Resolved
Oct 21, 7:47 PM EDT
Duration
1h 26m

Mux's updates (3)

  1. investigating · Oct 21, 6:21 PM EDT

    We are experiencing some latency in collecting beacons, beginning 22:04 UTC. Investigation is underway.

  2. monitoring · Oct 21, 6:51 PM EDT

    The system has recovered at 22:28 UTC and we are monitoring the results.

  3. resolved · Oct 21, 7:47 PM EDT

    This incident has been resolved. For a subset of customers, our ingestion pipeline was unresponsive to incoming beacons at 22:04 UTC. While our SDKs are programmed to retry, there is the potential for delayed or lost beacons at and around that time. Delayed/lost beacons would disrupt our realtime metrics and alerting. Missing beacons may also result in some missing event data for views being generated at that time.

What our checks recorded

We checked Mux 17 times from Mux's start time to its resolution, once every five minutes. Every one of them reached Mux's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 102 ms, against 113 ms over the 24 hours before. Mux posted the incident at Oct 21, 6:21 PM EDT.

Updates are Mux's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Mux. This recap summarizes incidents published on Mux's official status page.