User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 119 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 224 ms | 0 |
| Tue 01 | 0 | 0.0 | 195 ms | 0 |
| Tue 03 | 0 | 0.0 | 97 ms | 0 |
| Tue 05 | 0 | 0.0 | 66 ms | 0 |
| Tue 08 | 0 | 0.0 | 73 ms | 0 |
| Tue 10 | 0 | 0.0 | 263 ms | 0 |
| Tue 12 | 0 | 0.0 | 80 ms | 0 |
| Tue 14 | 0 | 0.0 | 219 ms | 0 |
| Tue 16 | 0 | 0.0 | 184 ms | 0 |
| Tue 19 | 0 | 0.0 | 194 ms | 0 |
| Tue 21 | 0 | 0.0 | 156 ms | 0 |
| Tue 23 | 0 | 0.0 | 89 ms | 0 |
| Wed 01 | 0 | 0.0 | 71 ms | 0 |
| Wed 03 | 0 | 0.0 | 246 ms | 0 |
| Wed 06 | 0 | 0.0 | 73 ms | 0 |
| Wed 08 | 0 | 0.0 | 55 ms | 0 |
| Wed 10 | 0 | 0.0 | 65 ms | 0 |
| Wed 12 | 0 | 0.0 | 150 ms | 0 |
| Wed 14 | 0 | 0.0 | 80 ms | 0 |
| Wed 15 | 0 | 0.0 | 751 ms | 0 |
| Wed 17 | 0 | 0.0 | 173 ms | 0 |
| Wed 19 | 0 | 0.0 | 264 ms | 0 |
| Wed 21 | 0 | 0.0 | 150 ms | 0 |
| Wed 23 | 0 | 0.0 | 95 ms | 0 |
| Thu 01 | 0 | 0.0 | 140 ms | 0 |
| Thu 03 | 0 | 0.0 | 175 ms | 0 |
| Thu 05 | 0 | 0.0 | 86 ms | 0 |
| Thu 08 | 0 | 0.0 | 247 ms | 0 |
| Thu 10 | 0 | 0.0 | 109 ms | 0 |
| Thu 12 | 0 | 0.0 | 154 ms | 0 |
| Thu 14 | 0 | 0.0 | 117 ms | 0 |
| Thu 16 | 0 | 0.0 | 180 ms | 0 |
| Thu 18 | 0 | 0.0 | 137 ms | 0 |
| Thu 20 | 0 | 0.0 | 101 ms | 0 |
| Thu 22 | 0 | 0.0 | 95 ms | 0 |
| Thu 23 | 0 | 0.0 | 105 ms | 0 |
| Fri 01 | 0 | 0.0 | 244 ms | 0 |
| Fri 03 | 0 | 0.0 | 160 ms | 0 |
| Fri 05 | 0 | 0.0 | 191 ms | 0 |
| Fri 07 | 0 | 0.0 | 180 ms | 0 |
| Fri 09 | 0 | 0.0 | 229 ms | 0 |
| Fri 10 | 0 | 0.0 | 167 ms | 0 |
| Fri 12 | 0 | 0.0 | 119 ms | 0 |
| Fri 14 | 0 | 0.0 | 234 ms | 0 |
| Fri 16 | 0 | 0.0 | 162 ms | 0 |
| Fri 18 | 0 | 0.0 | 264 ms | 0 |
| Fri 19 | 0 | 0.0 | 245 ms | 0 |
| Fri 20 | 0 | 0.0 | 119 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Mux yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Mux goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mux alerts to Slack, Discord or a webhook — free.
Mux, at mux.com, is one of the Cloud & developer services we monitor. Mux helps teams ship high-performance and cost-effective video in minutes, not months. Build better video into anything from websites to platforms to AI workflows.
Mux publishes an official status page at status.mux.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 180 ms average, 95–264 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mux incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
180 ms on average over the last 24 hours (95–264 ms).
Yes, at https://status.mux.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Mux here at once, the problem is on Mux's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Mux. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.