LiveKit incident: Investigating reports of failed SIP Transfer calls in US East

Affected components

• US East - SIP

1. postmortemSep 1, 2026, 11:44 UTC

   ## Summary On 17 August, between 17:24 and 18:05 UTC, a small percentage of SIP call transfers failed in our US East region during a routine configuration rollout. An issue in the automation that manages our SIP signaling servers prevented outgoing servers from being taken out of service safely, and those servers shut down while calls were still active on them. Transfers have completed normally since 18:05 UTC. Calls themselves stayed connected, and no other region was affected. ## Root Cause The configuration change restarts the servers that handle SIP signaling one at a time. Before a server is shut down, it is removed from service so that no new calls reach it, and it is then given some time to finish the calls it is already handling. In this case that removal did not complete expectedly and the outgoing servers kept receiving new calls for the entire drain duration, then shut down on schedule with calls still active on them. ## Timeline \(UTC\) * 16:52 - A routine configurati

2. resolvedAug 17, 2026, 19:22 UTC

   We have identified the root cause of both spikes and have ensured safeguards to prevent a recurrence. We've been monitoring since 18:05 UTC and have seen no further transfer failures, and have confirmed that SIP transfers are operating normally. We will follow up with a detailed post-mortem.

3. investigatingAug 17, 2026, 18:22 UTC

   No transfer failures has been observed since 18:05 UTC and SIP transfers are currently completing normally. Impact was limited to a small percentage of calls between 15:48-16:08 UTC and 17:24-18:05 UTC. We're actively monitoring while we investigate the cause and put safeguards in place to prevent a recurrence.

4. investigatingAug 17, 2026, 18:10 UTC

   We're investigating an elevated rate of failures when transferring active SIP calls in the US East region. SIP calls themselves remain connected, and inbound and outbound calling are otherwise operating normally.

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.

• GitHub: Incident with GitHub.comCritical · Aug 17, 2026, 13:40 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• CircleCI: GitHub Incidents impacting CircleCI functionalityMajor · Aug 17, 2026, 14:04 UTC
• Cursor: GitHub degradation affecting some Cursor services — Automations, Cloud Agents, CodebaseMajor · Aug 17, 2026, 14:34 UTC
• dbt Cloud: Git Failures in dbt PlatformMajor · Aug 17, 2026, 15:02 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• HashiCorp Vault: Delayed HCP Terraform RunsMinor · Aug 15, 2026, 17:08 UTC
• GitBook: GitHub outage affecting Git SyncMinor · Aug 17, 2026, 13:56 UTC
• Vercel: Partial disruption of Observability, Analytics, Firewall, Usage, and Login in DashboardMinor · Aug 17, 2026, 14:30 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