- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use LiveKit Cloud in us. 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-08-26 10:44 UTC and 2026-08-26 12:22 UTC may need a replay.Subscribe to LiveKit Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=livekit works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from LiveKit Cloud 2
- investigating
We are investigating a period of elevated error rates and timeouts (08:47:00-08:53:35 UTC) for LiveKit Inference requests in our US East region. Service has since recovered and inference requests are completing normally. We are continuing to investigate the cause and confirm the full scope and duration of impact. A further update will follow.
provider
- resolved
Between 08:47 and 08:54 UTC, the service that routes LLM, STT and TTS requests through LiveKit Inference in our US East region was unavailable, causing inference requests from agents in that region to fail or time out. Sessions depending on those responses may have degraded or ended prematurely. Replacement capacity came online at 08:54 UTC and request volumes returned fully to normal levels by 09:02 UTC. We have confirmed no further impact since then. The cause was a loss of capacity during automated infrastructure maintenance. We have identified fixes to prevent a recurrence.
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-93459e4eff
Is LiveKit Cloud still down?
No, this incident was resolved 2026-08-26 12:22 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
1h 38m, from 2026-08-26 10:44 UTC to 2026-08-26 12:22 UTC, by the times LiveKit Cloud posted.
What was affected?
LiveKit Cloud named in us.
What caused it?
LiveKit Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
LiveKit Cloud's official status page, https://status.livekit.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.