Investigating SIP participant timeouts and signalling connection errors

What to do

• Check whether you use LiveKit Cloud India - Real Time Communication, Australia - Real Time Communication, Singapore - Real Time Communication, US Central - Real Time Communication and 2 more in apac, au, 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 4d 20h it lasted.

  Anything that failed between 2026-04-24 18:12 UTC and 2026-04-29 14:41 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. investigatingApr 24, 2026, 6:12 PM UTC

   We received a single report of CreateSIPParticipant timeouts in Singapore. While investigating this, we discovered an increased rate of signalling connection errors on a very small minority of requests, mainly in India. We haven’t received any other reports, but are proactively creating this incident in case users encounter increased connection latency or failed inbound SIP calls. We are continuing to investigate and will update here once we know more.

   provider

2. identifiedApr 24, 2026, 11:20 PM UTC

   A fix is being implemented. We still have not received any further reports and believe the impact to be minor, but we're continuing to monitor for further issues.

   provider

3. resolvedApr 29, 2026, 2:41 PM UTC

   We are closing this incident as we have not received further reports and the signalling error rate has dropped back to baseline. We made some fine-tuning adjustments to our stack to improve performance and will continue to seek out opportunities to keep latency low.

   provider

Corrections

None so far.

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