Is Mux Down?

No — Mux is up

Mux's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 271 ms

Right now

The verdict is the worse of these two. How we decide

Mux's status page

status.mux.com · read 3 minutes ago · checked every 3 minutes

Operational

Mux's components, as its status page reports them
Component	Status
Mux Dashboard	Operational
Mux Docs	Operational
Mux Video - VOD	Operational
Mux Video - Live	Operational
Mux Robots	Operational
Mux Data - Data Collection	Operational
Mux Data - Engagement Counts API	Operational
Mux Player - Embeds	Operational

Open their status page

FlareWarden checks

mux.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 271 ms
Checked: 4 hours ago

By region

Ashburn reachable, 843 ms
Dallas reachable, 240 ms
Frankfurt reachable, 98 ms
Johannesburg reachable, 234 ms
London reachable, 163 ms
Los Angeles reachable, 133 ms
Newark reachable, 165 ms
São Paulo reachable, 292 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	102 ms	1 ms	9 ms	165 ms
Dallas	47 ms	0 ms	53 ms	167 ms
Frankfurt	27 ms	1 ms	7 ms	89 ms
Johannesburg	13 ms	0 ms	75 ms	159 ms
London	84 ms	2 ms	8 ms	151 ms
Los Angeles	39 ms	1 ms	21 ms	109 ms
Newark	70 ms	1 ms	19 ms	150 ms
São Paulo	196 ms	1 ms	6 ms	265 ms

We check that mux.com loads, not every feature behind it. Test it yourself

History

Incidents Mux reported

Since Oct 22, 1 day · from status.mux.com

Incidents: 2
Major or critical: 2
Median to resolve: 59m

Mux Data Collection Latency
major · Oct 21
lasted 1h 25m
Degraded VOD playback
major · Oct 21
lasted 33m

Mux website availability

Measured by FlareWarden · mux.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 279ms

Last 30 days

66-day clean streak

Sep 23 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of mux.com from multiple regions every 6 hours. Mux's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 66 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Mux does

Mux provides video infrastructure as an API: developers upload or stream to it, and it handles encoding, delivery and playback, with Mux Data measuring quality of experience. Products that embed video without running their own pipeline depend on it for both on-demand libraries and live streams, so its failures are visible to end viewers rather than to internal staff.

What an outage looks like

Players show a spinner and never start, or playback stops partway with an error. Live streams disconnect or fail to go live at the scheduled time, which is unrecoverable in a way that on-demand problems are not. Uploads finish but assets stay in a processing state. Mux Data stops collecting, so dashboards go flat without any actual drop in viewing.

What to do about it

status.mux.com separates Mux Video VOD from Live, and both from Mux Data collection, the Dashboard and Player embeds, so a live event problem is easy to tell from a library one. If a live stream is scheduled during an incident, delay it rather than starting into a degraded pipeline. Flat Mux Data numbers usually mean collection stopped, not that viewers left.

Is it down for everyone, or just you?

If this page says Mux is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Mux outage FAQ

Viewers see a spinner. Is it Mux or my player?

Test the same asset in another player or directly from its playback URL. If it also stalls, the problem is upstream in Mux; if only your embed does, look at the player configuration or the page around it. Mux lists Player embeds separately from Video VOD and Live, which helps separate the two quickly.

A live stream is scheduled during an incident. What should I do?

Delay it if the Live component is affected. A live broadcast cannot be repeated for the audience that missed it, and starting into a degraded pipeline risks a stream that drops partway rather than one that never began. Announce a new time, and check that the Live component is healthy before going ahead rather than trusting the overall banner.

My Mux Data numbers fell off a cliff. Did viewers leave?

Check data collection before drawing conclusions. Mux Data collection is its own component, and when it stops the charts flatten regardless of what viewers are doing. Playback can be entirely healthy while the measurement of it is not. Compare against another signal, such as your own application analytics, before reporting a drop in engagement.

Are on-demand videos and live streams affected together?

Frequently not. Mux Video VOD and Mux Video Live are listed as separate components and fail independently, so an existing library can play normally while live streaming is degraded, or the reverse. Match the symptom to the component before telling an audience that video is unavailable, since half of it may be working.

How we measure this

We request Mux's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Mux publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Mux itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Mux goes down

We check Mux every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required