LiveKit incident: Hosted agent builds failing in US East

Affected components

• US East - Cloud Agents

1. postmortemAug 17, 2026, 17:14 UTC

   ### 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 im

2. resolvedAug 14, 2026, 23:01 UTC

   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.

3. monitoringAug 14, 2026, 21:41 UTC

   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.

4. monitoringAug 14, 2026, 21:15 UTC

   We have deployed a mitigation and builds are now successful. We will continue monitoring while we collect any further details to share.

5. identifiedAug 14, 2026, 21:10 UTC

   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.

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.

• Elasticsearch: Increased error rates for microsoft-multilingual-e5-largeMajor · Aug 13, 2026, 08:32 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• OVHcloud: [GRA5/GRA9/GRA11][Compute - Instance] - Some instances incident notificationMajor · Aug 14, 2026, 15:26 UTC
• OVHcloud: [GRA11][Storage] - File storage incident notificationMajor · Aug 14, 2026, 16:07 UTC
• Anthropic: Service disruption on Claude servicesMajor · Aug 14, 2026, 20:30 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Linode: Connectivity Issue - IT-MIL (Milan) data centerMinor · Aug 14, 2026, 20:13 UTC

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