Skip to main content
LiveKit Cloud

Investigating delayed cloud agent builds in US East

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

Level
confirmed
Worst impact
Degraded
Components
US East - Cloud Agents
Regions
us

What to do

  • Check whether you use LiveKit Cloud US East - Cloud Agents in us. 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 6m it lasted.

    Anything that failed between 2026-10-06 03:46 UTC and 2026-10-06 04:52 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 2

  1. identified

    We are investigating an issue causing some cloud agent builds to be backed up in US East. This issue only impacts new builds for a small number of customers, existing agents are running without any impact.

    provider

  2. resolved

    A fix was applied and all builds are back to normal.

    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-f3960ac73f

Is LiveKit Cloud still down?

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

How long did it last?

1h 6m, from 2026-10-06 03:46 UTC to 2026-10-06 04:52 UTC, by the times LiveKit Cloud posted.

What was affected?

LiveKit Cloud named US East - Cloud Agents in us.

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.