Skip to main content
Mux

Mux Data Delayed Views for EU customers

Degraded Lasted 3h 8m · started · Mux's page

Level
confirmed
Worst impact
Degraded
Components
Mux Data - Data Collection
Regions
eu

What to do

  • Check whether you use Mux Mux Data - Data Collection in eu. 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 3h 8m it lasted.

    Anything that failed between 2026-04-30 00:22 UTC and 2026-04-30 03:30 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

  1. investigating

    Mux Data Views for EU customers are delayed beginning 22:53 UTC. We are investigating

    provider

  2. identified

    The issue has been identified and a fix is being implemented.

    provider

  3. monitoring

    Our pipeline latency is resolved and we are caught up as of 1:50 UTC

    provider

  4. 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-fa0163eb40

Is Mux still down?

No, this incident was resolved 2026-04-30 03:30 UTC. For Mux's live state, see https://down.guide/mux.

How long did it last?

3h 8m, from 2026-04-30 00:22 UTC to 2026-04-30 03:30 UTC, by the times Mux posted.

What was affected?

Mux named Mux Data - Data Collection in eu.

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.