Is LiveKit Cloud down? › Outage history › May 6, 2026

LiveKit Cloud partial outage on May 6, 2026: what happened

On May 6, 2026, the LiveKit status page reported "Outbound SRTP calls are failing". About 3 hours 18 min: from May 6, 2026, 19:46 UTC to May 6, 2026, 23:04 UTC, by the official start and resolution times.

LiveKit Cloud right now

At our last refresh (Oct 22, 2026, 12:35 UTC) LiveKit Cloud was up: All Systems Operational.

Is LiveKit Cloud down right now? →
Started
May 6, 2026, 19:46 UTC
Resolved
May 6, 2026, 23:04 UTC
Duration
3 hours 18 min
Official impact
Major
Affected
Global SIP
Source
Outbound SRTP calls are failing on the LiveKit status page

The LiveKit status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the LiveKit Cloud partial outage?

"A recent code change introduced a regression in how SIP trunk encryption settings were applied to outgoing calls. SIP trunks configured to require SRTP had that requirement silently dropped on outbound INVITEs when the per-call request did not also explicitly set an encryption mode."

From the LiveKit status page, incident report, May 10, 2026, 15:11 UTC.

When was it fixed?

The LiveKit status page marked it resolved at May 6, 2026, 23:04 UTC, 3 hours 18 min after it started. A fix was in place and being monitored from May 6, 2026, 20:05 UTC. Its resolution note: "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."

Timeline of official updates

Every update the LiveKit status page posted, oldest first. Times are UTC.

  1. May 6, 2026, 19:46 UTC investigating

    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.

  2. May 6, 2026, 20:05 UTC monitoring

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

  3. May 6, 2026, 20:32 UTC monitoring

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

  4. May 6, 2026, 23:04 UTC resolved

    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.

The official incident report

Published May 10, 2026, 15:11 UTC. The opening of the report; the full text is on the official page.

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`, or `Media Encryption Required`. - Identifying impact: Customers can search their call records during the window for failed outbound calls returning `488` from their carrier with one of the above reason phrases. Root cause A recent code change introduced a regression in how SIP trunk encryption settings were applied to outgoing calls. SIP trunks configured to require SRTP had that requirement silently dropped on outbound INVITEs when the per-call request did not also explicitly set an encryption mode. As a result, outbound calls were sent without SRTP, and carriers that were configured to expect SRTP on TLS correctly rejected them. Timeline \(UTC\) - 18:07 - Production deployment containing the regression went live. - 18:39 - Internal monitoring paged on a periodic end to end functionality test. - 19:42 - ...

Read the full report on the LiveKit status page

LiveKit Cloud partial outage questions

What caused the LiveKit Cloud partial outage on May 6, 2026?

In its incident report (May 10, 2026, 15:11 UTC), the LiveKit status page said: "A recent code change introduced a regression in how SIP trunk encryption settings were applied to outgoing calls. SIP trunks configured to require SRTP had that requirement silently dropped on outbound INVITEs when the per-call request did not also explicitly set an encryption mode."

When was the LiveKit Cloud partial outage on May 6, 2026 fixed?

The LiveKit status page marked it resolved at May 6, 2026, 23:04 UTC, 3 hours 18 min after it started. A fix was in place and being monitored from May 6, 2026, 20:05 UTC. Its resolution note: "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."

How long did the LiveKit Cloud partial outage last?

About 3 hours 18 min: from May 6, 2026, 19:46 UTC to May 6, 2026, 23:04 UTC, by the official start and resolution times.

Was LiveKit Cloud completely down?

No. The LiveKit status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: Global SIP.

Which parts of LiveKit Cloud were affected?

The LiveKit status page listed: Global SIP.

Other recent LiveKit Cloud incidents

Full LiveKit Cloud outage history and biggest outages → · Recent outages across all services →

Quotes are the LiveKit status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with LiveKit Cloud. Times are UTC.