Live / AssemblyAI / Incident
AssemblyAI: Real-time STT: 502 errors related to change to temporary tokens
AssemblyAI · assemblyai.comMinor incidentResolved2026-10-28 18:53 UTC
Public — what happened
Summary
AssemblyAI said that starting at 18:11 UTC on 2026-10-28, some Real-time speech-to-text sessions that relied on temporary tokens were failing with a 502 error. The company said it traced the problem to a recent change to temporary tokens and began undoing that change. By 18:21 UTC it reported the rollback was complete and errors were dropping, and it kept watching traffic to confirm rates returned to normal. The incident, which AssemblyAI rated minor, was marked resolved at 18:53.
Affected
Streaming API
Timeline
- Started — 2026-10-28 18:11 UTC
- Identified — 2026-10-28 18:11 UTC
- Monitoring — 2026-10-28 18:21 UTC
- Resolved — 2026-10-28 18:53 UTC · 42 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach AssemblyAI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for AssemblyAI: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the AssemblyAI report →
More from AssemblyAI
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.