Vendor reports: operationalResolved · vendor status “resolved”Official status API

Delayed data in Mux Data Monitoring dashboard and APIs

Reported by Mux · Hosting, CDN & Edge · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Jan 25, 2026, 10:42 UTC
Vendor's clock
Resolved
Jan 25, 2026, 13:09 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 27 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Mux reports operational: "Delayed data in Mux Data Monitoring dashboard and APIs".[E1, E2]
  • The vendor marked it resolved at 2026-01-25 13:09 UTC.[E3, E7]

Affected products and regions

  • Components: Mux Dashboard, Mux Data - Data Collection.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-01-25 13:09 UTC · summary s1, evidence 348bfffa13bbfc89

Evidence (7)
  1. E1Mux reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delayed data in Mux Data Monitoring dashboard and APIs". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-01-25 10:42 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Mux Dashboard, Mux Data - Data Collection. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-01-25 13:09 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Mux Dashboard, Mux Data - Data Collection

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Mux is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jan 25, 2026, 10:42 UTCVendor-reported startVendor time
  2. Jan 25, 2026, 13:09 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.