LiveKit Outage History

We have not seen further instances of this issue since the mitigation was applied. We will follow up with a postmortem as soon as possible.

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.

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.

On 2026-06-11 at 13:00 UTC, a serialization bug was introduced via frontend components which rendered some services unavailable via the dashboard for some users. These services included SIP trunk and dispatch rule creation/management as well as several advanced features in Agent Builder. A fix was pushed on 2026-06-17 at 17:43 UTC which resolved the issue.

We identified a connectivity problem in the Hyderabad cluster. As mitigation, we've drained the cluster to route traffic away from it. Mumbai traffic is unaffected and serving normally. We'll undrain Hyderabad once we're confident it's functioning normally.

All missing data has now been backfilled and the incident is resolved.

We have been monitoring the clusters for the past 16 hours and have not found any further disruptions.

Between ~17:16 and 17:21 UTC on May 7, 2026, inter-region connectivity between our US East region and other regions was briefly degraded due to a network connectivity issue in our underlying cloud provider's data center. During this window, sessions that relied on cross-region track relay through US East may have experienced brief connection failures or reconnections for some participants. Our system recovered automatically once the cloud provider's data center network connectivity was restored.

We are closing this incident as we have not received further reports and the signalling error rate has dropped back to baseline. We made some fine-tuning adjustments to our stack to improve performance and will continue to seek out opportunities to keep latency low.

We have identified a bug where LiveKit Cloud projects created after April 1 at 20:41 UTC which enabled Agent Insights encountered a bug where their observability data (recordings, traces, and agent logs) was not saved correctly. We have resolved the issue on April 8 at 03:19 UTC and Agent Insights should be fully operational for all new and existing projects. No action is required from impacted users. We will follow up with a postmortem as soon as possible.

This incident has been resolved.

Real-time analytics updates on Cloud Dashboard is now fully functional, and delayed data are in the process of being backfilled.

This incident has been resolved.

Between 15:00–17:25 UTC, a subset of SIP outbound calls in the US East region experienced failures due to an internal DNS resolution issue on a single host. Approximately 1.22% of calls within the region were affected. The affected host was taken out of rotation and workloads were redistributed. Call failure rates returned to baseline following remediation.

A dependency update in our latest docs deployment caused all requests to the MCP server at docs.livekit.io/mcp/ to return 500 errors. The issue began at 18:50 UTC and ended at 19:33 UTC. During this roughly 45 minute window, MCP clients - including IDE integrations and the LiveKit CLI - were unable to connect to the docs MCP server. The issue was caused by a package upgrade that introduced dependencies incompatible with our serverless hosting environment. We rolled back the change and confirmed the endpoint was fully operational at 19:33 UTC. No other services were affected.

We experienced degraded networking affecting core real time communication services in Mumbai region. The issue began at 06:06 UTC and was resolved by 06:22 UTC on March 18, 2026. All services are now restored and we are continuing to monitor.