M
Outage recap · Mux

Mux outage — November 4, 2026

On November 4, 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.

RTMP and SRT live streams disconnection

major
Started
Nov 4, 1:10 PM EST
Resolved
Nov 4, 2:21 PM EST
Duration
1h 10m

Mux's updates (3)

  1. identified · Nov 4, 1:10 PM EST

    We have experienced a small number of RTMP and SRT live streams disconnecting; most reconnected automatically within minutes. We have identified the likely cause and are working on a fix to prevent recurrence.

  2. monitoring · Nov 4, 2:09 PM EST

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

  3. resolved · Nov 4, 2:21 PM EST

    This incident has been resolved.

What our checks recorded

We checked Mux 14 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 513 ms, against 493 ms over the 24 hours before. Mux posted the incident at Nov 4, 1:10 PM EST.

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

RTMP and SRT live stream disconnects

minor
Started
Nov 4, 5:23 PM EST
Resolved
Nov 4, 8:02 PM EST
Duration
2h 39m

Mux's updates (8)

  1. investigating · Nov 4, 5:23 PM EST

    We are experiencing a small number of RTMP and SRT live streams disconnecting; most are reconnecting automatically within minutes. We have identified the likely cause and are working on a fix to prevent recurrence.

  2. identified · Nov 4, 5:24 PM EST

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

  3. identified · Nov 4, 5:52 PM EST

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

  4. identified · Nov 4, 6:25 PM EST

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

  5. identified · Nov 4, 6:38 PM EST

    We have tested a fix for this issue and working on rolling it out to production.

  6. monitoring · Nov 4, 7:49 PM EST

    A fixed was applied to production and we are monitoring the system.

  7. monitoring · Nov 4, 8:02 PM EST

    This incident has been resolved.

  8. resolved · Nov 4, 8:02 PM EST

    This incident has been resolved.

What our checks recorded

We checked Mux 32 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 460 ms, against 499 ms over the 24 hours before. Mux posted the incident at Nov 4, 5:23 PM EST.

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.