LiveKit incident: Degraded SIP Performance in US West

Affected components

• US West - SIP

1. postmortemOct 22, 2026, 14:22 UTC

   **Root Cause** On 2026-10-16, a subset of SIP calls in our US West region failed. Two of our SIP servers advertised IPv6 addresses for signaling and media, which many carrier providers don't support. Carriers rejected outbound calls routed through these servers, and inbound calls were answered but dropped almost immediately without audio. We had recently started running SIP in a US West cluster that uses both IPv4 and IPv6 networking and our SIP servers didn't enforce IPv4 addresses. **Technical Details** When a SIP server starts, it determines its public address by querying an external address-lookup service. On the two affected servers, our primary lookup service didn't respond in time so they fell back to a backup service that returned their IPv6 address instead. Nothing in the SIP server checked that the address it advertised was IPv4. **Timeline \(UTC\)** 2026-10-16 14:49 - First affected SIP server started with an IPv6 address; call failures began 2026-10-16 15:41 - Sec

2. resolvedOct 16, 2026, 17:30 UTC

   This incident has been resolved. Between 14:49 UTC and 15:58 UTC, approximately 14% of outbound calls and 5% of inbound calls in US West failed. We will follow up with more details surrounding the root cause and preventative actions in a postmortem.

3. monitoringOct 16, 2026, 16:57 UTC

   We estimate that approximately 14% of outbound calls and 5% of inbound calls in US West failed between 14:49 UTC and 15:58 UTC. We will follow up as soon as possible with more details.

4. monitoringOct 16, 2026, 16:35 UTC

   We applied mitigation as of 15:58 UTC and SIP outbound connection success has returned to normal. We are continuing to monitor before marking this resolved.

5. identifiedOct 16, 2026, 16:12 UTC

   We have identified the source of the issue and are working to route around the impact.

6. investigatingOct 16, 2026, 16:04 UTC

   We are investigating degraded SIP performance in US West starting at 14:49 UTC affecting new outbound calls.

What APIStatus.watch saw

• Oct 16, 2026, 16:04 UTCoperational → degraded
• Oct 16, 2026, 16:59 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Expo: Elevated iOS submission error ratesMajor · Oct 16, 2026, 14:07 UTC
• Fly.io: Platform Wide Rolling Host RebootsMajor · Oct 16, 2026, 16:22 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• Twilio: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Grafana Cloud: Phone call notifications to numbers in Russia and Kazakhstan are blockedMinor · Oct 13, 2026, 09:23 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to BrazilMinor · Oct 16, 2026, 13:55 UTC
• Twilio: SMS Delivery Delays from a Subset of Twilio Short Codes to Brisanet BrazilMinor · Oct 16, 2026, 14:44 UTC
• OVHcloud: [GRA11][Public Cloud] - Network API incident notificationMinor · Oct 16, 2026, 16:13 UTC

How often does LiveKit have incidents?

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