Pre-recorded STT requests that include Content Moderation failing

What to do

• Check whether your product depends on AssemblyAI. 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 2026-04-06 21:51 UTC and 2026-04-06 21:51 UTC may need a replay.

• Subscribe to AssemblyAI's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=assemblyai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from AssemblyAI 1

1. resolvedApr 6, 2026, 9:51 PM UTC

   Resolved – Content Safety Errors | April 6, 2026 Incident Window: 18:14 – 20:06 UTC Current Status: Resolved ✅ On April 6, 2026, during the incident window, customers using our Content Safety feature for Pre-recorded STT experienced errors for their requests. What happened: A configuration change inadvertently prevented our systems from processing Content Safety requests. This caused all Content Safety-enabled transcription jobs for Pre-recorded STT to fail during the affected period. Who was affected: Customers with the Content Safety feature enabled who submitted Pre-recorded STT requests between 18:14 and 20:06 UTC. What we did: Our team detected the issue and reverted the configuration change, fully restoring Content Safety functionality by 20:06 UTC. We sincerely apologize for the impact this had on your workflows. If you have any questions, please contact our team at support@assemblyai.com, and we'll be happy to assist.

   provider

Corrections

None so far.

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