Minor impactResolvedMedia

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

LiveKit reported this minor-impact incident on its official status page on Sep 2, 2026, 21:25 UTC. It was resolved after 20 min.

Right now LiveKit is operational. Live LiveKit status →

🔔 Get alerted when LiveKit has issuesFree · email alerts · no credit card
Sep 2, 2026, 21:25 UTC
started
Sep 2, 2026, 21:45 UTC
resolved
20 min
duration
Minor
impact

Affected components

  • Global SIP
  1. resolvedSep 2, 2026, 21:45 UTC

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

  2. monitoringSep 2, 2026, 21:25 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.

  3. investigatingSep 2, 2026, 21:03 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.

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.

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

LiveKit incident on Sep 2, 2026: Investigating reports of one-way audio issues in LiveKit Phone Numbers · APIStatus.watch