api.video had 19 outages in the last 2 years totaling 65h 27m of downtime — averaging 0.8 incidents per month.
There were 19 api.video outages since March 5, 2025 totaling 65h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.
A temporary service disruption occurred between 8h53 and 9h22 (CEST) due to an unexpected NGINX security update affecting our web server. The issue has been identified and resolved by our engineering team, and services are operating normally.
This incident has been resolved.
Our team identified an issue on April 26th at 20h UTC, that caused a slowdown in the video‑encoding pipeline. A fix has been deployed and the workers are running again, but the backlog of videos still needs to be processed. As a result, some videos may take longer than usual to become available.
The encoding queue has been fully processed and the pipeline is now operating normally. All pending videos have been cleared, and processing times have returned to the standard latency. No further delays are expected at this time.
We are currently investigating an incident affecting our Network, which is causing temporary availability issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
We're currently experiencing network issues which may impact some site functionality. An incident has been reported and our team investigating the situation
We are continuing to investigate this issue.
This incident has been resolved.
A significant portion of our service is currently unavailable. Our team is actively investigating the issue and working to identify the root cause. We will provide updates as soon as more information becomes available. Thank you for your patience while we work to restore full functionality.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Heavy traffic on our database servers caused access issues to our content delivery servers and affected the dashboard. We sincerely apologize for the outage and any inconvenience this may have caused.
A significant portion of our service is currently unavailable. Our team is actively investigating the issue and working to identify the root cause. We will provide updates as soon as more information becomes available. Thank you for your patience while we work to restore full functionality.
A network-related issue caused DNS resolution failures for some of our internal services, which affected service availability for a significant portion of users during 55 minutes. Our team identified the root cause, resolved the network/DNS issue, and services are now fully restored. We apologize for the disruption and appreciate your patience.
We are currently experiencing a significant slowdown in the processing of our customers' videos. Your content currently being processed may remain stuck in the queue. An internal investigation is underway to identify the cause of this issue. We will update this status as soon as possible.
The root cause has been identified, a fix is being deployed
Queue has been treated, service is back to normal. An hypervisor failure was identified has the root cause of the slowdown
Our video encoding pipeline is currently operating at reduced performance due to an internal processing issue. Users may see extended wait times for new video encodes.
We have identified an issue affecting a subset of our worker machines, causing reduced processing capacity and creating congestion on the remaining workers. This is resulting in longer-than-usual video encoding times. Our team is actively working on a solution to restore full capacity and improve performance
We have deployed a fix and restored additional processing capacity. Congestion in the encoding pipeline is now decreasing, and queued videos are progressing through the backlog. Please note that processing times for these previously stuck videos may still be longer than normal until the queue fully clears. Newly uploaded videos are expected to encode normally in most cases, though some minor delays may still occur during recovery. We are continuing to monitor the system closely as performance returns to normal.
This incident has been resolved.
We are currently investigating an issue related to our databases. Services impacted are the dashboard, the video upload, the delivery of private video, the live. Videos already in the CDN remains available.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Significant network instability on our LiveStream service. You may randomly encounter problems accessing or ingesting your broadcast sources. We are deploying a dedicated team to investigate and fix this situation.
Issue has been located, a fix will be deployed in a few minutes
A fix has been deployed. Nevertheless the LiveStream service performance remains behind its usual level. The team keeps monitoring the service.
The service has fully recovered. Performances have been optimal since 18:00 UTC.
We are experiencing delay on AI jobs processing (transcript, summarize). An investigation is underway.
The incident has been resolved. Pending tasks are being processed. We apologize for any inconvenience caused.
We are currently experiencing issues on our storage facility. Investigation ongoing Impacted services : - Vod Ingest - Vod delivery
Issue has been identified a fix is under test. Service is back. we will continue to monitor.
The storage has fully recover. The VOD ingest and delivery service are operational since 18:09 UTC.
We are currently experiencing delivery issues with Video On Demand (VOD) services for users located in the United States. The issue is linked to one of our third-party providers in the region. Videos that are not currently cached in our CDN may be unavailable or fail to load, while cached content remains accessible. We are actively working with our provider to resolve the problem and will provide updates as progress is made. We apologize for the inconvenience and appreciate your patience.
This incident has been resolved.
We’re currently investigating an issue affecting one of our partner and as a consequence our delivery service on US Region only. Our team is actively working to identify the cause and implement a fix as quickly as possible. We appreciate your patience and will provide updates as soon as we have more information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We’re currently investigating an issue affecting our livestream delivery service. Our team is actively working to identify the cause and implement a fix as quickly as possible. We appreciate your patience and will provide updates as soon as we have more information.
Our team has identified the root cause of the issue affecting our livestream delivery service. We are currently deploying a fix. We’ll continue to provide updates as progress is made.
The fix has been successfully deployed, and our livestream delivery service is now operating normally. We are currently monitoring the system to ensure continued stability and performance. Thank you for your patience throughout this process.
The issue affecting our livestream delivery service has been fully resolved, and all systems are now operating normally. The root cause was related to a component that encountered unexpected errors, disrupting stream processing. Our engineering team applied a fix and restored normal functionality. We’re continuing to review the incident internally to prevent similar issues in the future. Thanks!
We’re currently investigating an issue affecting our livestream delivery service. Our team is actively working to identify the cause and implement a fix as quickly as possible. We appreciate your patience and will provide updates as soon as we have more information.
We've identified the root cause of the issue. Our infrastructure team deployed a fix at 11:08 UTC, and the livestream delivery service is now operating as expected.
This incident has been resolved.
We are experiencing some issues with the delivery of some videos in the US region. Our team is doing our best to find the root cause of the problem.
Our team has identified the root cause of the issue and implemented a fix. We're currently monitoring the situation to ensure stability. We'll share more details about the incident as soon as possible.
A misconfiguration on our US-based origin servers was identified, which temporarily blocked access to some video files. The configuration has been corrected at 14:50UTC, and the system is now fully operational. We apologies for the inconvenience.
We are currently experiencing a significant degradation of our API due to a third-part provider having issue in different locations. We will provide more details as soon as possible.
Earlier today, api.video experienced a disruption in service due to a network issue affecting our infrastructure provider, Gcore. This began at approximately 10:00 GMT+2 and caused degraded performance and potential unavailability for some users. Gcore identified and resolved the root cause of the issue, and services were fully restored as of 11:09 GMT+2 (services were partially back to normal at 10:38 GMT+2) . We have been monitoring the situation closely and can confirm that the issue is now resolved. We apologize for any inconvenience this may have caused and appreciate your patience. A Root Cause Analysis (RCA) from Gcore will follow in the coming days. If you continue to experience any issues, please don’t hesitate to reach out to our support team. More details about the issue here: https://status.gcore.com Thank you for your understanding.
Incident Summary: Between 09:25 UTC and 09:42 UTC, our API returned 500 errors due to an issue with our messaging cluster. Impact: During this period, API requests failed, potentially disrupting user workflows. Root Cause: The issue was traced to a failure in our messaging cluster, which affected message processing. Resolution: Our team identified the problem and restored messaging service, bringing the API back to normal operations by 09:42 UTC. We apologize for the inconvenience.