LiveKit reported this minor-impact incident on its official status page on Aug 6, 2026, 19:51 UTC. It was resolved after 7h.
Right now LiveKit is operational. Live LiveKit status →
Today there was an issue with one of our GPU providers that caused it run at about 50% capacity. Requests above capacity return 503s, which we route to another, fallback provider. This fallback provider was not able to rise to the occasion and also returned 503s. In the very near future we will be onboarding additional providers to avoid these kinds of issues.
A burst of requests increased the failure rate. Both primary and secondary model providers failed to fulfill the requests at the time; we are root-causing the issue. We are continuing to monitor.
We are actively investigating elevated error rate on LiveKit Inference (google/gemma-4-31b-it)
Between approximately 18:45 and 19:15 UTC today, a subset of LiveKit Inference requests using the google/gemma-4-31b-it model returned errors. Affected agent sessions would have seen an LLM request error on those requests. Other models and other LiveKit services were not affected. No action is needed on your part. If you continue to see errors, please reach out to support. We apologize for the disruption.
Our 5-minute checks didn't record a change in LiveKit's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
LiveKit reported 18 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 31m. See LiveKit's uptime and incident history