Is LiveKit Cloud down? › Outage history › Apr 15, 2026

LiveKit Cloud partial outage on Apr 15, 2026: what happened

On Apr 15, 2026, the LiveKit status page reported "Increased Latency in RoomService APIs, brief period of higher error rate". About 4 hours 45 min: from Apr 15, 2026, 23:23 UTC to Apr 16, 2026, 04:09 UTC, by the official start and resolution times.

LiveKit Cloud right now

At our last refresh (Oct 22, 2026, 12:35 UTC) LiveKit Cloud was up: All Systems Operational.

Is LiveKit Cloud down right now? →
Started
Apr 15, 2026, 23:23 UTC
Resolved
Apr 16, 2026, 04:09 UTC
Duration
4 hours 45 min
Official impact
Major
Affected
Global Real Time Communication, Regional Real Time Communication - US West - Real Time Communication
Source
Increased Latency in RoomService APIs, brief period of higher error rate on the LiveKit status page

The LiveKit status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the LiveKit Cloud partial outage?

"The sweeper is a background process that removes rows from the `rooms` table as sessions end. Earlier on 2026-04-15, its throughput dropped significantly, and over roughly 8 hours stale rows accumulated to the point where the table was many times larger than its intended steady-state size."

From the LiveKit status page, incident report, Apr 17, 2026, 16:37 UTC.

When was it fixed?

The LiveKit status page marked it resolved at Apr 16, 2026, 04:09 UTC, 4 hours 45 min after it started. A fix was in place and being monitored from Apr 16, 2026, 03:51 UTC. Its resolution note: "This issue is now fully resolved. We will be posting a detailed RCA."

Timeline of official updates

Every update the LiveKit status page posted, oldest first. Times are UTC.

  1. Apr 15, 2026, 23:23 UTC investigating

    We are investigating reports of increased latencies in RoomService APIs in the US West region, specifically on CreateRoom, DeleteRoom, and UpdateRoomMetadata APIs.

  2. Apr 16, 2026, 00:13 UTC investigating

    We are continuing to investigate this issue.

  3. Apr 16, 2026, 01:07 UTC 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.

  4. Apr 16, 2026, 02:10 UTC identified

    We continue to see the long Room API latencies which are now 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.

  5. Apr 16, 2026, 03:45 UTC investigating

    While applying a fix for the API latencies, we are temporarily seeing increased failure rates in RoomServices APIs, including CreateRoom, UpdateRoomMetadata, and DeleteRoom. We are actively working on mitigating this. Impact has been upgraded to major.

  6. Apr 16, 2026, 03:51 UTC monitoring

    Our fix is fully implemented and we are not seeing any more failures or high latencies of the RoomService APIs. We are continuing to monitor the issue. We did observe a period of 15 minutes with high API failures while mitigation steps were being applied.

  7. Apr 16, 2026, 04:09 UTC resolved

    This issue is now fully resolved. We will be posting a detailed RCA.

The official incident report

Published Apr 17, 2026, 16:37 UTC. The opening of the report; the full text is on the official page.

Summary LiveKit's core realtime and agent services are designed to tolerate database failures. WebRTC media, SIP calls, and hosted agent sessions continue to operate even when our database backend is slow or unavailable. A subset of Room APIs, specifically `CreateRoom`, `DeleteRoom`, and `UpdateRoomMetadata`, do depend on a database for consistency and disaster recovery. That database is highly available and globally distributed, with no single point of failure. When it is under significant contention, these Room APIs can return errors or time out, while realtime traffic continues to flow normally. On 2026-04-15, database contention caused a percentage of Room API calls to fail in our US-West region. Remediation work later produced a 26-minute global outage of the Room APIs. Realtime sessions, SIP calls, and agent processes were unaffected throughout. We sincerely apologize to customers whose applications were disrupted during this incident. Impact The incident had two distinct phases of customer impact. Phase 1: Elevated Room API timeouts in US-West \(2026-04-15 22:10 UTC to 2026-04-16 03:14 UTC\) A percentage of `DeleteRoom`, `UpdateRoomMetadata`, and `ListRooms` calls timed out, primarily in our US-West region. Other regions saw limited impact during this phase. Customers with high Room API volume in US-West observed elevated error rates on their integrations; the majority of customers were not affected. Phase 2: Global Room API outage \(2026-04-16 03:14 to 03:40 UTC, ~26 minutes\) While we were swapping in a rebuilt `rooms` table, the table was briefly missing from the database, and the majority of Room API calls globally returned HTTP 500 with `ERROR: relation "rooms" does not exist`. WebRTC sessions, SIP calls, and agent processes continued to function, ...

Read the full report on the LiveKit status page

LiveKit Cloud partial outage questions

What caused the LiveKit Cloud partial outage on Apr 15, 2026?

In its incident report (Apr 17, 2026, 16:37 UTC), the LiveKit status page said: "The sweeper is a background process that removes rows from the `rooms` table as sessions end. Earlier on 2026-04-15, its throughput dropped significantly, and over roughly 8 hours stale rows accumulated to the point where the table was many times larger than its intended steady-state size."

When was the LiveKit Cloud partial outage on Apr 15, 2026 fixed?

The LiveKit status page marked it resolved at Apr 16, 2026, 04:09 UTC, 4 hours 45 min after it started. A fix was in place and being monitored from Apr 16, 2026, 03:51 UTC. Its resolution note: "This issue is now fully resolved. We will be posting a detailed RCA."

How long did the LiveKit Cloud partial outage last?

About 4 hours 45 min: from Apr 15, 2026, 23:23 UTC to Apr 16, 2026, 04:09 UTC, by the official start and resolution times.

Was LiveKit Cloud completely down?

No. The LiveKit status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: Global Real Time Communication, Regional Real Time Communication - US West - Real Time Communication.

Which parts of LiveKit Cloud were affected?

The LiveKit status page listed: Global Real Time Communication, Regional Real Time Communication - US West - Real Time Communication.

Other recent LiveKit Cloud incidents

Full LiveKit Cloud outage history and biggest outages → · Recent outages across all services →

Quotes are the LiveKit status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with LiveKit Cloud. Times are UTC.