Skip to main content
LiveKit Cloud

Real time communication service degradation in Mumbai

Degraded Lasted 0m · started · LiveKit Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
apac

What to do

  • Check whether you use LiveKit Cloud in apac. 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-03-18 11:25 UTC and 2026-03-18 11:25 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. resolved

    We experienced degraded networking affecting core real time communication services in Mumbai region. The issue began at 06:06 UTC and was resolved by 06:22 UTC on March 18, 2026. All services are now restored and we are continuing to monitor.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-ca915a73c6

Is LiveKit Cloud still down?

No, this incident was resolved 2026-03-18 11:25 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.

How long did it last?

0m, from 2026-03-18 11:25 UTC to 2026-03-18 11:25 UTC, by the times LiveKit Cloud posted.

What was affected?

LiveKit Cloud named in apac.

What caused it?

LiveKit Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

LiveKit Cloud's official status page, https://status.livekit.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.