- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
What to do
Check whether you use LiveKit Cloud in eu. 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 0m it lasted.
Anything that failed between 2026-07-23 08:00 UTC and 2026-07-23 08:00 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 1
- resolved
On July 23, between 07:50 and 08:07 UTC, media servers in our London region experienced a host-level network fault, causing them to fail health checks and restart. Users connected to these servers may have experienced brief connection interruptions, and egress operations may have seen increased latency. The affected servers were removed and replaced. The region has been operating normally since.
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-a8c5b022ee
Is LiveKit Cloud still down?
No, this incident was resolved 2026-07-23 08:00 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
0m, from 2026-07-23 08:00 UTC to 2026-07-23 08:00 UTC, by the times LiveKit Cloud posted.
What was affected?
LiveKit Cloud named in eu.
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.