- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Web services
- Down Index
- 38of 100
What to do
Check whether you use api.video Web services. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 49m it lasted.
Anything that failed between 2025-12-10 10:09 UTC and 2025-12-10 10:58 UTC may need a replay.Subscribe to api.video's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=api-video works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from api.video 3
- investigating
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.
provider
- identified
The root cause has been identified, a fix is being deployed
provider
- resolved
Queue has been treated, service is back to normal. An hypervisor failure was identified has the root cause of the slowdown
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e7afdcb37c
Is api.video still down?
No, this incident was resolved 2025-12-10 10:58 UTC. For api.video's live state, see https://down.guide/api-video.
How long did it last?
49m, from 2025-12-10 10:09 UTC to 2025-12-10 10:58 UTC, by the times api.video posted.
What was affected?
api.video named Web services.
What caused it?
api.video hasn't published a root cause. If it does, it shows here.
Where does this come from?
api.video's official status page, https://status.api.video, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.