Mux incident: Monitoring dashboard data delayed

Affected components

• Mux Dashboard
• Mux Data - Data Collection

1. resolvedFeb 1, 2026, 23:20 UTC

   This incident has been resolved.

2. monitoringFeb 1, 2026, 22:25 UTC

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

3. investigatingFeb 1, 2026, 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.

4. investigatingFeb 1, 2026, 21:56 UTC

   We are investigating an issue where monitoring data is significantly delayed

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Mux's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• 1Password: Sign-in failure in some cases due to 2FA prompt not appearingMinor · Jan 23, 2026, 20:33 UTC

How often does Mux have incidents?

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