Mux incident: Elevated webhook delivery latency

Affected components

• Mux Video - Live
• Mux Video - VOD

1. resolvedSep 24, 2026, 18:21 UTC

   This incident has been resolved. Between 16:40 UTC and 17:36 UTC, webhook events were delivered with delays averaging around 5 minutes, with some events delayed up to 15 minutes. Video processing, playback, and API requests were unaffected, and no events were lost — all delayed webhooks have been delivered.The underlying issue in one of our internal database clusters has been addressed, and delivery times have been stable since 17:36 UTC. We apologize for the disruption.

2. monitoringSep 24, 2026, 17:51 UTC

   Webhook delivery times have returned to normal. Between 16:40 UTC and 17:36 UTC, webhook events were delivered with delays averaging around 5 minutes, with some events delayed up to 15 minutes. Video processing, playback, and API requests were unaffected, and no events were lost — all delayed webhooks have been delivered.We have addressed the underlying issue in one of our internal database clusters and are monitoring to confirm.

3. identifiedSep 24, 2026, 17:44 UTC

   We have identified the cause of the elevated webhook delivery times. An issue in one of our internal database clusters introduced a delay in the pipeline that queues webhook events, resulting in delivery delays beginning at 16:40 UTC. Video processing, playback, and API requests are unaffected, and no events have been lost — delayed webhooks are still being delivered. Delivery times are beginning to recover.

4. investigatingSep 24, 2026, 17:37 UTC

   We are currently investigating elevated webhook delivery times. Beginning at 16:40 UTC, some webhooks are being delivered with a delay of approximately 5 minutes. Video processing, playback, and API requests are not affected, and no webhook events are being dropped — delayed events will still be delivered. We will provide an update as soon as we have more information.

What APIStatus.watch saw

• Sep 24, 2026, 17:40 UTCoperational → degraded
• Sep 24, 2026, 18:25 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [EU-WEST-PAR][Network] - Public network incident notificationMajor · Sep 23, 2026, 14:28 UTC
• OVHcloud: [EU-WEST-PAR][Containers & Orchestration] - Managed Kubernetes Service incident notificationMajor · Sep 23, 2026, 14:57 UTC
• Supabase: Project Lifecycle Issues in eu-west-1Major · Sep 24, 2026, 15:36 UTC
• Fly.io: State database issues in GRUMajor · Sep 24, 2026, 17:11 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Mobile Puerto RicoMinor · Sep 20, 2026, 17:47 UTC
• Twilio: Voice Call Post Dial Delay from Twilio Phone Numbers to Jazz PakistanMinor · Sep 21, 2026, 06:10 UTC
• Akamai: Increased latency during upstream provider maintenance in Singapore, Hong Kong, and JapanMinor · Sep 22, 2026, 00:30 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Hugging Face: Slower downloads in the Asia-Pacific regionMinor · Sep 22, 2026, 18:48 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