Loading status…
Loading status…
LiveKit status · Communication · checked (4s ago)
Also searched as LiveKit Cloud.
No — LiveKit is not down. All LiveKit systems are reported operational.
According to LiveKit's official status page, LiveKit was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, LiveKit's feed reported no outage in 100.00% of our checks.
Everything above is read from LiveKit's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported LiveKit in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
LiveKit provides realtime audio and video infrastructure — WebRTC rooms, an SFU, and the agents framework used to put voice AI into calls. LiveKit Cloud is the hosted version; the server is also open source and widely self-hosted.
The status page covers LiveKit Cloud and reports regionally, which matters because participants connect to the nearest edge. A self-hosted LiveKit server is not covered here at all. Media quality problems — jitter, packet loss, one participant sounding bad — are network conditions rather than service state, and no status page reports them.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where LiveKit's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days LiveKit was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 4s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of LiveKit's status endpoint.
LiveKit has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what LiveKit posted itself — not every problem users hit.
postmortem · Sep 15, 10:10 PM (4d ago)
postmortem · Sep 15, 05:04 PM (4d ago)
resolved · Sep 15, 12:08 PM (4d ago)
postmortem · Sep 5, 11:36 PM (14d ago)
resolved · Sep 4, 10:00 AM (15d ago)
resolved · Sep 2, 09:03 PM (17d ago)
resolved · Sep 2, 08:15 AM (17d ago)
resolved · Aug 26, 10:44 AM (24d ago)
resolved · Aug 24, 10:11 AM (26d ago)
resolved · Aug 21, 09:00 AM (29d ago)
postmortem · Aug 20, 09:10 PM (30d ago)
resolved · Aug 19, 07:33 PM (31d ago)
postmortem · Aug 17, 06:10 PM (33d ago)
postmortem · Aug 14, 09:10 PM (36d ago)
resolved · Aug 13, 08:42 PM (37d ago)
resolved · Aug 12, 06:34 PM (38d ago)
resolved · Aug 7, 09:22 PM (43d ago)
resolved · Aug 6, 07:47 PM (44d ago)
resolved · Aug 4, 08:45 PM (46d ago)
resolved · Aug 3, 03:30 PM (47d ago)
Most connection failures are the client's network: corporate firewalls block UDP and force TURN relaying, which degrades quality without failing. An expired or wrongly-scoped access token fails to join a room with an error that reads as a service fault. Browser permissions for camera and microphone are a common cause of a participant joining silently with no media.
LiveKit is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.