LiveKit outage: Outbound SRTP calls are failing

Affected components

• Global SIP

1. postmortemMay 10, 2026, 15:11 UTC

   **Summary** On 2026-05-06 between 18:07 and 19:56 UTC, a code change to the API server which handles CreateSIPParticipant calls caused outbound calls to incorrectly inherit their encryption settings from outbound trunks. This resulted in calls that didn't specify an encryption setting in the request itself to be sent without SRTP, even if the LiveKit trunk was configured to require it. If users had configured their carrier’s trunk to expect SRTP \(by enabling Twilio’s Secure Trunking, for example\) those INVITEs were rejected. Approximately 2% of global outbound SIP calls were affected during the incident window. **Impact** - Window: 2026-05-06 18:07 - 19:56 UTC - Scope: Outbound TLS calls where the encryption setting was not set in the request and the carrier was configured to expect SRTP. - Customer symptom: Outbound calls failed at the carrier with `488` rejections such as Twilio's `32208 SIP trunk or domain is required to use secure media (SRTP)`, `Not Acceptable Here`

2. resolvedMay 6, 2026, 23:04 UTC

   We are resolving this incident as we have not observed any additional errors since the fix was rolled out. We will follow up with a postmortem as soon as possible.

3. monitoringMay 6, 2026, 20:32 UTC

   We believe this incident was not provider-specific and as such have removed Twilio from the incident title.

4. monitoringMay 6, 2026, 20:05 UTC

   A fix has been implemented and we are monitoring the results. The issue persisted from 18:10 - 19:58 UTC.

5. investigatingMay 6, 2026, 19:46 UTC

   We have noted that outbound calls with both TLS and media encryption enabled via Twilio are failing. We are currently investigating and will update here as soon as we know more.

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.

• CircleCI: Some Pipelines are being lostMajor · May 6, 2026, 19:42 UTC
• Pinecone: [AWS][us-east-1] 5xx errors for some requests on some indexesMajor · May 6, 2026, 20:02 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Mailgun: Automatic Sender Security Records Not ProvisioningMinor · May 6, 2026, 15:40 UTC
• Snyk: Issues API DelaysMinor · May 6, 2026, 20:45 UTC
• MongoDB Atlas: Atlas Backup Export Jobs Degraded PerformanceMinor · May 6, 2026, 21:48 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