Mux Outage History

Mux is up right now

Pingoru has recorded 53 incidents for Mux: 41 in the last 12 months and 6 in the last 90 days.

Source: status.mux.com

53incidents recorded
41last 12 months
6last 90 days
6 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct4
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Mux in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026622 of 720 (3%)
May 202667 of 744 (1%)
June 2026413 of 720 (2%)
July 2026660 of 744 (8%)
August 2026126 of 744 (3%)
September 202611 of 720 (0%)
October 202646 of 587 (1%)

Incidents, newest first

Minor August 19, 2025 Some assets generated from live streams stalling at the end 3h 49m Mux Video - Live

Started Aug 19, 2025, 04:14 PM UTC· resolved Aug 19, 2025, 08:03 PM UTC

  1. investigating Aug 19, 2025, 04:14 PM UTC

    We are currently investigating an issue where for some live streams, the assets generated from the live streams may stall for playbacks at the very end, and creating static renditions for those assets may be delayed

  2. monitoring Aug 19, 2025, 05:01 PM UTC

    For the issue of live streams stalling for playbacks, and the delay of creating static renditions for those assets, we have identified the root cause. Affected assets were created from live streams from 8/18 9:03 PM (UTC) to 8/19 8:29 AM (UTC). The issue has been mitigated as of 8/19 8:34 AM (UTC). We are continuing to monitor the situation and will be reaching out to impacted customers directly.

  3. resolved Aug 19, 2025, 08:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 2, 2025 Errors in Mux Data Collection 4h 3m Mux Data - Data Collection

Started Aug 02, 2025, 02:13 AM UTC· resolved Aug 02, 2025, 06:16 AM UTC

  1. investigating Aug 02, 2025, 02:13 AM UTC

    We are currently investigating an issue where customers may see missing data from 2025-08-02 01:48:50 UTC to 2025-08-02 02:07:5 UTC.

  2. identified Aug 02, 2025, 02:41 AM UTC

    We've identified the cause of the data collection errors that occurred between August 2, 2025 at 01:48:50 UTC and 02:07:50 UTC. A networking connectivity issue in the Mux Data cluster affected our data processing systems, which may result in missing or incomplete views and monitoring data during the affected period.

  3. monitoring Aug 02, 2025, 03:09 AM UTC

    Our team is working with our infrastructure provider to understand the underlying cause of the connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time.

  4. resolved Aug 02, 2025, 06:16 AM UTC

    Our team is continuing to work with our infrastructure provider to understand the underlying cause of the transient connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time. At this point, all services are operational and operating as expected

Read the full incident report →

Major August 1, 2025 Mux Data no longer reporting finalized views 1h 7m Mux Dashboard, Mux Data - Data Collection

Started Aug 01, 2025, 10:06 PM UTC· resolved Aug 01, 2025, 11:14 PM UTC

  1. investigating Aug 01, 2025, 10:06 PM UTC

    We are currently investigating an issue where views not showing up in the API or dashboard beginning 21:42:30 UTC

  2. identified Aug 01, 2025, 10:13 PM UTC

    This issue has been identified as latency in our processing pipeline. There is no data loss and a fix is being implemented.

  3. monitoring Aug 01, 2025, 10:37 PM UTC

    A fix has been implemented. Views were delayed from 2025-08-01 21:42:00 to 2025-08-01 22:06:00, and are now available in the system. Some monitoring metrics were inflated/misreported during this time.

  4. resolved Aug 01, 2025, 11:14 PM UTC

    This incident has been resolved.

Read the full incident report →