Resolved after 1 hour 25 minutes, affecting Mux Data - Data Collection, on October 21, 2026.
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.
Affected components
Update timeline
- investigating Oct 21, 2026, 10:21 PM UTC
We are experiencing some latency in collecting beacons, beginning 22:04 UTC. Investigation is underway.
- monitoring Oct 21, 2026, 10:51 PM UTC
The system has recovered at 22:28 UTC and we are monitoring the results.
- resolved Oct 21, 2026, 11:47 PM UTC
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.
Your product runs on more than Mux
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services