- Level
- confirmed
- Worst impact
- Major outage
- Components
- Asynchronous API, Website, Streaming API, Playground, Dashboard, LLM Gateway
- Regions
- eu
- Down Index
- 59of 100
What to do
Check whether you use AssemblyAI Asynchronous API, Website, Streaming API, Playground and 2 more in eu. 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 1h 38m it lasted.
Anything that failed between 2026-01-29 17:54 UTC and 2026-01-29 19:32 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 9
- investigating
We are currently investigating an issue affecting async + LLM gateway services. More updates to come as we learn more.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are currently investigating an issue affecting our Async and LLM Gateway services, which are returning 500 errors. Our team is actively working to identify and resolve the problem. We will provide updates as more information becomes available. All streaming API and EU endpoint services are running normally. This incident is isolated to NA API endpoints for async + LLM gateway.
provider
- investigating
We are seeing requests beginning to successfully complete and have moved to the monitoring phase. Some requests are still returning 500 errors. Our team continues to actively investigate and monitor the situation. We will provide updates as more information becomes available.
provider
- monitoring
We are seeing requests beginning to successfully complete and have moved to the monitoring phase. Some requests are still returning 500 errors. Our website is down, and logins may be affected. Our team continues to actively investigate and monitor the situation. We will provide updates as more information becomes available.
provider
- monitoring
We are continuing to see requests being completed. We are working through a backlog of requests, resulting in elevated turnaround times while we recover. Our team continues to actively monitor the situation. We will provide updates as more information becomes available.
provider
- monitoring
We are continuing to work through the backlog, and turnaround times are improving. Our team continues to actively monitor the situation. We will provide updates as more information becomes available.
provider
- resolved
We have cleared the backlog, and turnaround times are back to normal. Our team continues to actively monitor the situation. We will provide a post-mortem when available.
provider
- postmortem
**Summary: January 29 Outage** On January 29, our Async Transcription and LLM Gateway went down for 25 minutes, followed by two hours of degraded performance. Here's what happened. Our traffic has been steadily increasing and we received an influx of batch transcription jobs that were higher than usual. Autoscaling did what it should—spun up workers. We ran out of spot instances, fell back to on-demand, then hit AWS's Elastic Network Interface limit. Every ECS task needs an ENI. With no ENIs available, our authentication service couldn't rotate its tasks. It scaled to zero. Everything stopped. When we tried to recover, a Lambda function meant to help with failures was hammering the AWS API with describe calls, rate-limiting the very operations we needed to bring things back. A tool built for recovery was blocking recovery. **What actually went wrong:** We didn't monitor ENI utilization and our authentication service shared resources with batch workers. Traffic spike in one starved the other. **What we're doing:** Short-term: ENI alerts, isolate auth on dedicated capacity, fix the Lambda. Medium-term: Full multi-region for everything. This was preventable. We had the warning signs and didn't connect them. We're sorry, and we're fixing it.
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-441734d7b0
Is AssemblyAI still down?
No, this incident was resolved 2026-01-29 19:32 UTC. For AssemblyAI's live state, see https://down.guide/assemblyai.
How long did it last?
1h 38m, from 2026-01-29 17:54 UTC to 2026-01-29 19:32 UTC, by the times AssemblyAI posted.
What was affected?
AssemblyAI named Asynchronous API, Website, Streaming API, Playground and 2 more in eu.
What caused it?
AssemblyAI hasn't published a root cause. If it does, it shows here.
Where does this come from?
AssemblyAI's official status page, https://status.assemblyai.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.