Live / mux / Incident
mux: Mux Data Collection Latency
mux · mux.comMinor incidentResolved2026-10-21 23:47 UTC
Public — what happened
Summary
mux reported a minor incident in which its Data product was slow to collect beacons, the small data signals it receives, with the delay starting at 22:04 UTC on 2026-10-21. The company said it began investigating at 22:21 UTC and did not name a cause in the updates provided. At 22:51 UTC mux said the system had recovered at 22:28 UTC and that it was monitoring the results, and the incident was marked resolved at 23:47 UTC.
Affected
Mux Data - Data Collection
Timeline
- Started — 2026-10-21 22:21 UTC
- Investigating — 2026-10-21 22:21 UTC
- Monitoring — 2026-10-21 22:51 UTC
- Resolved — 2026-10-21 23:47 UTC · 1h 26m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach mux against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for mux: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the mux report →
More from mux
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.