- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Video On Demand
- Down Index
- 44of 100
What to do
Check whether you use api.video Video On Demand. 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 1d 2h it lasted.
Anything that failed between 2021-02-02 14:45 UTC and 2021-02-03 17:20 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
Following yesterday's incident, the delivery infrastructure is still experiencing unstable functioning today. All of our technical teams are working to resolve the problem and stabilize it as quickly as possible.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
The delivery platform has been stable for 24 hours now. Data access conflicts on the central database prior to caching on the local redis created a bottleneck and the stacking of TCP connections to provide the resource access responses. We have adapted the configuration to better manage these competitive accesses. 2ndQuadrant/EDB(the world's largest provider of PostgreSQL products and solutions) did a full Postgresql configuration review this afternoon to provide additional optimizations as well.
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-2f0b8c3d53
Is api.video still down?
No, this incident was resolved 2021-02-03 17:20 UTC. For api.video's live state, see https://down.guide/api-video.
How long did it last?
1d 2h, from 2021-02-02 14:45 UTC to 2021-02-03 17:20 UTC, by the times api.video posted.
What was affected?
api.video named Video On Demand.
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.