Elevated webhook delivery latency
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.
The latest update from Mux.
State
Resolved
Started
38 d ago
2026-09-24 17:37 UTC
Lasted
44 min
until 2026-09-24 18:21 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
8 min 17%
Identified
7 min 16%
Monitoring
30 min 67%
Updates
Times in UTCAs posted by Mux
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.
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.
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.
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.
Affected components
2Mux in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
8
Median duration
1 h
This incident
27% shorter than the median
Other Mux incidents
All incidentsMux·Elevated Mux Video Errors
This incident has been resolved. Some customers have reported on-demand assets created during or shortly after the incident window didn’t finish processing and are still showing a status of "preparing". Our team is working to get these assets processed. At this time you do not need to take any action, and we’ll post an update here as soon as they’re resolved. If this is having an urgent impact on your business, please contact us via mux.com/support or reach out to your CSM directly, and include a list of asset IDs that are impacted.
Mux·Mux Data Collection Latency
This incident has been resolved. For a subset of customers, our ingestion pipeline was unresponsive to incoming beacons at 22:04 UTC. While our SDKs are programmed to retry, there is the potential for delayed or lost beacons at and around that time. Delayed/lost beacons would disrupt our realtime metrics and alerting. Missing beacons may also result in some missing event data for views being generated at that time.
Mux·Degraded VOD playback
This incident has been resolved.
Mux·Elevated API Latency
This incident has been resolved.
Mux·Elevated errors on Direct Uploads
This incident has been resolved.
Follow Mux
Your coding agent knows when Mux is down, and tells you when a failure is theirs, not yours. You can also get Mux incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mux" and tell me if Mux has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=mux/feed subscribe https://outages.cc/feed.xml?providers=muxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane