Mux Data CSV Exports Delayed
This incident has been resolved, export jobs are complete
The latest update from Mux.
State
Resolved
Started
76 d ago
2026-08-17 14:55 UTC
Lasted
25 h 36 min
until 2026-08-18 16:31 UTC
Worst impact
Notice
Timeline
4 updatesInvestigating
30 min 2%
Identified
25 h 6 min 98%
Updates
Times in UTCAs posted by Mux
This incident has been resolved, export jobs are complete
Export jobs are being run for the next 24 hours, beginning with 8/13. We will notify here when the jobs are complete and exports are available.
The issue has been identified and we have started the process of running delayed exports jobs.
We are investigating an issue where CSV exports are delayed beginning 8/13 to today.
Mux in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
8
Median duration
1 h
This incident
25× 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