- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on LiveKit Cloud. 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-03-18 18:30 UTC and 2026-03-18 18: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 1
- resolved
A dependency update in our latest docs deployment caused all requests to the MCP server at docs.livekit.io/mcp/ to return 500 errors. The issue began at 18:50 UTC and ended at 19:33 UTC. During this roughly 45 minute window, MCP clients - including IDE integrations and the LiveKit CLI - were unable to connect to the docs MCP server. The issue was caused by a package upgrade that introduced dependencies incompatible with our serverless hosting environment. We rolled back the change and confirmed the endpoint was fully operational at 19:33 UTC. No other services were affected.
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-ea46b39b99
Is LiveKit Cloud still down?
No, this incident was resolved 2026-03-18 18:30 UTC. For LiveKit Cloud's live state, see https://down.guide/livekit.
How long did it last?
0m, from 2026-03-18 18:30 UTC to 2026-03-18 18:30 UTC, by the times LiveKit Cloud posted.
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.