Mux: Mux Data Collection Latency

What to do

Check whether you use Mux 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 26m it lasted.
Anything that failed between 2026-10-21 22:21 UTC and 2026-10-21 23:47 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.

investigatingOct 21, 2026, 10:21 PM UTC
We are experiencing some latency in collecting beacons, beginning 22:04 UTC. Investigation is underway.
provider
monitoringOct 21, 2026, 10:51 PM UTC
The system has recovered at 22:28 UTC and we are monitoring the results.
provider
resolvedOct 21, 2026, 11:47 PM UTC
This incident has been resolved. For a subset of customers, our ingestion pipeline was unresponsive to incoming beacons at 22:04 UTC. While our SDKs are programmed to retry, there is the potential for delayed or lost beacons at and around that time. Delayed/lost beacons would disrupt our realtime metrics and alerting. Missing beacons may also result in some missing event data for views being generated at that time.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Mux still down?

No, this incident was resolved 2026-10-21 23:47 UTC. For Mux's live state, see https://down.guide/mux.

How long did it last?

1h 26m, from 2026-10-21 22:21 UTC to 2026-10-21 23:47 UTC, by the times Mux posted.

What was affected?

Mux named 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.