New Multi-region uptime checks and custom-domain status pages

LiveKit Outage History

Daily provider-status observations and published incident history for LiveKit.

Operational

LiveKit is operational. Verified . Official provider source.

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

Jul 24Oct 21

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 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Cloud Dashboard, Analytics Services, and Billing API failures
major Observed active window 2h 58m

View incident details and source

Started:

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
minor Observed active window 1h 38m

View incident details and source

Started:

Europe Central - Cloud Agents
monitoring
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
minor Observed active window 41m

View incident details and source

Started:

Global SIP
monitoring
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.
Twilio Voice outage
minor Observed active window 3h 11m

View incident details and source

Started:

Global SIP
monitoring
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.
LiveKit dashboard failing to load
major Observed active window 3h 44m

View incident details and source

Started:

Cloud Dashboard (cloud.livekit.io)
monitoring
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.

August 2026
Investigating elevated API errors in India
minor Source not attested
Last archived state: resolved
View archived record details
India - Real Time Communication
investigating
Between approximately 09:00 and 10:05 UTC, we observed intermittent elevated error rates on participant management APIs in the Mumbai region. Error rates have since returned to normal, and other regions were not affected. We are continuing to investigate the root cause and are monitoring the region.
Agent session analytics displaying incorrect values in EU Central and India regions
minor Source not attested
Last archived state: resolved
View archived record details
India - Analytics Ingestion Europe Central - Analytics Ingestion
monitoring
We are continuing to monitor while the historical data backfill completes, and will resolve this incident once all analytics for the affected window are fully restored.
monitoring
We identified an issue where agent session analytics in the Cloud dashboard displayed zero concurrent sessions, beginning late on August 21 (UTC). This was a reporting issue only — agent sessions, calls, and all real-time services in these regions operated normally throughout. Ingestion has been restored and we are backfilling historical analytics for the affected window; some charts may show incomplete history until this completes. We are monitoring while the backfill finishes.
Investigating reports of elevated Egress API errors
minor Source not attested
Last archived state: resolved
View archived record details
Global Egress
investigating
We had a spike of errors between 20:52 and 21:01 UTC, and the errors have subsided to baseline as of 21:01 UTC. We are actively monitoring and will share more updates in 30 minutes.
investigating
We are currently investigating reports of elevated API errors across the Egress service. We will post another update in 5 minutes.
Investigating delayed session data ingestion on Cloud Dashboard
minor Source not attested
Last archived state: resolved
View archived record details
Cloud Dashboard (cloud.livekit.io)
monitoring
mitigations have been deployed and we are now catching up to realtime.
identified
the amount of data we are ingesting in the sessions view is outpacing our ability to ingest, thus causing a delay in ingestion. we are pursuing a few mitigations right now including moving to a larger database instance to relieve the processing bottleneck.
identified
We are continuing to work on a fix for this issue.
identified
Sessions data ingest remains delayed for about an hour. It's not impacting other dashboards. we've identified the source of the slow ingest and are working on a mitigation. will update again in 30 mins
investigating
We are currently investigating delayed session data ingestion on Cloud Dashboard. No services appear to be impacted and we don't expect any data to be lost.
Investigating reports of failed SIP Transfer calls in US East
minor Source not attested
Last archived state: resolved
View archived record details
US East - SIP
investigating
No transfer failures has been observed since 18:05 UTC and SIP transfers are currently completing normally. Impact was limited to a small percentage of calls between 15:48-16:08 UTC and 17:24-18:05 UTC. We're actively monitoring while we investigate the cause and put safeguards in place to prevent a recurrence.
investigating
We're investigating an elevated rate of failures when transferring active SIP calls in the US East region. SIP calls themselves remain connected, and inbound and outbound calling are otherwise operating normally.
Hosted agent builds failing in US East
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The total build error rate has decreased significantly due to the mitigation, but a small percentage of builds in US East are still failing. We are continuing to monitor and will follow up with another update as soon as possible.
monitoring
We have deployed a mitigation and builds are now successful. We will continue monitoring while we collect any further details to share.
identified
New hosted agent builds are failing in US East. Existing agent workloads are not affected. We are currently deploying a mitigation and will follow up with more information shortly.
Investigating longer than usual dashboard loading times
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing a 5-10 minute delay in loading some sessions, but we are confident that no data is being lost. We are currently monitoring and will update again once ingestion times have returned to baseline.
investigating
We are currently investigating longer than usual dashboard loading times. No services appear to be impacted and we don't expect any data to be lost.
Investigating alerts for increased timeout error rates on ListParticipants APIs
Source not attested
Last archived state: resolved
View archived record details
monitoring
Error rates on ListParticipants API requests returned to normal as of 18:58 UTC. We will follow up with more details as soon possible.
investigating
We are currently investigating alerts for elevated server error rates on ListParticipants APIs across multiple regions. The impact appears to be intermittent and limited to a subset of room-management API requests. We will follow up with more details as soon possible.
Investigating alerts for degraded room service
Source not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a mitigation to the affected regions and are now monitoring to ensure that performance signals return to baseline. We are still working on determining impact (including how users can determine if they were affected) and will share those details as soon as possible.
investigating
We are currently investigating automated alerting which triggered for degraded Room service performance in the US West and US Central regions beginning around 19:45 UTC. We are working to determine if there is any customer-facing impact. If there is impact, we don't currently have reason to believe that it is widespread. We will update again within 30 minutes.
Elevated error rate on LiveKit Inference (google/gemma-4-31b-it)
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
We are actively investigating elevated error rate on LiveKit Inference (google/gemma-4-31b-it)
identified
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.