Mux incident: Possible Mux Data historical metrics delays

Affected components

• Mux Data - Data Collection

1. resolvedJan 9, 2026, 23:57 UTC

   This incident has been resolved.

2. monitoringJan 9, 2026, 23:25 UTC

   Our team has implemented a fix to resolve the delayed historical metrics, and is monitoring the situation. We’ll post an update as soon as the issue is fully resolved.

3. identifiedJan 9, 2026, 23:15 UTC

   Our team has identified a cause to delayed historical data and is actively working on a fix. We’ll continue to share updates as we have them.

4. investigatingJan 9, 2026, 22:51 UTC

   We are currently investigating possible delays in Mux Data historical metrics beginning at approximately 19:55 UTC. We apologize for the inconvenience and will share an update once we have more information.

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.

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