Live / LiveKit / Incident
LiveKit: Investigating failing calls and RoomService API failures in US Central/East and dashboard issues
LiveKit · livekit.ioMinor incidentResolved2026-10-29 01:19 UTC
Public — what happened
Summary
LiveKit said it began investigating at 23:47 UTC on October 28 after more outbound calls than usual were failing in its US Central and US East regions. Over the next half hour it reported that the cloud dashboard could not be reached and that inbound calls and its Room Service were also affected. LiveKit said it tried a mitigation, and by 00:16 UTC it believed this had worked, with the dashboard accessible again and error rates falling. It later noted degraded SIP, RTC and API services in its Mexico region while the US regions stayed stable, and the incident was marked resolved at 01:19 UTC on October 29; LiveKit did not state a cause in the updates provided.
Affected
Cloud Dashboard (cloud.livekit.io), US East - SIP, US Central - SIP, US Central - Real Time Communication, US East - Real Time Communication
Timeline
- Started — 2026-10-28 23:47 UTC
- Investigating — 2026-10-28 23:47 UTC (5 updates)
- Monitoring — 2026-10-29 00:16 UTC
- Identified — 2026-10-29 00:36 UTC
- Resolved — 2026-10-29 01:19 UTC · 1h 32m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach LiveKit against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for LiveKit: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the LiveKit report →
More from LiveKit
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.