LiveKit incident: Intermittent connectivity disruptions in US regions

1. postmortemMay 22, 2026, 07:36 UTC

   ## Summary LiveKit Cloud runs as a distributed realtime network, with data centers around the world interconnected via dedicated networking. Even with dedicated fiber, momentary disruptions between any two data centers can and do occur. To handle these blips, we have built a comprehensive set of resilience mechanisms that automatically reroute and relay traffic over alternate healthy paths. For example, if data centers A and B cannot reach one another cleanly but both can reach data center C, we use C as a relay so that traffic flows A to C to B. Under normal circumstances, network blips between our data centers are handled transparently there would be no visible impact. Between 2026-05-07 and 2026-05-19, a small number of these otherwise routine network blips did become customer-visible in our US regions. Affected sessions experienced a brief interruption to media \(under 5 minutes\) before recovering on a new path. ## Impact Five short windows of disruption were observed, each ti

2. resolvedMay 16, 2026, 02:50 UTC

   We are resolving this incident as we have not observed any further connectivity disruptions. We will follow up with a postmortem once available.

3. monitoringMay 15, 2026, 21:16 UTC

   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.

4. investigatingMay 15, 2026, 16:57 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LiveKit's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Datadog: Azure Metrics ReportingCritical · May 16, 2026, 02:17 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Mixpanel: Query API degraded performanceMinor · May 14, 2026, 23:17 UTC
• Expo: High queue times for Android and iOS buildsMinor · May 15, 2026, 07:15 UTC
• Netlify: Purges are Delayed on Primary Load BalancerMinor · May 15, 2026, 16:23 UTC
• LaunchDarkly: Delayed processing of Session Replay and Error dataMinor · May 16, 2026, 00:03 UTC

How often does LiveKit have incidents?

LiveKit reported 18 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 31m. See LiveKit's uptime and incident history