- Level
- confirmed
- Worst impact
- Degraded
- Components
- Japan - Real Time Communication
- Regions
- apac, jp
What to do
Check whether you use LiveKit Cloud Japan - Real Time Communication in apac, jp. 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-07 10:30 UTC and 2026-07-07 10:30 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
- investigating
We are currently investigating increased connection failures affecting our Japan region beginning at 18:18 UTC.
provider
- resolved
Users connecting to our Japan region experienced elevated connection failures between approximately 18:18 and 18:43 UTC, caused by a network disruption affecting connectivity between our Tokyo data centres. Connectivity was restored by 18:43 UTC. Update (July 7): After the initial recovery, one replacement media server in Tokyo came online serving only IPv6. From approximately 22:00 UTC on July 6, connections routed to this server failed for clients on networks without IPv6 connectivity. The server was removed from service at 10:30 UTC on July 7, and connection success rates in Japan have returned to normal.
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-9974e23347
Is LiveKit Cloud still down?
No, this incident was resolved 2026-07-07 10:30 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
0m, from 2026-07-07 10:30 UTC to 2026-07-07 10:30 UTC, by the times LiveKit Cloud posted.
What was affected?
LiveKit Cloud named Japan - Real Time Communication in apac, jp.
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.