Is Mux down?
For agents
proceed
Proceed.
GET upbutler.com/status/mux/status.agent.json
MCP: upstream_status {"service":"mux"}
Video encoding, streaming and Mux Data.
What Mux reports
Operational
Taken as is from Mux's own status page API. Incident titles and component names below are theirs.
Open status.mux.comUpButler's independent probe
There is no keyless endpoint of Mux that says anything useful, so UpButler does not probe it. To check your own Mux account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Mux components
8 operational
- Mux DashboardOperational
- Mux DocsOperational
- Mux Video - VODOperational
- Mux Video - LiveOperational
- Mux RobotsOperational
- Mux Data - Data CollectionOperational
- Mux Data - Engagement Counts APIOperational
- Mux Player - EmbedsOperational
Mux incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Mux.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Elevated API Latency | minor | 1 h | |
| Elevated errors on Direct Uploads | major | 3 h 3 min |
Tell your outage from Mux's
Declare that your project depends on Mux. When one of your monitors fails while Mux has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- muxcurl -s https://upbutler.com/status/mux/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "mux",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Mux down right now?
- No. As of 2026-10-10 05:09 UTC, Mux is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Mux's own status page API at https://status.mux.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Mux's words.
- How can my agent or app check Mux status?
- Fetch https://upbutler.com/status/mux/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"mux"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Mux's?
- Add "mux" to the dependencies of your UpButler workspace. When one of your monitors fails while Mux has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in media
UpButler is not affiliated with Mux. Status and incident text belong to Mux and are read from their public status source; the probe result is UpButler's own measurement.