- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on LiveKit Cloud. 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-06-11 15:30 UTC and 2026-06-11 15:30 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 1
- resolved
Between 13:00 and 15:05 UTC, a subset of requests to certain Google Gemini preview models (gemini-3.1-flash-lite and gemini-3-flash-preview) routed through LiveKit Inference returned errors due to a project-level misconfiguration. These preview models did not yet have model failover configured; all other models and providers were unaffected. This was resolved by routing the traffic via an alternate provider and fixing the misconfiguration. As resolution measures, we are extending model-level failover to cover these models and adding increased monitoring for such failures in the future.
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-087c223ef0
Is LiveKit Cloud still down?
No, this incident was resolved 2026-06-11 15:30 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
0m, from 2026-06-11 15:30 UTC to 2026-06-11 15:30 UTC, by the times LiveKit Cloud posted.
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.