- Level
- confirmed
- Worst impact
- Degraded
- Components
- Mux Dashboard, Mux Data - Data Collection
- Down Index
- 23of 100
What to do
Check whether you use Mux Mux Dashboard, Mux Data - Data Collection. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 23m it lasted.
Anything that failed between 2026-02-01 21:56 UTC and 2026-02-01 23:20 UTC may need a replay.Subscribe to Mux's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mux works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Mux 4
- investigating
We are investigating an issue where monitoring data is significantly delayed
provider
- investigating
Elevated latency in the processing of incoming monitoring data began approximately 21:35 UTC. This impacted most customers that have access to monitoring data. Latency has starting improving, and we continue to investigate root cause.
provider
- monitoring
We've taken corrective action and are monitoring the results. Tail latencies have fully recovered.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-78d44fd790
Is Mux still down?
No, this incident was resolved 2026-02-01 23:20 UTC. For Mux's live state, see https://down.guide/mux.
How long did it last?
1h 23m, from 2026-02-01 21:56 UTC to 2026-02-01 23:20 UTC, by the times Mux posted.
What was affected?
Mux named Mux Dashboard, Mux Data - Data Collection.
What caused it?
Mux hasn't published a root cause. If it does, it shows here.
Where does this come from?
Mux's official status page, https://status.mux.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.