JW Player incident

Asset and Delivery Issues

Minor Resolved View vendor source →

JW Player experienced a minor incident on June 12, 2025 affecting Dashboard and Live Channels and 1 more component, lasting 3h 20m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 06:22 PM UTC
Resolved
Jun 12, 2025, 09:43 PM UTC
Duration
3h 20m
Detected by Pingoru
Jun 12, 2025, 06:22 PM UTC

Affected components

DashboardLive ChannelsMedia Delivery

Update timeline

  1. identified Jun 12, 2025, 06:22 PM UTC

    Third party provider issue impacting Instant Live.

  2. identified Jun 12, 2025, 06:42 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jun 12, 2025, 06:48 PM UTC

    We are also seeing issues logging into the dashboard. If you are currently logged in, you will still retain access, but logging in is currently not functioning.

  4. identified Jun 12, 2025, 06:57 PM UTC

    We've mitigated the issue affecting on-demand ingest. All new on-demand ingests — including new Direct Uploads — should now function normally. Please note: Direct Uploads created before approximately 18:50 UTC may still be impacted. Live ingest remains affected, and we're continuing to work on a fix.

  5. identified Jun 12, 2025, 07:34 PM UTC

    We’re currently experiencing a service disruption that is impacting parts of our platform — particularly live ingest. While on-demand ingest has partially recovered, some features may still be degraded. Our team is actively investigating the issue and monitoring the situation closely. We’ll share updates as soon as we have more information.

  6. identified Jun 12, 2025, 07:42 PM UTC

    The issues logging in to the dashboard have been resolved, but our team continues to monitor the situation fully.

  7. identified Jun 12, 2025, 07:51 PM UTC

    We are seeing services recover, and functionality has been primarily restored across the system. Our team continues to monitor for impact and performance, and will provide updates as we have them.

  8. identified Jun 12, 2025, 07:59 PM UTC

    Our engineering teams have identified the root cause and applied targeted mitigations. The underlying dependency has recovered in most regions, with the exception of us-central1. However, we’re aware that some customers may still be experiencing varying levels of impact across specific Google Cloud products. All relevant teams are actively working to restore full service. At this time, we do not have an estimated time for complete recovery.

  9. monitoring Jun 12, 2025, 08:21 PM UTC

    All ingest and delivery services have fully recovered following the resolution of the upstream provider issue. We are actively monitoring to ensure continued stability.

  10. resolved Jun 12, 2025, 09:43 PM UTC

    This incident has been resolved.