Live  /  LiveKit  /  Incident

LiveKit: Investigating reports of intermittently increased API latency impacting Egress, Ingress, and SIP

LiveKit · livekit.ioMinor incidentResolved2026-09-15 18:03 UTC
Public — what happened

Summary

LiveKit reported a minor incident involving intermittent slowdowns in its API that affected its Egress, Ingress, and SIP services. According to LiveKit, the first period of disruption began at 13:40 UTC and hit Ingress and Egress for roughly 3 minutes, while a second, shorter period starting at 16:11 UTC affected SIP, Ingress, and Egress for about 1 minute. The company did not identify a cause in its update and said it was still monitoring the situation, though the incident is listed as resolved at 18:24.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 39, 2026, our weekly internet health report.

The full archive is on the LiveKit status & history page.

Related: LiveKit status & history. SquidGrid is not affiliated with LiveKit.