---
service: "LiveKit"
status: "up"
reports_last_hour: 0
reports_last_12_hours: 0
baseline_reports_per_hour: 0
checked_at: "2026-10-31T22:42:22.196Z"
url: "https://instatus.com/now/livekit.io"
official_status_page: "https://status.livekit.io"
website: "https://livekit.io"
---

# Is LiveKit down?

No, it's up. 0 reports in the last hour.

## Official updates

- **Disconnections and failed connections in multiple regions** (RESOLVED, 2026-10-31T07:43:54.000Z): This incident has been resolved. Between 07:10 and 07:43 UTC on October 31, a software bug caused media servers in several regions to restart repeatedly. During this window: - Participants connected to affected servers were disconnected. Impact was heaviest in US East, US Central, US West, Canada and Mexico, where about 18% of participants were disconnected at least once. Many were disconnected more than once, as automatic reconnects landed on servers that then restarted as well. A small share of participants in Europe Central, Europe South, UAE, Saudi Arabia and Israel were also disconnected. Most disconnected participants reconnected automatically, about half within 5 seconds, but each reconnect started a new session rather than resuming the existing one, so participants may have seen repeated audio and video interruptions. Some participants did not reconnect. Participants joining during this window may also have taken longer to connect or failed to join. - Most agents reconnected and continued their conversations, but a small number of agent sessions ended or restarted. Some SIP call transfers also failed. - About 1.3% of Room Service API requests failed during this period. ListParticipants and GetParticipant were the most affected. Some WHIP ingress update and delete requests also failed. The bug was triggered when a specific type of data message was relayed between servers hosting the same multi-region room. We stopped the trigger at 07:43 UTC, and there were no further restarts after that. A fix was deployed to all regions by 08:49 UTC. Apologies for the impact. We will follow up with a postmortem sharing more details on impact and RCA as soon as possible.
- **Investigating failing calls and RoomService API failures in US Central/East and dashboard issues** (RESOLVED, 2026-10-28T23:47:43.000Z): This incident has been resolved. Between 23:30 and 23:58 UTC, a network disruption at an upstream infrastructure provider affected our US East region, with impact also seen in US Central. During this window: Inbound SIP calls in US East and US Central failed at elevated rates, with affected calls rejected with 500 or 503 responses. Answered inbound calls were about 65% below normal across the window, and up to 90% below normal between 23:45 and 23:55 UTC. About 10% of outbound SIP call requests (CreateSIPParticipant) in US East failed, some returning 408 deadline_exceeded. Between 23:28 and 23:58 UTC, there were elevated rates of Room Service, Egress, and Ingress API request server errors in US East. Some participants in US East and US Central saw failed room joins or increased packet loss. The LiveKit Cloud dashboard was inaccessible for part of this window. Network connectivity recovered at approximately 23:58 UTC, and error rates and call volumes returned to normal by 00:20 UTC. A related network issue also affected our much smaller Mexico region from 23:29 UTC, disconnecting active sessions and degrading service until traffic was moved to nearby regions at approximately 01:01 UTC. Sincere apologies for the impact. We will follow up with a postmortem.
- **Investigating reports of elevated RoomService API errors** (INVESTIGATING, 2026-10-06T00:10:10.000Z): We have determined that the elevated API errors are isolated to cross-region traffic between US East and US Central. We will provide further details shortly.

## LiveKit outage FAQ

### Is LiveKit down right now?

No, it's up. 0 reports in the last hour.

### Is LiveKit down for everyone or just me?

It looks like it's just you. Reports for LiveKit are at their usual level, so try reloading, checking your connection, or signing out and back in.

### What problems are people reporting with LiveKit?

Nobody has said what's broken with LiveKit in the last hour. If something isn't working for you, pick it above so others can see.

### When was the last LiveKit outage?

Reports for LiveKit haven't spiked in the last 30 days.

### Does LiveKit have a status page?

Yes. LiveKit posts updates on its official status page, which currently says operational.

[Go to status page](https://status.livekit.io/)

### What can I do if LiveKit isn't working?

Check this page and LiveKit's status page for updates, and wait a few minutes before trying again. Skip reinstalling: if it's an outage, the fix is on their side.

### How do I report a LiveKit problem?

Hit “I have an issue too” at the top of this page and pick what's broken. Your report shows on the live chart within a minute, and you can leave a comment to tell others what you're seeing.

### How does Instatus Now know?

We combine reports from people on this page with LiveKit's official status page, which we check every minute.
