api.video Outage History

A slowdown in api.video's video-encoding pipeline on April 26th at 20h UTC caused delays in video processing, affecting web services for 33 minutes. The issue created a backlog that resulted in videos taking longer than usual to become available even after the initial fix was deployed. The encoding queue was fully processed and normal operations resumed on April 27th at 09:02 UTC.

A slowdown in api.video's video-encoding pipeline was identified on April 26th at 20h UTC, causing delays in video processing and availability. The issue affected web services, with a fix deployed and workers restored to normal operation. A backlog of videos remained to be processed, resulting in continued longer-than-usual processing times for some videos.

A network infrastructure malfunction caused a 2.5-hour service disruption affecting api.video's web services, video player, video on demand, user space, and live streaming components. The issue was identified and resolved through infrastructure fixes. All affected services have been restored and are being monitored.

api.video experienced network instability that impacted web services, video player, video on demand, and live streaming functionality for 26 minutes. The engineering team investigated the network issues and successfully resolved the incident. All affected services were restored to normal operation.

api.video experienced a major service outage lasting 2.1 hours that affected web services, video player, video on demand, and live streaming functionality. The incident was caused by heavy traffic on database servers, which created access issues for content delivery servers and impacted the dashboard. The service was fully restored after implementing a fix and monitoring the results.

A network-related DNS resolution issue caused a major service outage affecting api.video's web services, video on demand, user space, and live streaming components for 52 minutes. The incident impacted a significant portion of users who experienced service unavailability across these core platform features. The team identified and resolved the underlying network/DNS problem, fully restoring all services.