Is LiveKit down?
For agents
proceed
Proceed.
GET upbutler.com/status/livekit/status.agent.json
MCP: upstream_status {"service":"livekit"}
Realtime audio and video infrastructure for voice agents.
What LiveKit reports
Operational
Taken as is from LiveKit's own status page API. Incident titles and component names below are theirs.
Open status.livekit.ioUpButler's independent probe
There is no keyless endpoint of LiveKit that says anything useful, so UpButler does not probe it. To check your own LiveKit account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
LiveKit components
80 operational
- Global Real Time CommunicationOperational
- Cloud Dashboard (cloud.livekit.io)Operational
- Global EgressOperational
- Global IngressOperational
- Global SIPOperational
- Global Cloud AgentsOperational
- Global InferenceOperational
Regional SIP
- US West - SIPOperational
- US East - SIPOperational
- India - SIPOperational
- Brazil - SIPOperational
- Australia - SIPOperational
- Japan - SIPOperational
- US Central - SIPOperational
- Israel - SIPOperational
- Saudi Arabia - SIPOperational
- UAE - SIPOperational
Regional Cloud Agents
- US East - Cloud AgentsOperational
- Europe Central - Cloud AgentsOperational
- India - Cloud AgentsOperational
Regional Inference
- US East - InferenceOperational
- Australia - InferenceOperational
- Europe South - InferenceOperational
- Brazil - InferenceOperational
- South Africa - InferenceOperational
- Singapore - InferenceOperational
- US West - InferenceOperational
- Saudi Arabia - InferenceOperational
- Israel - InferenceOperational
- United Kingdom - InferenceOperational
- Europe Central - InferenceOperational
- US Central - InferenceOperational
- Japan - InferenceOperational
- UAE - InferenceOperational
Regional Phone Numbers
- US Phone NumbersOperational
Regional Analytics Ingestion
- US West - Analytics IngestionOperational
- Brazil - Analytics IngestionOperational
- India - Analytics IngestionOperational
- Japan - Analytics IngestionOperational
- Australia - Analytics IngestionOperational
- Singapore - Analytics IngestionOperational
- US Central - Analytics IngestionOperational
- South Africa - Analytics IngestionOperational
Regional Egress
- Japan - EgressOperational
- US West - EgressOperational
- US East - EgressOperational
- Singapore - EgressOperational
- India - EgressOperational
- UAE - EgressOperational
- Brazil - EgressOperational
- South Africa - EgressOperational
- US Central - EgressOperational
- Saudi Arabia - EgressOperational
Regional Real Time Communication
- Japan - Real Time CommunicationOperational
- Brazil - Real Time CommunicationOperational
- India - Real Time CommunicationOperational
- US West - Real Time CommunicationOperational
- Australia - Real Time CommunicationOperational
- Singapore - Real Time CommunicationOperational
- US Central - Real Time CommunicationOperational
- South Africa - Real Time CommunicationOperational
- UAE - Real Time CommunicationOperational
Regional TURN
- Brazil - TURNOperational
- Japan - TURNOperational
- US West - TURNOperational
- India - TURNOperational
- Australia - TURNOperational
- Singapore - TURNOperational
- US Central - TURNOperational
- South Africa - TURNOperational
- UAE - TURNOperational
Regional Ingress
- US East - IngressOperational
- US West - IngressOperational
- Japan - IngressOperational
- Singapore - IngressOperational
- Australia - IngressOperational
- South Africa - IngressOperational
- Saudi Arabia - IngressOperational
- India - IngressOperational
- Brazil - IngressOperational
LiveKit incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Investigating delayed cloud agent builds in US East | minor | 1 h 6 min | |
| Investigating scaling issue affecting Cloud Agents in EU (Frankfurt) | minor | 47 min |
Tell your outage from LiveKit's
Declare that your project depends on LiveKit. When one of your monitors fails while LiveKit has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- livekitcurl -s https://upbutler.com/status/livekit/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "livekit",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is LiveKit down right now?
- No. As of 2026-10-10 05:08 UTC, LiveKit is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From LiveKit's own status page API at https://status.livekit.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are LiveKit's words.
- How can my agent or app check LiveKit status?
- Fetch https://upbutler.com/status/livekit/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"livekit"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or LiveKit's?
- Add "livekit" to the dependencies of your UpButler workspace. When one of your monitors fails while LiveKit has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in messaging and realtime
UpButler is not affiliated with LiveKit. Status and incident text belong to LiveKit and are read from their public status source; the probe result is UpButler's own measurement.