Mux incident: Mux Data monitoring metrics incomplete/latent

Affected components

• Mux Data - Data Collection

1. resolvedSep 5, 2025, 20:08 UTC

   This incident has been resolved.

2. monitoringSep 5, 2025, 19:25 UTC

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

3. identifiedSep 5, 2025, 18:23 UTC

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

4. investigatingSep 5, 2025, 17:53 UTC

   We are continuing to investigate where in our pipeline the latency is coming from. Customers will continue to see the leading edge of monitoring data be artificially low and fill in over time.

5. investigatingSep 5, 2025, 17:20 UTC

   We are seeing intermittent drops in monitoring data starting 15:13 UTC that then fill in over time. We are currently investigating.

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.

• Vimeo: Classic Interactive DowntimeMajor · Sep 5, 2025, 12:35 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