- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Mux. 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 9m it lasted.
Anything that failed between 2026-05-07 22:32 UTC and 2026-05-07 23:41 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 currently investigating errors in Mux Data historical metrics beginning at approximately 22:08 UTC. We apologize for the inconvenience and will share an update once we have more information.
provider
- identified
Our team has identified the cause of elevated Data Historical metrics errors and is actively working on a fix. We’ll continue to share updates as we have them.
provider
- monitoring
Our team has implemented a fix and we are monitoring the results. We’ll post an update as soon as the issue is fully resolved.
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-e9fbda49ad
Is Mux still down?
No, this incident was resolved 2026-05-07 23:41 UTC. For Mux's live state, see https://down.guide/mux.
How long did it last?
1h 9m, from 2026-05-07 22:32 UTC to 2026-05-07 23:41 UTC, by the times Mux posted.
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.