LiveKit reported this critical-impact incident on its official status page on Apr 3, 2026, 17:13 UTC. It was resolved after 9 min.
Right now LiveKit is operational. Live LiveKit status →
**Root Cause** A gap in our DNS update process resulted in a misconfiguration of the DNS for [livekit.io](http://livekit.io), causing several A records to be overwritten. This resulted in an incorrect IP address being returned for [livekit.io](http://livekit.io). All real-time services - calls, RTC, and hosted agents - were unaffected as they operate on separate domains. We do have DNS monitoring in place, but it was not configured to page on-call. As a result, the issue was identified by LiveKit engineering after a short delay. **Timeline** * **2026-04-03 17:46 UTC**: DNS configuration change applied; resolution begins failing for [livekit.io](http://livekit.io). * **2026-04-03 17:52 UTC**: Issue identified by LiveKit. * **2026-04-03 18:15 UTC**: Root cause identified and fix applied. * **2026-04-03 18:18 UTC**: Fix fully propagated; services restored. Total duration: ~32 minutes. **Mitigations** * Enforce tighter automated guardrails around DNS updates. * Enable paging on ex
A fix has been implemented and we are monitoring the results. All users should now be able to access the Cloud Dashboard.
We are currently investigating this issue and will update as soon as we know more.
Our 5-minute checks didn't record a change in LiveKit's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
LiveKit reported 18 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 31m. See LiveKit's uptime and incident history