Looking for an update now? Check the current status, or follow LiveKit for future changes.
82.8%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
86.7%
30
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
Cloud Dashboard, Analytics Services, and Billing API failures
Cloud Dashboard (cloud.livekit.io)US West - Analytics Ingestion
monitoring
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
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
We are continuing to investigate this issue.
investigating
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
We are investigating an issue where users may be unexpectedly signed out of the LiveKit Cloud dashboard and unable to sign back in.
Identified increased agent join latencies in eu-central
We have applied a mitigation and believe that symptoms should be improving. We will update again with confirmation as soon as possible.
identified
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.
Investigating reports of one-way audio issues in LiveKit Phone Numbers
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
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.
Since ~06:30 UTC, outbound calls routed through Twilio are failing at an elevated rate. Twilio is reporting degraded voice connectivity (https://status.twilio.com/), affecting North America, Latin America, Europe, and the Middle East & Africa.
A fix has been deployed as of 1055 UTC, and the dashboard is now loading successfully. We are continuing to monitor before marking this resolved.
identified
We have identified the cause: a problematic node in US-East and are deploying a fix. Impact continues to be limited to the dashboard.
investigating
We are currently investigating reports of our dashboard failing to load across multiple regions, beginning at 0700 UTC. Other services remain unaffected and the impact is limited to the dashboard.
Legacy Incident Archive
33 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Elevated latency in Hyderabad region
minorSource not attested
Last archived state: resolved
View archived record details
investigating
As of 09:21 UTC, we've applied a mitigation by routing traffic away from the Hyderabad region. Latency rates are returning to normal levels. We're continuing to monitor the issue.
investigating
We're investigating elevated latency affecting Ingress and SIP services in our Hyderabad region.
Degraded Connectivity in US Central
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified the root cause as a single problematic media node in US Central, which has been suspended at 14:38 UTC. We are continuing to monitor before marking this resolved.
monitoring
We have routed the traffic away from the US Central region at 14:00 UTC and are seeing the connection failures returning to normal levels. We are continuing to monitor the issue.
investigating
We're investigating elevated SIP call connection failures in our US Central region beginning at ~12:06 UTC. We are working to mitigate this issue.
May 2026
Elevated Reports of Participant Connection Latency and Errors In US East Region
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Service is operating normally with traffic routing through other regions. We are working on bringing US East back online and will share a detailed RCA once complete.
monitoring
Connection errors have fully cleared since the US East drain completed at 15:44 UTC. We'll continue monitoring. We will be sharing a detailed RCA.
monitoring
US East drain is complete and all new traffic is now routing to other regions. Error rate is trending down and we'll continue monitoring.
identified
We are observing database connection timeouts in the US East region and are currently seeing an impact to all services in the region. We are currently draining the region and routing away all traffic to other regions.
investigating
We are currently investigating reports of spikes in participant connection latency and errors
Network instability in Frankfurt
Source not attested
Last archived state: resolved
View archived record details
monitoring
We have re-enabled our Frankfurt cluster and are monitoring for further disruptions.
investigating
We have observed network instability impacting cross-region traffic from Frankfurt beginning at 18:15 UTC. Traffic has been redirected from Frankfurt as of 19:55 UTC. Participants originally connecting via Frankfurt may see slightly increased latency until the region is restored.
Intermittent connectivity disruptions in US regions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have not observed further instances of connectivity disruptions since 13:19 UTC. We are continuing to investigate why our reroute mechanism did not activate in these isolated instances and are monitoring for further disruptions.
investigating
We are investigating intermittent connectivity disruptions affecting a subset of sessions, caused by internal network degradation between several of our US clusters (most heavily impacting US East). Affected sessions may see brief interruptions (less than 5 minutes) to media relay. We have observed these interruptions at the following times:
- 5/12/26 05:00 UTC
- 5/12/26 17:00 UTC
- 5/13/26 19:00 UTC
- 5/15/26 07:30 UTC
We are actively investigating. Further updates to follow.
Outbound TLS calls are failing
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We believe this incident was not provider-specific and as such have removed Twilio from the incident title.
monitoring
A fix has been implemented and we are monitoring the results. The issue persisted from 18:10 - 19:58 UTC. We will follow up with a postmortem as soon as possible.
investigating
We have noted that outbound calls using TLS via Twilio are failing. We are currently investigating and will update here as soon as we know more.
Cloud Agents experiencing deployment failures in US East
Source not attested
Last archived state: resolved
View archived record details
monitoring
US-East recovered as of 08:55 UTC and has been serving traffic normally since. New and existing agent deployments are working as expected.
We are moving to monitoring while we confirm sustained stability. A full post-incident review will follow.
investigating
We are continuing to work on restoring the Kubernetes API server in US-east. Starting at 08:15 UTC, we are observing impact to existing agent deployments in addition to new deployments. Mitigation is in progress.
investigating
etcd service in our US East Kubernetes cluster is currently down, resulting in API server unresponsiveness and failures for new deployments and redeployments. We are actively working on mitigating this with our data center provider.
investigating
Our team is actively working to resolve deployment failures in US East. Existing deployed agents should not be affected in any way.
investigating
New agent deployments are temporarily unavailable in the US East region, and our team is actively working on this. Dispatches to previously deployed agents are not affected.
investigating
We are currently investigating intermittent deployment failures on Cloud Agents in US East.
investigating
We are currently investigating degraded performance on Agents Hosted on LiveKit Cloud in US East.
April 2026
Investigating SIP participant timeouts and signalling connection errors
Source not attested
Last archived state: resolved
View archived record details
identified
A fix is being implemented. We still have not received any further reports and believe the impact to be minor, but we're continuing to monitor for further issues.
investigating
We received a single report of CreateSIPParticipant timeouts in Singapore. While investigating this, we discovered an increased rate of signalling connection errors on a very small minority of requests, mainly in India. We haven’t received any other reports, but are proactively creating this incident in case users encounter increased connection latency or failed inbound SIP calls. We are continuing to investigate and will update here once we know more.
Increased Latency in RoomService APIs in US West Region
minorSource not attested
Last archived state: resolved
View archived record details
investigating
While applying a fix for the API latencies, we are temporarily seeing increased failure rates (about 10% of the calls) in RoomServices APIs, including CreateRoom and DeleteRoom APIs. We are actively working on mitigating this.
identified
We continue to see the long Room API latencies are also impacting other regions. The latency increases appear to originate from a specific table in our distributed database. The issue has been escalated with the database vendor and we are working on a workaround for decreasing the API latencies. Other services are not impacted.
investigating
We believe these elevated latencies began around 22:00 UTC. We have confirmed that only API requests in US-West should be impacted. The current list of impacted APIs appears to be CreateRoom, DeleteRoom, and UpdateRoomMetadata. We are working on mitigating the issue to return latencies back to normal.
investigating
We are continuing to investigate this issue.
investigating
We are investigating reports of increased latencies in RoomService APIs in the US West region, specifically on CreateRoom, DeleteRoom, and UpdateRoomMetadata APIs.
LiveKit Cloud Dashboard Down
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue and will update as soon as we know more.
