Is LiveKit down right now?

LiveKit uptime, last 90 days

Each bar is one UTC day, coloured by the worst state we saw on the official status page.

Recent LiveKit incidents

• Disconnections and failed connections in multiple regions · 31 Oct 2026, 07:43 UTC · minor

  postmortem · 3 Nov 2026, 13:54 UTC

  **Summary** On October 31, 2026, between 07:10 and 07:43 UTC, an uncommon data pattern surfaced a latent software bug which caused media servers in several regions to restart repeatedly. A small percentage of participants were disconnected and the vast majority automatically reconnected. Impact was concentrated in North America. We stopped the trigger at 07:43 UTC and deployed a fix to all regions by 08:49 UTC. We apologize for the disruption this caused. **Root Cause** Applications can open their own data channel and send raw data over it, outside of LiveKit's standard data message format. Media servers forward this raw data to other participants in the room, wrapping it with the sender's identity so that receivers know who sent it. When a room spans multiple regions, the media server…

  resolved · 31 Oct 2026, 07:43 UTC

  This incident has been resolved. Between 07:10 and 07:43 UTC on October 31, a software bug caused media servers in several regions to restart repeatedly. During this window: - Participants connected to affected servers were disconnected. Impact was heaviest in US East, US Central, US West, Canada and Mexico, where about 18% of participants were disconnected at least once. Many were disconnected more than once, as automatic reconnects landed on servers that then restarted as well. A small share of participants in Europe Central, Europe South, UAE, Saudi Arabia and Israel were also disconnected. Most disconnected participants reconnected automatically, about half within 5 seconds, but each reconnect started a new session rather than resuming the existing one, so participants may have seen…

  Read on status.livekit.io

• Investigating failing calls and RoomService API failures in US East and dashboard issues · 28 Oct 2026, 23:47 UTC · 1 h 32 min · minor

  postmortem · 1 Nov 2026, 15:41 UTC

  ## Summary On October 28, 2026, a network disruption at our cloud provider affected our US East data center. Starting at 23:28 UTC, services in US East lost the ability to reach our database and certain external services, such as model providers. Connections to end users and to our other regions kept working, so realtime media continued to flow. This caused widespread failures across SIP calls, Room Service, Egress and Ingress APIs, and Cloud Agents in US East. A related issue affected our Mexico region for longer. Connectivity in US East came back at around 23:58 UTC. Mexico recovered at 01:01 UTC after we moved its traffic to nearby regions. Our automatic failover should have moved traffic away from US East, and it didn't. That's the main thing we're fixing. We sincerely apologize to…

  resolved · 29 Oct 2026, 01:19 UTC

  This incident has been resolved. Between 23:30 and 23:58 UTC, a network disruption at an upstream infrastructure provider affected our US East region. During this window: Inbound SIP calls in US East failed at elevated rates, with affected calls rejected with 500 or 503 responses. Answered inbound calls were about 65% below normal across the window, and up to 90% below normal between 23:45 and 23:55 UTC. About 10% of outbound SIP call requests (CreateSIPParticipant) in US East failed, some returning 408 deadline_exceeded. Between 23:28 and 23:58 UTC, there were elevated rates of Room Service, Egress, and Ingress API request server errors in US East. Some participants saw failed room joins or increased packet loss. The LiveKit Cloud dashboard was inaccessible for part of this window. Ne…

  monitoring · 29 Oct 2026, 00:41 UTC

  We've applied a mitigation for our Mexico region and services have returned to baseline. We are continuing to monitor and will update again within 15 minutes.

  identified · 29 Oct 2026, 00:36 UTC

  While the US regions still appear to be stable, we are tracking degraded services including SIP, RTC, and APIs in our Mexico region. We will update again as soon as possible.

  monitoring · 29 Oct 2026, 00:16 UTC

  We believe the mitigation was successful and are seeing services return to normal. The dashboard is accessible and error rates have gone down across services. We are continuing to monitor to make sure that the situation is resolved. We will update again as soon as possible.

  investigating · 29 Oct 2026, 00:09 UTC

  We are still determining the full scope of impact, but we believe that the Room Service has also been impacted. We will update again within 15 minutes.

  investigating · 29 Oct 2026, 00:00 UTC

  We are currently attempting a mitigation. We will follow up with more information in the next 15 minutes.

  investigating · 28 Oct 2026, 23:57 UTC

  We believe there is also impact to inbound calls in the affected regions. We are working on identifying the cause and will update again within 15 minutes.

  Read on status.livekit.io

• Increased join latency in US East and US Central · 20 Oct 2026, 23:09 UTC · 42 min · minor

  resolved · 20 Oct 2026, 23:50 UTC

  Between 21:30 and 23:17 UTC, roughly 10% of all WebRTC connections in our US East and US Central regions took 5 seconds or longer to establish. We applied a mitigation at 23:15 UTC, and join latencies have returned to normal by 23:17 UTC. We will follow up with more details on the root cause and preventive actions in a postmortem. We apologize for the impact and appreciate your patience.

  monitoring · 20 Oct 2026, 23:25 UTC

  We identified connection drops at load balancers in our US Central and US East regions that caused a subset of connection latencies to take 5 seconds or longer. We applied a mitigation at 23:15 UTC, and we are seeing connection speeds return to normal. We are continuing to monitor before marking this resolved.

  investigating · 20 Oct 2026, 23:09 UTC

  We are currently investigating higher than normal join latencies affecting a small percentage of participants in our US East and US Central regions. The latency increase appears to have begun at 21:30 UTC. Affected participants may notice increased join latencies higher than 5 seconds. The SDK retries automatically, and most of these joins succeed on retry. If your application stops waiting for an agent before then, those calls may time out. We will share another update as we learn more.

  Read on status.livekit.io

• Investigating reports of elevated API failures in Chicago region · 19 Oct 2026, 17:02 UTC · 32 min · minor

  postmortem · 22 Oct 2026, 00:47 UTC

  ## Summary On October 19, 2026, between 16:34 and 17:03 UTC and again between 17:47 and 17:54 UTC, some room management, agent dispatch and SIP API requests failed for rooms hosted in our US Central \(Chicago\) region. Requests from other regions that targeted those rooms also failed. During these windows some rooms could not be created or joined, and some agents were not dispatched. The cause was CPU exhaustion on the node running one of our message bus instances in US Central. A recently deployed overlay network used more CPU than it requested, and because our monitoring tracked CPU per pod rather than per node, we didn't see the node run out. That message bus instance began dropping messages, and a room-coordination service that depended on it stopped completing requests. We have mov…

  resolved · 19 Oct 2026, 17:34 UTC

  Between 16:35-17:03 UTC, Chicago region experienced about 11% failure rates in API errors, failed agent dispatches, and issues connecting to rooms. We faced another wave of the same issue between 17:47-17:53 UTC where the failure rates were less than 10%. Room Service APIs called from other regions targeting to a room hosted in Chicago region were also affected during this period. API requests made with recent server SDK versions are automatically retried in other regions, so customers on those versions should not have seen these errors. The last related errors occurred at 17:53 UTC, and all affected services are operating normally since. We will share a detailed RCA with more information soon.

  monitoring · 19 Oct 2026, 17:11 UTC

  A fix has been implemented as of 17:00 UTC and we are seeing the errors return back to baseline. We are continuing to monitor before marking this resolved.

  investigating · 19 Oct 2026, 17:02 UTC

  We are currently investigating reports of elevated API errors across our services in the Chicago region.

  Read on status.livekit.io

• Degraded SIP Performance in US West · 16 Oct 2026, 16:04 UTC · 1 h 26 min · minor

  postmortem · 22 Oct 2026, 14:22 UTC

  **Root Cause** On 2026-10-16, a subset of SIP calls in our US West region failed. Two of our SIP servers advertised IPv6 addresses for signaling and media, which many carrier providers don't support. Carriers rejected outbound calls routed through these servers, and inbound calls were answered but dropped almost immediately without audio. We had recently started running SIP in a US West cluster that uses both IPv4 and IPv6 networking and our SIP servers didn't enforce IPv4 addresses. **Technical Details** When a SIP server starts, it determines its public address by querying an external address-lookup service. On the two affected servers, our primary lookup service didn't respond in time so they fell back to a backup service that returned their IPv6 address instead. Nothing in the SIP…

  resolved · 16 Oct 2026, 17:30 UTC

  This incident has been resolved. Between 14:49 UTC and 15:58 UTC, approximately 14% of outbound calls and 5% of inbound calls in US West failed. We will follow up with more details surrounding the root cause and preventative actions in a postmortem.

  monitoring · 16 Oct 2026, 16:57 UTC

  We estimate that approximately 14% of outbound calls and 5% of inbound calls in US West failed between 14:49 UTC and 15:58 UTC. We will follow up as soon as possible with more details.

  monitoring · 16 Oct 2026, 16:35 UTC

  We applied mitigation as of 15:58 UTC and SIP outbound connection success has returned to normal. We are continuing to monitor before marking this resolved.

  identified · 16 Oct 2026, 16:12 UTC

  We have identified the source of the issue and are working to route around the impact.

  investigating · 16 Oct 2026, 16:04 UTC

  We are investigating degraded SIP performance in US West starting at 14:49 UTC affecting new outbound calls.

  Read on status.livekit.io

• Intermittent connection timeouts in the Frankfurt region · 16 Oct 2026, 10:55 UTC · 1 h 4 min · minor

  resolved · 16 Oct 2026, 11:59 UTC

  This incident is resolved. Connections to the Frankfurt region have returned to normal.

  monitoring · 16 Oct 2026, 11:15 UTC

  We have applied a mitigation and new connections should no longer time out. We are monitoring to confirm that connection times have returned to normal.

  investigating · 16 Oct 2026, 10:55 UTC

  We are investigating intermittent timeouts when establishing new connections to our Frankfurt (EU) region. A small percentage of connection attempts may time out. We are working on a mitigation and will post an update as soon as possible.

  Read on status.livekit.io

• Observability upload and Agent Simulations failures · 13 Oct 2026, 10:01 UTC · 3 h 43 min · critical

  postmortem · 21 Oct 2026, 23:40 UTC

  **Root Cause** During a security rotation of access credentials, we revoked a storage credential that we believed was no longer in use. It was still being used by our observability platform, which stores the data behind the dashboard and the Analytics API, the Agent Insights data that agents upload at the end of each session, and by the service that serves that data back for downloads and Agent Simulations. Once the credential was revoked, uploads failed in all regions. Restoring service took longer than a credential swap normally would for three reasons: * New credentials had to be set up, and each affected service had to be updated to use them. * The new credentials took longer than expected to become available in all regions \(about two hours in our US East region\). * Once the obser…

  resolved · 13 Oct 2026, 13:44 UTC

  This incident has been resolved. Between 08:15 and 12:35 UTC, agents were not able to upload agent observability data to LiveKit's servers in all regions. Agent sessions completed normally, but, unfortunately, any Agent Insights data which attempted to upload within that window (traces/transcripts/logs/recordings) is unrecoverable. The ability to download existing Agent Insights data was impaired until 13:15 UTC. Agent Simulations were unavailable due to a upstream dependency and came back online at 13:25 UTC. Sincere apologies for the impact. We will follow up with a postmortem as soon as possible.

  identified · 13 Oct 2026, 13:15 UTC

  Agent Insights uploads are now operational and session data has been storing normally since 12:40 UTC. We are still investigating an issue with Simulations. Simulation runs may complete without a transcript, summary, or verdict. We will post an update shortly.

  identified · 13 Oct 2026, 11:40 UTC

  We are continuing to work on a fix for this issue.

  identified · 13 Oct 2026, 10:45 UTC

  We have identified the cause of the Agent Insights issue and are working on a fix.

  investigating · 13 Oct 2026, 10:01 UTC

  We are investigating an issue with Agent Insights where agents are unable to upload their observability data at the end of their sessions. Some recent agent sessions may be missing from the dashboard's sessions list or shown as “In progress”. Agent sessions themselves are not affected. We will post an update shortly.

  Read on status.livekit.io

• Investigating delayed cloud agent builds in US East · 6 Oct 2026, 03:46 UTC · 1 h 6 min · minor

  resolved · 6 Oct 2026, 04:52 UTC

  A fix was applied and all builds are back to normal.

  identified · 6 Oct 2026, 03:46 UTC

  We are investigating an issue causing some cloud agent builds to be backed up in US East. This issue only impacts new builds for a small number of customers, existing agents are running without any impact.

  Read on status.livekit.io

• Investigating scaling issue affecting Cloud Agents in EU (Frankfurt) · 5 Oct 2026, 13:34 UTC · 47 min · minor

  resolved · 5 Oct 2026, 14:21 UTC

  This incident has been resolved, and we have confirmed full recovery.

  monitoring · 5 Oct 2026, 13:40 UTC

  A fix has been implemented and we are monitoring to confirm full recovery.

  investigating · 5 Oct 2026, 13:34 UTC

  We are investigating potential scaling issues with LiveKit Cloud hosted agents in eu-central resulting in increased join latencies. Existing agents are still functional and can serve sessions normally, but they may be slower to join new sessions. We are actively working on a mitigation to alleviate this issue. We will provide another update as soon as possible.

  Read on status.livekit.io

• Monitoring reports of intermittently increased API latency impacting Egress, Ingress, and SIP · 15 Sept 2026, 22:10 UTC · 1 h 5 min · minor

  postmortem · 17 Sept 2026, 13:53 UTC

  Please see a full postmortem [here](https://status.livekit.io/incidents/dbqb4jhxcg9h).

  resolved · 15 Sept 2026, 23:15 UTC

  We have resolved the underlying issue and have not observed any further occurrences of this incident. We will follow up with a detailed postmortem in the original incident.

  monitoring · 15 Sept 2026, 22:10 UTC

  From 21:11 to 21:21 UTC we observed an occurrence of the same incident experienced earlier today impacting Global SIP, Ingress, and Egress due to the same underlying issue. We are currently operating normally and are continuing to monitor.

  Read on status.livekit.io

• Investigating reports of intermittently increased API latency impacting Egress, Ingress, and SIP · 15 Sept 2026, 17:04 UTC · 1 h 12 min · minor

  postmortem · 17 Sept 2026, 14:26 UTC

  ### Summary On 15 September, LiveKit Cloud experienced three periods of degraded performance between 13:34–13:41, 16:06–16:11 and 21:10–21:22 UTC. Ingress creation was the most affected: more than half of `CreateIngress` requests failed at the worst point. A number of in-progress recordings ended prematurely, and a small percentage of inbound SIP calls failed during a one-minute period \(during each impact window\). Realtime connections were not affected and media already flowing continued normally. The cause was a dropped connection to our primary metadata database that neither the client nor server side detected, which left a transaction open and holding row locks for up to 17 minutes. Requests queued behind those locks, and the sudden release of that backlog — not the wait itself — is…

  resolved · 15 Sept 2026, 18:16 UTC

  We are resolving this incident as the underlying issue has been resolved. Thank you for your patience and apologies for the disruption. We will follow up with a postmortem as soon as possible.

  monitoring · 15 Sept 2026, 18:03 UTC

  We are continuing to monitor, but want to keep users up to date with how we believe impact may have materialized. The first impact window started at 13:40 UTC and impacted Ingress and Egress services for about 3 minutes. The second impact window started at 16:11 UTC and impacted SIP, Ingress, and Egress services for about 1 minute.

  monitoring · 15 Sept 2026, 17:37 UTC

  We are still investigating, but believe that customer impact should be mostly mitigated - although some spikes may still be occurring. We are investigating reports of aborted egresses which we believe were also related to this issue. We will post another update as soon as possible.

  investigating · 15 Sept 2026, 17:04 UTC

  We are investigating reports of intermittently increased API latencies starting at 13:30 UTC. Users may observe increased latency spikes across all APIs.

  Read on status.livekit.io

• Cloud Dashboard, Analytics Services, and Billing API failures · 15 Sept 2026, 12:31 UTC · 2 h 58 min · major

  resolved · 15 Sept 2026, 15:30 UTC

  This incident has been resolved. Between 12:08 and 14:23 UTC, customers were unable to access the Cloud Dashboard and the Analytics Services APIs. The cause was a control plane failure in our last remaining legacy Kubernetes cluster, which took out a dependency of those services. Our user-facing services (RTC, SIP, and others) were unaffected, as they run redundantly across our modern clusters and have no dependency on the legacy cluster. We have no indication of data loss. Recovery took longer than we would like, as mitigation required working within the legacy cluster. Work was already underway to make the affected dependency redundant across our modern clusters, and that cluster is scheduled for decommissioning, which removes this class of failure. We will follow up with a postmortem.

  monitoring · 15 Sept 2026, 14:29 UTC

  A fix has been deployed as of 14:23 UTC, and access to the Cloud Dashboard and Analytics Services APIs is returning to normal. We are continuing to monitor before marking this resolved. Recovery may take a few additional minutes for some clients as the change fully propagates; retrying or reconnecting will restore access.

  identified · 15 Sept 2026, 13:04 UTC

  We have identified the cause of the issue affecting the Cloud Dashboard and Analytics Services APIs, and recovery work is underway. Customers may continue to see errors accessing the Cloud Dashboard and Analytics Services APIs during this time. Room APIs, RTC APIs, and all other services remain healthy and unaffected. We have no indication of data loss from this incident. We will post another update as recovery progresses.

  investigating · 15 Sept 2026, 12:49 UTC

  We are continuing to investigate this issue.

  investigating · 15 Sept 2026, 12:31 UTC

  We are continuing to investigate this issue affecting LiveKit Cloud dashboard, Analytic Services APIs and Billing APIs. Users may be unexpectedly signed out and unable to sign back in, and API requests may return 522 errors.

  investigating · 15 Sept 2026, 12:08 UTC

  We are investigating an issue where users may be unexpectedly signed out of the LiveKit Cloud dashboard and unable to sign back in.

  Read on status.livekit.io

• Some sessions incorrectly shown as active · 8 Sept 2026, 08:45 UTC

  resolved · 4 Sept 2026, 10:00 UTC

  A subset of room sessions that ended around 4 September 09:57 UTC were not recorded with an end time. These sessions continue to appear as active in the Cloud dashboard and in session records, and no `room_ended` end time is reflected for them. This was a reporting issue only. Rooms ended normally for participants, live traffic was not affected, and there is no impact on usage or billing. The underlying cause has been identified and fixed. Affected sessions from this window may continue to display as active; they can be safely disregarded.

  Read on status.livekit.io

• Identified increased agent join latencies in eu-central · 5 Sept 2026, 23:36 UTC · 1 h 36 min · minor

  postmortem · 8 Sept 2026, 21:59 UTC

  **Root Cause** A configuration change introduced a formatting error in the startup settings for the server pools that run hosted agents in our eu-central region. Newly provisioned servers failed to start, so the region could not add capacity. Agents that were already running were unaffected, but new agent deployments, version rollouts, and automatic scale-ups were delayed or stuck pending until the change was reverted. **Timeline \(UTC\)** `2026-09-04 23:56` - Configuration change deployed. The error only affected newly provisioned servers, so there was no immediate impact. `2026-09-05 18:07` - New servers began failing to start. Impact begins, intermittent at first. `2026-09-05 22:23` - Our monitoring alerted us to agent deployments stuck pending and we began investigating. `20…

  resolved · 6 Sept 2026, 01:12 UTC

  The mitigation was successful and users shouldn't notice any issues with join latencies or creating new agents. We will follow up as soon as possible with a postmortem.

  monitoring · 6 Sept 2026, 00:24 UTC

  We have applied a mitigation and believe that symptoms should be improving. We will update again with confirmation as soon as possible.

  identified · 5 Sept 2026, 23:36 UTC

  We have identified an issue with LiveKit Cloud hosted agents in eu-central. Existing agents in eu-central are facing scaling issues resulting in increased join latencies. Existing agents are still functional and can serve sessions normally, but they may be slower to join new sessions. Additionally, new agents cannot be created in this region. We are actively working on a mitigation to alleviate this issue. We will provide another update as soon as possible.

  Read on status.livekit.io

• Investigating reports of one-way audio issues in LiveKit Phone Numbers · 2 Sept 2026, 21:25 UTC · 20 min · minor

  resolved · 2 Sept 2026, 21:45 UTC

  This incident has been resolved. We will follow up with a detailed postmortem as soon as possible.

  monitoring · 2 Sept 2026, 21:25 UTC

  An upstream carrier reverted a codec change that was causing one-way audio issues on calls to LiveKit-issued phone numbers. As of 21:10 UTC calls are connecting normally and we are no longer seeing the issue. The upstream codec change has impacted calls from T-Mobile and AT&T carriers. No other SIP providers were affected. We are monitoring before marking this resolved.

  investigating · 2 Sept 2026, 21:03 UTC

  We are investigating elevated issues in calls connected to LiveKit Phone numbers where callee audio is not being heard by the caller. This is currently only experienced for numbers issues by LiveKit, and no other SIP provider connectivity should be affected. Our team is actively investigating this.

  Read on status.livekit.io