# Mux Data Collection Latency

- Provider: [Mux](https://down.guide/providers/mux)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 1h 26m
- started 2026-10-21 22:21 UTC
- Mux Data - Data Collection
- id: DWN-fb9702ff8d
- Official page: https://stspg.io/g67z2c2rynl3

## Updates from Mux
### 2026-10-21 22:21 UTC: investigating
We are experiencing some latency in collecting beacons, beginning 22:04 UTC. Investigation is underway.

### 2026-10-21 22:51 UTC: monitoring
The system has recovered at 22:28 UTC and we are monitoring the results.

### 2026-10-21 23:47 UTC: resolved
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.

From the builder: does your app depend on Mux? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=mux) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Mux.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-fb9702ff8d), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
