- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 1d 1h it lasted.
Anything that failed between 2026-08-17 14:55 UTC and 2026-08-18 16:31 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 CSV exports are delayed beginning 8/13 to today.
provider
- identified
The issue has been identified and we have started the process of running delayed exports jobs.
provider
- identified
Export jobs are being run for the next 24 hours, beginning with 8/13. We will notify here when the jobs are complete and exports are available.
provider
- resolved
This incident has been resolved, export jobs are complete
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-821a121fd8
Is Mux still down?
No, this incident was resolved 2026-08-18 16:31 UTC. For Mux's live state, see https://down.guide/mux.
How long did it last?
1d 1h, from 2026-08-17 14:55 UTC to 2026-08-18 16:31 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.