# LiveKit: Incident updated: Degraded SIP Performance in US West

> Incident updated: Degraded SIP Performance in US West. Detected 2026-10-22 by Rewindex: what changed on LiveKit’s status page, with the before/after diff.

Canonical: https://rewindex.com/change/rd167b7b1e71fb5
Last updated: 2026-10-22T14:33:50Z

**Summary:** _summary pending_
- Kind: Incident update · Label: Normal progress (rule)
- Changed: 2026-10-22 14:33 UTC · Detected: 2026-10-22 14:33 UTC
- [Source: https://stspg.io/dwszh1v29gsq](https://stspg.io/dwszh1v29gsq)
- [Company: LiveKit](https://rewindex.com/company/livekit.md)
- Versions: before incident\_version:666/03776y0cfgxq@2695b34ef5da → after incident\_version:666/03776y0cfgxq@bead02f8354d
- Change 2 of 2 for this incident

Incident page (full timeline): [Degraded SIP Performance in US West](https://rewindex.com/company/livekit/incidents/03776y0cfgxq.md)
## What changed

**1. Changed: Status**

```diff
- resolved
+ postmortem
```

**2. Added: Update** (postmortem) · 2026-10-22 14:26 UTC

```diff
+ 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 - Second affected SIP server started with an IPv6 address 2026-10-16 ~15:48 - Customers began reporting failures to our support team 2026-10-16 15:58 - SIP traffic began moving away from the final affected cluster due to automatic cluster draining 2026-10-16 15:59 - Last affected call; customer impact ended 2026-10-16 17:08 - Began rolling out the long term fix requiring the usage of IPv4 2026-10-16 ~21:28 - Fix rollout completed 2026-10-16 ~22:30 - SIP traffic restored to the affected cluster Scope of Impact Between 14:49 and 15:59 UTC on 2026-10-16, SIP calls handled by the two affected servers in US West failed. During that window, about 14% of outbound calls in US West were rejected at setup and about 5% of inbound calls were answered and then dropped without audio. Detection and Response Our customers noticed this before our monitoring did. Our alerts watch for error-level logs, but carrier rejections are logged as routine events since they happen during normal operation. We also weren't tracking call failure rates on individual servers so our on-call engineers were paged in manually about an hour after the first failure. Mitigations and Follow-ups We deployed a fix so SIP servers only use IPv4 addresses when determining their public address. We'll add safeguards and automated tests to ensure a SIP server's call setup messages only contain IPv4 addresses. We are additionally adding improvements in monitoring so that we can proactively detect and prevent these sorts of failures. We apologize for the disruption this caused. We appreciate your understanding and are committed to continuously improving our platform's reliability. If you have any questions, please reach out to our support team.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-10-19 20:53 UTC | [Incident silently edited: Degraded SIP Performance in US West](https://rewindex.com/change/r2647288c3866b7.md) | Wording only |
| 2026-10-22 14:33 UTC | Incident updated: Degraded SIP Performance in US West (this change) | Normal progress |

Previous: [change](https://rewindex.com/change/r2647288c3866b7.md) · All LiveKit changes: [timeline](https://rewindex.com/company/livekit/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._

## Cite this

Incident updated: Degraded SIP Performance in US West on LiveKit’s status page, changed 2026-10-22 14:33 UTC (change 2 of 2).

- Canonical URL: https://rewindex.com/change/rd167b7b1e71fb5
- Citation: LiveKit, “Incident updated: Degraded SIP Performance in US West” (2026-10-22 14:33 UTC). Archived by Rewindex: https://rewindex.com/change/rd167b7b1e71fb5 (CC BY 4.0).
- Markdown link: `[LiveKit: Incident updated: Degraded SIP Performance in US West (2026-10-22)](https://rewindex.com/change/rd167b7b1e71fb5)`


---
Canonical: https://rewindex.com/change/rd167b7b1e71fb5 · Markdown: https://rewindex.com/change/rd167b7b1e71fb5.md · JSON: https://rewindex.com/api/v1/changes/rd167b7b1e71fb5 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-11T04:21:16.351Z