- Level
- confirmed
- Worst impact
- Degraded
- Components
- Global Inference
- Down Index
- 21of 100
What to do
Check whether you use LiveKit Cloud Global Inference. 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 5h 54m it lasted.
Anything that failed between 2026-06-11 17:52 UTC and 2026-06-11 23:47 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 3
- investigating
We are currently investigating intermittent 429 errors for Google Gemini models routed through LiveKit Inference.
provider
- identified
We have identified the cause as an upstream limit on our Google Gemini API account. Automatic failover to an alternate Gemini deployment is in place and has reduced the impact, but a subset of requests to Google Gemini models may still intermittently return errors when failover capacity is exceeded. We are actively engaged with Google support to restore full capacity and will share further updates as we have them. Other models and providers remain unaffected.
provider
- resolved
This incident has been resolved. The errors were caused by an upstream issue at our model provider (Google) that incorrectly triggered an account-level usage cap on our Gemini API access, returning rate-limit errors for a subset of Gemini requests routed through LiveKit Inference. Google identified the cause, rolled back the change on their side, and raised our account limits to prevent recurrence. Gemini requests are now serving normally and error rates have returned to baseline. Other models and providers were unaffected throughout.
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-19afaf3831
Is LiveKit Cloud still down?
No, this incident was resolved 2026-06-11 23:47 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
5h 54m, from 2026-06-11 17:52 UTC to 2026-06-11 23:47 UTC, by the times LiveKit Cloud posted.
What was affected?
LiveKit Cloud named Global Inference.
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.