- 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 20h 11m it lasted.
Anything that failed between 2026-05-22 20:26 UTC and 2026-05-23 16:36 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 have observed network instability impacting cross-region traffic from Frankfurt beginning at 18:15 UTC. Traffic has been redirected from Frankfurt as of 19:55 UTC. Participants originally connecting via Frankfurt may see slightly increased latency until the region is restored.
provider
- monitoring
We have re-enabled our Frankfurt cluster and are monitoring for further disruptions.
provider
- resolved
We have been monitoring the clusters for the past 16 hours and have not found any further disruptions.
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-108d63d348
Is LiveKit Cloud still down?
No, this incident was resolved 2026-05-23 16:36 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
20h 11m, from 2026-05-22 20:26 UTC to 2026-05-23 16:36 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.