Skip to main content
LiveKit Cloud

Elevated latency in Hyderabad region

Degraded Lasted 2h 2m · started · LiveKit Cloud's page

Level
confirmed
Worst impact
Degraded
Components
India - SIP, India - Ingress
Regions
apac, in

What to do

  • Check whether you use LiveKit Cloud India - SIP, India - Ingress in apac, 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 2h 2m it lasted.

    Anything that failed between 2026-06-05 09:06 UTC and 2026-06-05 11:08 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. investigating

    We're investigating elevated latency affecting Ingress and SIP services in our Hyderabad region.

    provider

  2. investigating

    As of 09:21 UTC, we've applied a mitigation by routing traffic away from the Hyderabad region. Latency rates are returning to normal levels. We're continuing to monitor the issue.

    provider

  3. resolved

    We identified a connectivity problem in the Hyderabad cluster. As mitigation, we've drained the cluster to route traffic away from it. Mumbai traffic is unaffected and serving normally. We'll undrain Hyderabad once we're confident it's functioning normally.

    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-757d7a0dc2

Is LiveKit Cloud still down?

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

How long did it last?

2h 2m, from 2026-06-05 09:06 UTC to 2026-06-05 11:08 UTC, by the times LiveKit Cloud posted.

What was affected?

LiveKit Cloud named India - SIP, India - Ingress in apac, in.

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.