- 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 51m it lasted.
Anything that failed between 2026-08-14 21:10 UTC and 2026-08-14 23:01 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 5
- identified
New hosted agent builds are failing in US East. Existing agent workloads are not affected. We are currently deploying a mitigation and will follow up with more information shortly.
provider
- monitoring
We have deployed a mitigation and builds are now successful. We will continue monitoring while we collect any further details to share.
provider
- monitoring
The total build error rate has decreased significantly due to the mitigation, but a small percentage of builds in US East are still failing. We are continuing to monitor and will follow up with another update as soon as possible.
provider
- resolved
We pushed a second mitigation at 22:14 UTC and all US East builds have been successful since 22:25 UTC. We will follow up with a postmortem describing the timeline, root cause, and follow ups as soon as possible.
provider
- postmortem
### Summary An issue with the image registry which powers our hosted agents offering temporarily caused new hosted agent builds in US East to fail. Existing agent workloads were not affected, and no sessions or calls were impacted. ### Timeline \(UTC\) * 19:54 - Hosted agent builds begin failing in US East * 20:48 - Our team noticed the increased failure rate and began investigating * 21:04 - First mitigation deployed * 21:08 - Most builds succeeding * 22:14 - Second mitigation deployed, covering the remaining affected infrastructure * 22:24 - All builds succeeding ### Scope of Impact Only new hosted agent builds and deploys in US East were affected. Agents already running were unaffected, as were all sessions, calls, and other regions. Customers who were impacted would have seen their deploy fail with “unable to deploy agent: an error occurred while building your agent, please try again”. ### Mitigations and Follow-ups * We are improving alerting on build failures. * We are improving monitoring of our downstream image registries. We appreciate your understanding and are committed to continuously improving our platform's reliability. If you have any questions, please reach out to our support team.
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-9026dbee0b
Is LiveKit Cloud still down?
No, this incident was resolved 2026-08-14 23:01 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
1h 51m, from 2026-08-14 21:10 UTC to 2026-08-14 23:01 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.