Resolved after 4 hours 3 minutes, affecting Mux Data - Data Collection, on August 2, 2025.
Our team is continuing to work with our infrastructure provider to understand the underlying cause of the transient connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time. At this point, all services are operational and operating as expected
Affected components
Update timeline
- investigating Aug 02, 2025, 02:13 AM UTC
We are currently investigating an issue where customers may see missing data from 2025-08-02 01:48:50 UTC to 2025-08-02 02:07:5 UTC.
- identified Aug 02, 2025, 02:41 AM UTC
We've identified the cause of the data collection errors that occurred between August 2, 2025 at 01:48:50 UTC and 02:07:50 UTC. A networking connectivity issue in the Mux Data cluster affected our data processing systems, which may result in missing or incomplete views and monitoring data during the affected period.
- monitoring Aug 02, 2025, 03:09 AM UTC
Our team is working with our infrastructure provider to understand the underlying cause of the connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time.
- resolved Aug 02, 2025, 06:16 AM UTC
Our team is continuing to work with our infrastructure provider to understand the underlying cause of the transient connectivity issues that affected an instance in our cluster during the impact window. This resulted in data loss for any in-flight views that were being processed on the affected instance during this time. At this point, all services are operational and operating as expected
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