Mux incident

Intermittent API failures and higher latency on requests and webhooks

Minor Resolved View vendor source →

Mux experienced a minor incident on May 15, 2025 affecting Mux Dashboard and Mux Video - VOD and 1 more component, lasting 22h 2m. The incident has been resolved; the full update timeline is below.

Started
May 15, 2025, 05:05 PM UTC
Resolved
May 16, 2025, 03:08 PM UTC
Duration
22h 2m
Detected by Pingoru
May 15, 2025, 05:05 PM UTC

Affected components

Mux DashboardMux Video - VODMux Data - Data Collection

Update timeline

  1. identified May 15, 2025, 05:05 PM UTC

    Around 16:50 UTC, Mux experienced a brief disruption due to network connectivity issues affecting some webhook events and dashboard sessions. During this period: - Some customers may have experienced delayed webhook event delivery. - Attempts to access the Mux Dashboard may have resulted in errors. - API requests to endpoints such as /video/v1/assets and /video/v1/live-streams may have intermittently failed or taken longer to complete. - Some beacon collection for Data may be interrupted, causing errors making network requests on clients. The SDKs will retry these requests, resulting in no data loss. At this time, all systems have recovered and operating normally. However, this is the third disruption of this type since ~10:50 UTC, and our team is actively working on ensuring that this does not re-occur.

  2. identified May 15, 2025, 05:26 PM UTC

    There was a typo in the original message, which should have read (the key word, "not", was missing): At this time, all systems have recovered and operating normally. However, this is the third disruption of this type since ~10:50 UTC, and our team is actively working on ensuring that this does *not* re-occur.

  3. monitoring May 15, 2025, 07:24 PM UTC

    We have narrowed down these issues to networking issues in an underlying service provider's infrastructure, and are working with them to minimize any impact. Our team continues to actively monitor the systems for any impact.

  4. resolved May 16, 2025, 03:08 PM UTC

    This incident has been resolved.