- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web services
- Down Index
- 27of 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 29m it lasted.
Anything that failed between 2026-04-27 08:33 UTC and 2026-04-27 09:02 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 2
- identified
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.
provider
- resolved
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.
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-e069bb0b9d
Is api.video still down?
No, this incident was resolved 2026-04-27 09:02 UTC. For api.video's live state, see https://down.guide/api-video.
How long did it last?
29m, from 2026-04-27 08:33 UTC to 2026-04-27 09:02 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.