- Level
- confirmed
- Worst impact
- Degraded
- Components
- United Kingdom - Real Time Communication
- Regions
- eu
What to do
Check whether you use LiveKit Cloud United Kingdom - Real Time Communication 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 52m it lasted.
Anything that failed between 2026-07-14 09:49 UTC and 2026-07-14 10:41 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 2
- monitoring
Between 08:54 am and 09:06 am UTC, 5.4% of room service api requests in our London region failed with errors. A fix was applied and error rates returned to normal by 09:06 am UTC. We are continuing to monitor.
provider
- resolved
Error rates for room service api requests in our London region have remained normal since 09:06 am UTC and we are no longer seeing any issues.
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-3e81afe8dc
Is LiveKit Cloud still down?
No, this incident was resolved 2026-07-14 10:41 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
52m, from 2026-07-14 09:49 UTC to 2026-07-14 10:41 UTC, by the times LiveKit Cloud posted.
What was affected?
LiveKit Cloud named United Kingdom - Real Time Communication 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.