Elevated rate of egress ending early in India region

What to do

• Check whether you use LiveKit Cloud India - Egress in in. 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 10h 54m it lasted.

  Anything that failed between 2026-06-16 09:49 UTC and 2026-06-16 20:42 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. monitoringJun 16, 2026, 9:49 AM UTC

   We identified an issue in the India region where a small number of active sessions may have ended earlier than expected. Affected sessions could experience egress recordings stopping mid-session. We've deployed a mitigation and are monitoring to confirm resolution. Other regions are unaffected.

   provider

2. resolvedJun 16, 2026, 8:42 PM UTC

   We have not seen further instances of this issue since the mitigation was applied. We will follow up with a postmortem as soon as possible.

   provider

3. postmortemJun 23, 2026, 5:46 PM UTC

   **Summary** Between June 5 and June 16, 2026, an intermittent loss of connectivity between internal systems caused room state to be altered incorrectly in a single region in India. As a result, a small number of active sessions in that region ended earlier than expected, and affected egress recordings could stop mid-session. While the intermittent issue was undetected for some time, the impacted number of egresses was low and limited to the one affected region in India - other regions were unaffected. **Timeline \(UTC\)** * 2026-06-05 05:00 - Intermittent loss of connectivity between internal systems begins causing room state to be incorrectly altered in one India region, leading to some egresses being terminated prematurely. * 2026-06-16 06:45 - Mitigation was deployed and monitoring began. Eligible connections were moved to a different region and added redundancy was deployed to the affected internal tooling. * 2026-06-16 20:42 - No further instances were observed since the mitigation was applied. Incident was marked resolved. **Resolution** We mitigated the outage by moving eligible connections to a different region and by adding redundancy to the affected internal tooling so it could better tolerate intermittent connectivity loss. As a longer-term fix, we hardened the communication channels between the involved systems. We have not observed any further occurrences since the mitigation was applied, and we are continuing to evaluate additional improvements to our tolerance for this class of failure.

   provider

Corrections

None so far.

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