LiveKit incident: Degraded Connectivity in US Central

Affected components

• US Central - SIP

1. postmortemJun 4, 2026, 14:01 UTC

   **Summary** On June 2, 2026, a small subset of users connected to LiveKit Cloud US Central region experienced elevated connection failures between 12:06 and 14:38 UTC. A single node in the region entered a degraded state in which it continued to accept new connections but could not reliably complete the real-time media connection those calls depend on. As a result, a portion of participant connections, including inbound and outbound SIP calls routed through Chicago failed to connect or dropped shortly after starting. We mitigated this by routing SIP traffic away from the affected server, suspending and removing the faulty node, and restoring normal service to the region. **Timeline \(UTC\)** * 12:06 — Start of measurable customer impact * 14:04 — Chicago SIP traffic drained as mitigation * 14:38 — Problematic server suspended; customer impact ends * 15:07 — Chicago SIP service fully restored **Root cause** The incident was caused by a "gray failure" of a single node in the

2. resolvedJun 2, 2026, 15:18 UTC

   This incident has been resolved.

3. monitoringJun 2, 2026, 14:58 UTC

   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.

4. monitoringJun 2, 2026, 14:17 UTC

   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.

5. investigatingJun 2, 2026, 14:05 UTC

   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.

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.

• GitBook: Increased API error rateMajor · Jun 2, 2026, 14:40 UTC
• ClickHouse Cloud: New service provisioning may fail in AzureMinor · May 28, 2026, 18:26 UTC
• Contentful: Issues with file uploadsMinor · Jun 2, 2026, 13:02 UTC
• Elasticsearch: Missing Metrics in Cloud Console - Azure North EuropeMinor · Jun 2, 2026, 13:25 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