- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 37of 100
What to do
Check whether your product depends on api.video. 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 0m it lasted.
Anything that failed between 2025-03-05 09:45 UTC and 2025-03-05 09:45 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 1
- resolved
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.
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-7ad1076dd5
Is api.video still down?
No, this incident was resolved 2025-03-05 09:45 UTC. For api.video's live state, see https://down.guide/api-video.
How long did it last?
0m, from 2025-03-05 09:45 UTC to 2025-03-05 09:45 UTC, by the times api.video posted.
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.