Mux incident: Mux Data Pipeline Latency for EU Customers

Affected components

• Mux Data - Data Collection

1. resolvedApr 28, 2026, 17:33 UTC

   This incident has been resolved.

2. monitoringApr 28, 2026, 16:22 UTC

   We are monitoring for additional latency. EU saw elevated latency 15:50 UTC to 16:04 UTC. Monitoring data was inaccurate during that window and views were delayed. No data was lost.

3. investigatingApr 28, 2026, 16:05 UTC

   We are seeing some latency in both Monitoring and Historical views starting 15:53 UTC for EU customers and 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.

• 1Password: Login and Sync IssuesCritical · Apr 27, 2026, 14:54 UTC
• Elasticsearch: Missing Metrics in Cloud Console — US East (us-east-1)Major · Apr 28, 2026, 14:46 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• DigitalOcean: Elevated 5xx “context canceled” errors impacting serverless inferenceMinor · Apr 28, 2026, 13:45 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

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