Mux incident

Incomplete Data Collection

Major Resolved View vendor source →

Mux experienced a major incident on July 31, 2025 affecting Mux Data - Data Collection, lasting 3h 48m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2025, 07:49 PM UTC
Resolved
Jul 31, 2025, 11:38 PM UTC
Duration
3h 48m
Detected by Pingoru
Jul 31, 2025, 07:49 PM UTC

Affected components

Mux Data - Data Collection

Update timeline

  1. investigating Jul 31, 2025, 07:49 PM UTC

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

  2. investigating Jul 31, 2025, 07:50 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 31, 2025, 08:02 PM 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.

  4. identified Jul 31, 2025, 08:25 PM UTC

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

  5. monitoring Jul 31, 2025, 08:39 PM UTC

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

  6. investigating Jul 31, 2025, 08:44 PM UTC

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

  7. monitoring Jul 31, 2025, 09:17 PM 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.

  8. monitoring Jul 31, 2025, 10:51 PM UTC

    We are continuing to monitor for any further issues.

  9. resolved Jul 31, 2025, 11:38 PM UTC

    This incident has been resolved.