- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use LiveKit Cloud 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 5m it lasted.
Anything that failed between 2026-08-07 21:22 UTC and 2026-08-07 22:27 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
- investigating
We are currently investigating automated alerting which triggered for degraded Room service performance in the US West and US Central regions beginning around 19:45 UTC. We are working to determine if there is any customer-facing impact. If there is impact, we don't currently have reason to believe that it is widespread. We will update again within 30 minutes.
provider
- monitoring
We have applied a mitigation to the affected regions and are now monitoring to ensure that performance signals return to baseline. We are still working on determining impact (including how users can determine if they were affected) and will share those details as soon as possible.
provider
- resolved
This incident has been resolved. Between 19:45 and 20:00 UTC, calls crossing the US West US Central link experienced intermittent degradation in Room Service and SIP performance. The underlying network between the two regions had episodes of high packet loss during this time period. We rerouted traffic and performance has returned to baseline as of 22:00 UTC. We will follow up with a postmortem, which will include further details regarding scale and scope.
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-cf8bb4f31b
Is LiveKit Cloud still down?
No, this incident was resolved 2026-08-07 22:27 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
1h 5m, from 2026-08-07 21:22 UTC to 2026-08-07 22:27 UTC, by the times LiveKit Cloud posted.
What was affected?
LiveKit Cloud named 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.