Minor impactResolvedMedia

LiveKit incident: Elevated latency in Hyderabad region

LiveKit reported this minor-impact incident on its official status page on Jun 5, 2026, 09:06 UTC. It was resolved after 2h 2m.

Right now LiveKit is operational. Live LiveKit status →

🔔 Get alerted when LiveKit has issuesFree · email alerts · no credit card
Jun 5, 2026, 09:06 UTC
started
Jun 5, 2026, 11:08 UTC
resolved
2h 2m
duration
Minor
impact

Affected components

  • India - Ingress
  • India - SIP

Timeline

updates from LiveKit's status page ↗
  1. resolvedJun 5, 2026, 11:08 UTC

    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.

  2. investigatingJun 5, 2026, 10:05 UTC

    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.

  3. investigatingJun 5, 2026, 09:06 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LiveKit's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does LiveKit have incidents?

LiveKit reported 18 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 31m. See LiveKit's uptime and incident history

← Previous: Degraded Connectivity in US Central (Jun 2, 2026)Next: Intermittent errors for Google Gemini models via Inference (Jun 11, 2026) →
LiveKit incident on Jun 5, 2026: Elevated latency in Hyderabad region · APIStatus.watch