Rejected INVITEs in US East

What to do

• Check whether you use LiveKit Cloud in us. 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 0m it lasted.

  Anything that failed between 2026-04-22 13:00 UTC and 2026-04-22 13:00 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 1

1. resolvedApr 22, 2026, 1:00 PM UTC

   Between 13:15 and 14:25 UTC on April 22, inbound SIP calls routed through our US East region where the toUser field was left empty (approximately 5% of total inbound calls in this region) were rejected by our system due to a failing internal trunk lookup. Upstream carriers surfaced these rejections to end users as 503 "Service Unavailable" responses. A recent change to our internal service responsible for SIP trunk authorization lookups caused trunk queries to return empty results if the toUser field was empty. When our SIP service received an empty trunk lookup, it rejected the inbound INVITE. The regression was deployed to one US region as part of a staged rollout. Our routine checks during the release identified the issue. Once the offending change was rolled back, inbound call rejections returned to baseline within minutes and full service was restored. Other regions and all outbound calls were unaffected. We are introducing a dedicated monitor for this specific failure mode so that any recurrence pages our on-call engineers immediately, rather than relying on broader error-rate signals.

   provider

Corrections

None so far.

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