Mux outage: Incomplete Data Collection

Affected components

• Mux Data - Data Collection

1. resolvedJul 31, 2025, 23:38 UTC

   This incident has been resolved.

2. monitoringJul 31, 2025, 22:51 UTC

   We are continuing to monitor for any further issues.

3. monitoringJul 31, 2025, 21:17 UTC

   The elevated latency we observed in our collection stack has been mitigated and as of 21:01 UTC we are fully recovered. We are now monitoring for additional issues.

4. investigatingJul 31, 2025, 20:44 UTC

   We are not seeing a full recovery and are investigating the cause.

5. monitoringJul 31, 2025, 20:39 UTC

   A fix has been implemented and we are monitoring the results. Impact mitigated at 20:29 UTC

6. identifiedJul 31, 2025, 20:25 UTC

   The issue has been identified and we are working on a fix. Mux Data customers are continuing to see collection degradation.

7. investigatingJul 31, 2025, 20:02 UTC

   Beginning at 19:35 UTC, customers will see reduced CCV counts and elevated failure/exit percentages in the monitoring product. Views during this time may not have complete data. We are continuing to investigate.

8. investigatingJul 31, 2025, 19:50 UTC

   We are continuing to investigate this issue.

9. investigatingJul 31, 2025, 19:49 UTC

   We are investigating an issue where many customers are not receiving all incoming beacon data

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.

• Airtable: Jira cloud rate limiting impacting larger syncsMinor · Jul 31, 2025, 17:01 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