Mux incident: Mux Data Delayed Views for EU customers

Affected components

• Mux Data - Data Collection

1. resolvedApr 30, 2026, 03:30 UTC

   This incident has been resolved.

2. monitoringApr 30, 2026, 02:26 UTC

   Our pipeline latency is resolved and we are caught up as of 1:50 UTC

3. identifiedApr 30, 2026, 01:03 UTC

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

4. investigatingApr 30, 2026, 00:22 UTC

   Mux Data Views for EU customers are delayed beginning 22:53 UTC. We are 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.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• GitHub: Incomplete pull request results in repositoriesMinor · Apr 28, 2026, 14:17 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 UTC
• LaunchDarkly: Issue with Experiment Results in case of Flag Variation editsMinor · Apr 29, 2026, 20:19 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