Mux: Data collection degraded
Timeline of updates
- resolved
From 6:30 UTC to 8:15 UTC on November 4th, Mux experienced an API availability incident that significantly impacted data collection for a subset of customers. The issue has been resolved and collection is fully operational. Impacted customers may see gaps in charts over the incident time period.
From Mux’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.mux.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Mux, started 2016-11-04 21:03 UTC, resolved after 0 min, 1 update(s).
- Title
- Data collection degraded
- Vendor
- Mux
- Date
- URL
- https://rewindex.com/company/mux/incidents/kctdcpkdsj1j
Mux profileRecent Mux incidentsAll outages on November 4, 2016Mux in November 2016MarkdownJSON