AssemblyAI: Pre-recorded STT requests that include Content Moderation failing
Timeline of updates
- resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f4ba1aae79532e4a…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by AssemblyAI, started 2026-04-06 21:51 UTC, resolved after 0 min, 1 update(s).
- Title
- Pre-recorded STT requests that include Content Moderation failing
- Vendor
- AssemblyAI
- Date
- URL
- https://rewindex.com/company/assemblyai/incidents/bklzlvgkr7y5
AssemblyAI profileRecent AssemblyAI incidentsAll outages on April 6, 2026AssemblyAI in April 2026MarkdownJSON