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 →
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.
The system has recovered at 22:28 UTC and we are monitoring the results.
We are experiencing some latency in collecting beacons, beginning 22:04 UTC. Investigation is underway.
Overlapping incidents aren't necessarily related.
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