outages.live
Live

Mux

Mux is operational

Checked 25 s ago Operational

History

90 days agoToday

Incidents in 90 days

7

Days with an incident

8

Median duration

1 h

Longest incident

25 h 36 min

Components

8
Mux Dashboard Operational
90 days ago1 day with an incidentToday
Mux Docs Operational
90 days agoNo incidentsToday
Mux Video - VOD Operational
90 days ago6 days with an incidentToday
Mux Video - Live Operational
90 days ago2 days with an incidentToday
Mux Robots Operational
90 days agoNo incidentsToday
Mux Data - Data Collection Operational
90 days ago2 days with an incidentToday
Mux Data - Engagement Counts API Operational
90 days agoNo incidentsToday
Mux Player - Embeds Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration1 min02:05 to 02:05Elevated Mux Video ErrorsMajor outage

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.

Oct 21, 2026

Duration1 h 26 min22:21 to 23:47Mux Data Collection LatencyPartial outage

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.

Duration34 min21:30 to 22:04Degraded VOD playbackPartial outage

This incident has been resolved.

Oct 9, 2026

Duration1 h23:04 to 00:05Elevated API LatencyDegraded

This incident has been resolved.

Oct 5, 2026

Duration3 h 3 min19:44 to 22:47Elevated errors on Direct UploadsPartial outage

This incident has been resolved.

Sep 24, 2026

Duration44 min17:37 to 18:21Elevated webhook delivery latencyDegraded

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.

Aug 17, 2026

Duration25 h 36 min14:55 to 16:31Mux Data CSV Exports DelayedNotice

This incident has been resolved, export jobs are complete

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=mux
Slack
/feed subscribe https://outages.live/feed.xml?providers=mux

Go from tracking outages to fixing production issues with Polylane.

Try Polylane