Investigating reports of one-way audio issues in LiveKit Phone Numbers

What to do

• Check whether you use LiveKit Cloud Global SIP. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.

  Anything that failed between 2026-09-02 21:25 UTC and 2026-09-02 21:45 UTC may need a replay.

• Subscribe to LiveKit Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=livekit works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LiveKit Cloud 3

1. investigatingSep 2, 2026, 9:03 PM UTC

   We are investigating elevated issues in calls connected to LiveKit Phone numbers where callee audio is not being heard by the caller. This is currently only experienced for numbers issues by LiveKit, and no other SIP provider connectivity should be affected. Our team is actively investigating this.

   provider

2. monitoringSep 2, 2026, 9:25 PM UTC

   An upstream carrier reverted a codec change that was causing one-way audio issues on calls to LiveKit-issued phone numbers. As of 21:10 UTC calls are connecting normally and we are no longer seeing the issue. The upstream codec change has impacted calls from T-Mobile and AT&T carriers. No other SIP providers were affected. We are monitoring before marking this resolved.

   provider

3. resolvedSep 2, 2026, 9:45 PM UTC

   This incident has been resolved. We will follow up with a detailed postmortem as soon as possible.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.