High API Errors rate (09:25–09:42 UTC)

What to do

• Check whether your product depends on api.video. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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.

Root cause

Incident Summary: Between 09:25 UTC and 09:42 UTC, our API returned 500 errors due to an issue with our messaging cluster.

Updates from api.video 1

1. resolvedMar 5, 2025, 9:45 AM UTC

   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

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.