Skip to main content
LiveKit Cloud

Monitoring reports of intermittently increased API latency impacting Egress, Ingress, and SIP

Degraded Lasted 1h 5m · started · LiveKit Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Global Egress, Global Ingress, Global SIP
Down Index
19of 100

What to do

  • Check whether you use LiveKit Cloud Global Egress, Global Ingress, Global SIP. 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 1h 5m it lasted.

    Anything that failed between 2026-09-15 22:10 UTC and 2026-09-15 23:15 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. monitoring

    From 21:11 to 21:21 UTC we observed an occurrence of the same incident experienced earlier today impacting Global SIP, Ingress, and Egress due to the same underlying issue. We are currently operating normally and are continuing to monitor.

    provider

  2. resolved

    We have resolved the underlying issue and have not observed any further occurrences of this incident. We will follow up with a detailed postmortem in the original incident.

    provider

  3. postmortem

    Please see a full postmortem [here](https://status.livekit.io/incidents/dbqb4jhxcg9h).

    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-11d3ead132

Is LiveKit Cloud still down?

No, this incident was resolved 2026-09-15 23:15 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.

How long did it last?

1h 5m, from 2026-09-15 22:10 UTC to 2026-09-15 23:15 UTC, by the times LiveKit Cloud posted.

What was affected?

LiveKit Cloud named Global Egress, Global Ingress, Global SIP.

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.