LiveKit reported "Intermittent connection timeouts in the Frankfurt region" on its status page at 2026-10-16 10:55 UTC.

When did the incident start and end?

It started at 2026-10-16 10:55 UTC and ended at 2026-10-16 11:59 UTC. It lasted 1 h 4 min.

How do I get alerts for LiveKit?

Subscribe to the LiveKit live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of LiveKit. outages.live reads it every few minutes and keeps every update.

LiveKitIncident · 2026-10-16 10:55 UTC

Intermittent connection timeouts in the Frankfurt region

Q: What is affected?

LiveKit lists these components: Europe Central - Real Time Communication, Regional Real Time Communication - Europe Central - Real Time Communication.

ResolvedOfficial update

This incident is resolved. Connections to the Frankfurt region have returned to normal.

The latest update from LiveKit.

State

Resolved

Started

17 d ago

2026-10-16 10:55 UTC

Lasted

1 h 4 min

until 2026-10-16 11:59 UTC

Worst impact

Degraded

Timeline

3 updates

10:5511:1111:2711:4311:59

DegradedUpdate postedTimes in UTC

Investigating

20 min 32%

Monitoring

44 min 68%

Updates

Times in UTC

As posted by LiveKit

Resolved2026-10-16 11:59 UTC

This incident is resolved. Connections to the Frankfurt region have returned to normal.

Monitoring2026-10-16 11:15 UTC

We have applied a mitigation and new connections should no longer time out. We are monitoring to confirm that connection times have returned to normal.

Investigating2026-10-16 10:55 UTC

We are investigating intermittent timeouts when establishing new connections to our Frankfurt (EU) region. A small percentage of connection attempts may time out. We are working on a mitigation and will post an update as soon as possible.

Affected components

Europe Central - Real Time CommunicationRegional Real Time Communication - Europe Central - Real Time Communication

Follow LiveKit

Your coding agent knows when LiveKit is down, and tells you when a failure is theirs, not yours. You can also get LiveKit incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "livekit" and tell me if LiveKit has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=livekit

Slack

/feed subscribe https://outages.cc/feed.xml?providers=livekit

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane