Major impactResolvedMedia

Mux outage: Mux Data Collection Latency

Mux reported this major-impact incident on its official status page on Oct 21, 2026, 22:21 UTC. It was resolved after 1h 26m.

Right now Mux is operational. Live Mux status →

🔔 Get alerted when Mux has issuesFree · email alerts · no credit card
Oct 21, 2026, 22:21 UTC
started
Oct 21, 2026, 23:47 UTC
resolved
1h 26m
duration
Major
impact

Affected components

  • Mux Data - Data Collection
  1. resolvedOct 21, 2026, 23:47 UTC

    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.

  2. monitoringOct 21, 2026, 22:51 UTC

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

  3. investigatingOct 21, 2026, 22:21 UTC

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

What APIStatus.watch saw

  • Oct 21, 2026, 21:35 UTCoperational → degraded
  • Oct 21, 2026, 21:45 UTCdegraded → operational
  • Oct 21, 2026, 22:25 UTCoperational → degraded
  • Oct 21, 2026, 22:55 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Mux have incidents?

Mux reported 5 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h. See Mux's uptime and incident history