Is LiveKit Cloud down? › Outage history › May 28, 2026
LiveKit Cloud outage on May 28, 2026: what happened
On May 28, 2026, the LiveKit status page reported "Elevated Reports of Participant Connection Latency and Errors In US East Region". About 5 hours 20 min: from May 28, 2026, 14:53 UTC to May 28, 2026, 20:13 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.
- Started
- May 28, 2026, 14:53 UTC
- Resolved
- May 28, 2026, 20:13 UTC
- Duration
- 5 hours 20 min
- Official impact
- Critical
- Affected
- US East - Real Time Communication, Global Real Time Communication, Regional Real Time Communication - US East - Real Time Communication
- Source
- Elevated Reports of Participant Connection Latency and Errors In US East Region on the LiveKit status page
The LiveKit status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.
What caused the LiveKit Cloud outage?
"We sincerely apologize to customers whose traffic was disrupted. We've let you down, and we are taking this very seriously."
From the LiveKit status page, incident report, May 30, 2026, 18:18 UTC.
When was it fixed?
The LiveKit status page marked it resolved at May 28, 2026, 20:13 UTC, 5 hours 20 min after it started. A fix was in place and being monitored from May 28, 2026, 15:50 UTC. Its resolution note: "Connection errors have remained cleared since the US East drain at 15:44 UTC, and as of 19:30 UTC, US East is back online. We'll share a detailed RCA in the coming days."
Timeline of official updates
Every update the LiveKit status page posted, oldest first. Times are UTC.
May 28, 2026, 14:53 UTC investigating
We are currently investigating reports of spikes in participant connection latency and errors
May 28, 2026, 15:35 UTC 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.
May 28, 2026, 15:50 UTC 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.
May 28, 2026, 16:27 UTC 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.
May 28, 2026, 18:27 UTC 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.
May 28, 2026, 20:13 UTC resolved
Connection errors have remained cleared since the US East drain at 15:44 UTC, and as of 19:30 UTC, US East is back online. We'll share a detailed RCA in the coming days.
The official incident report
Published May 30, 2026, 18:18 UTC. The opening of the report; the full text is on the official page.
Summary LiveKit Cloud validates incoming API and connection requests via an internal authentication service, accessed over gRPC. The service has been in place since 2022 and is designed for resilience: it runs as multiple redundant instances, has pod-level health monitoring that automatically reaps unhealthy pods, and is backed by in-memory caches so it can survive transient database failures. On 2026-05-28, between 13:55 UTC and 15:45 UTC, a percentage of requests and new connections in our US East region failed or timed out. The root cause was a rare failure mode on a single instance of the authentication service. The instance remained reachable and its TCP connections stayed alive, but it began responding to gRPC requests extremely slowly, in a way that did not trip our existing pod-level health checks or cause gRPC clients to fail over. We sincerely apologize to customers whose traffic was disrupted. We've let you down, and we are taking this very seriously. In addition to the corrective actions outlined below, we are performing a thorough audit of our systems for other failure modes we may not have anticipated. Timeline and Impact \(all times in UTC on 2026-05-28\) * 13:55: Elevated rate of authentication failures observed. * 14:15: On-call team notified; investigation begins. * 14:46: Error rate continues to climb; incident escalated to Sev 1. * 15:35: US East drained; error rate begins to subside. * 16:32: Root cause identified; faulty instance shut down. * 16:32: Webhooks backlogged during the incident begin to deliver. Between 2026-05-28 13:55 UTC and 15:35 UTC, a percentage of API requests and new connection attempts in our US East region failed or timed out. This included new participant connections, SIP connection requests, and agent connections ...
Read the full report on the LiveKit status page
LiveKit Cloud outage questions
What caused the LiveKit Cloud outage on May 28, 2026?
In its incident report (May 30, 2026, 18:18 UTC), the LiveKit status page said: "We sincerely apologize to customers whose traffic was disrupted. We've let you down, and we are taking this very seriously."
When was the LiveKit Cloud outage on May 28, 2026 fixed?
The LiveKit status page marked it resolved at May 28, 2026, 20:13 UTC, 5 hours 20 min after it started. A fix was in place and being monitored from May 28, 2026, 15:50 UTC. Its resolution note: "Connection errors have remained cleared since the US East drain at 15:44 UTC, and as of 19:30 UTC, US East is back online. We'll share a detailed RCA in the coming days."
How long did the LiveKit Cloud outage last?
About 5 hours 20 min: from May 28, 2026, 14:53 UTC to May 28, 2026, 20:13 UTC, by the official start and resolution times.
Was LiveKit Cloud completely down?
The LiveKit status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness. The affected parts listed were: US East - Real Time Communication, Global Real Time Communication, Regional Real Time Communication - US East - Real Time Communication.
Which parts of LiveKit Cloud were affected?
The LiveKit status page listed: US East - Real Time Communication, Global Real Time Communication, Regional Real Time Communication - US East - Real Time Communication.
Other recent LiveKit Cloud incidents
- Increased join latency in US East and US Central Oct 20, 2026, 23:09 UTC, 42 minutes
- Investigating reports of elevated API failures in Chicago region Oct 19, 2026, 17:02 UTC, 32 minutes
- Degraded SIP Performance in US West Oct 16, 2026, 16:04 UTC, 1 hour 26 min
- Intermittent connection timeouts in the Frankfurt region Oct 16, 2026, 10:55 UTC, 1 hour 4 min
- Observability upload and Agent Simulations failures Oct 13, 2026, 10:01 UTC, 3 hours 43 min
- Investigating delayed cloud agent builds in US East Oct 6, 2026, 03:46 UTC, 1 hour 6 min
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.