Skip to main content
LiveKit logo

Is LiveKit Down?

No — LiveKit is up

Reachable from all 8 checked regions

Average response time: 141ms

Last checked · checks run every 6 hours

Official status page: https://status.livekit.io

LiveKit uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
161ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

8-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: no data
Sep 30: no data
Oct 1: no data
Oct 2: no data
Oct 3: no data
Oct 4: no data
Oct 5: no data
Oct 6: 100.00% uptime, 16 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
136ms
DNS 62ms TCP 2ms TLS 20ms TTFB 126ms
arn
52ms
DNS 13ms TCP 1ms TLS 10ms TTFB 47ms
cdg
98ms
DNS 20ms TCP 9ms TLS 17ms TTFB 69ms
dfw
215ms
DNS 76ms TCP 1ms TLS 56ms TTFB 189ms
ewr
82ms
DNS 25ms TCP 1ms TLS 20ms TTFB 73ms
fra
82ms
DNS 37ms TCP 1ms TLS 13ms TTFB 77ms
gru
292ms
DNS 262ms TCP 3ms TLS 12ms TTFB 287ms
iad
173ms
DNS 98ms TCP 1ms TLS 12ms TTFB 156ms

What LiveKit does

LiveKit is an open-source WebRTC platform for realtime audio, video and data, with LiveKit Cloud as its hosted version. Developers use its client SDKs and its Agents framework for Python and Node.js to build voice AI agents, video apps and telephone agents. LiveKit Cloud runs the same open-source server as a global mesh, and adds managed agent hosting, built-in inference, SIP telephony, phone numbers and Egress recording.

What an outage looks like

Clients show a Reconnecting state, video pauses for a few seconds, and other participants appear to leave and rejoin the room. Voice agents take longer to join a session, phone calls carry one-way audio, Egress recordings end early, and Egress, Ingress and API calls slow down. The Cloud dashboard at cloud.livekit.io may fail to load. Many incidents are limited to one region, such as US East or EU Frankfurt.

What to do about it

Check status.livekit.io and find your region: it lists Real Time Communication, TURN, SIP, Egress, Ingress, Cloud Agents, Inference and Analytics Ingestion per region. Let the SDK reconnect on its own and show a notice on its Reconnecting event instead of forcing users to rejoin. Inbound SIP calls on the global endpoint fail over to the next-nearest region automatically, but a region-pinned project does not.

Is it down for everyone, or just you?

If this page says LiveKit is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Twilio
Twilio
Telnyx
Telnyx
ElevenLabs
ElevenLabs
Ably
Ably

LiveKit outage FAQ

Is LiveKit down for everyone or just me?
Check status.livekit.io, which the LiveKit Cloud sign-in page links to, and look at your own region's rows, since most incidents affect one region or one product. LiveKit's Connection Tester at livekit.com/webrtc/connection-test checks whether clients can reach a server. The checks on this page probe livekit.com, the company website, so a fault in your project's media servers or in cloud.livekit.io can happen while they stay green.
Does a LiveKit Cloud outage affect self-hosted LiveKit servers?
No, not directly: every row on the status page is a LiveKit Cloud service. A self-hosted deployment runs the open-source LiveKit server on infrastructure you manage, in the regions you choose, so its health is yours to monitor. Self-hosted agents do not use LiveKit Inference, which is a Cloud feature; they call STT, LLM and TTS providers with your own API keys, so check those providers' status pages when a self-hosted agent stops responding.
What happens to a LiveKit call when the connection drops?
The SDK tries to resume it automatically. It first reconnects the signaling WebSocket and performs an ICE restart, which usually causes little or no disruption, though video can pause for a few seconds. If that fails, it runs a full reconnection: it fires a Reconnecting event, rejoins the room, republishes local tracks and fires Reconnected. Other participants briefly see the user leave and come back.
Will LiveKit resend webhooks my server missed?
Yes, within limits. LiveKit retries each webhook request several times before abandoning it, and when events queue up it delivers them in order, sending newer events only after older ones are delivered or abandoned. Its docs say there is no delivery guarantee, so after a long outage on your side, reconcile room and participant state through the server API instead of relying on webhooks alone.
How long do LiveKit outages usually last?
Most are resolved within a couple of hours. Of the 50 most recent incidents on LiveKit's status page, the median was resolved in about an hour and a half, 36 were closed within four hours, and two stayed open for more than a day. You can subscribe on status.livekit.io by email, text message, Slack, Microsoft Teams, webhook or RSS. Projects on the Ship plan or higher get direct email support.

How we measure this

  • We request LiveKit's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where LiveKit publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when LiveKit goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required