Regions, regional endpoints, and static IPs

Overview

LiveKit Cloud is available in multiple regions around the world. Some deployments require traffic to remain within a specific region or use predictable IP ranges for firewall rules, compliance, or data residency requirements. This topic describes the available regions, static IP ranges, and the services to which they apply.

Region groups for protocol-based region pinning

A region group is a named group of LiveKit Cloud locations. You can pin a project to a region group to keep its realtime traffic within a specific area for compliance or data residency requirements.

Regions with more than one location offer automatic in-region redundancy: if one location has an outage, traffic reroutes to another location within the same region. Single-location regions keep traffic in region but don't have in-region redundancy, so they can't offer the same availability guarantees.

The following region groups are available for protocol-based region pinning with realtime SDKs:

Region-based endpoints for SIP

By default, SIP endpoints are global and LiveKit routes each call through the region closest to its origination point. A region-based endpoint directs traffic only to nodes within a single region instead. Use one to keep inbound calls inside a specific region, for example to comply with local telephony regulations or data residency requirements.

The endpoint format is as follows:

{sip_subdomain}.{region_name}.sip.livekit.cloud

Where {sip_subdomain} is your LiveKit SIP URI subdomain and {region_name} is one of the following regions:

Destination country for outbound calls

You can limit outbound calls to a specific region by setting the destination_country parameter. When destination_country is set, outbound calls originate from a server within the specified country. To learn more about how this parameter works, see Outbound calls in the Region pinning for telephony topic.

The following table includes the list of supported regions and two-letter country codes  for the destination_country parameter:

Static IPs

Static IP ranges let you allowlist LiveKit Cloud traffic in a firewall without using wildcard domains. They're currently available for the following regions:

Static IPs apply to the following services:

• Realtime
• SIP signaling and media
• Webhooks

Seeing IPs outside the expected region

LiveKit's default DNS address, like <subdomain>.livekit.cloud, resolves to the cluster closest to the connecting client. If the client is outside a region with static IPs, that cluster might not be covered by the static IP ranges above.

To force connections into a covered region, connect using regional addresses:

• <subdomain>.canada.rtc.livekit.cloud
• <subdomain>.eu.rtc.livekit.cloud
• <subdomain>.india.rtc.livekit.cloud
• <subdomain>.japan.rtc.livekit.cloud
• <subdomain>.us.rtc.livekit.cloud

The same region prefix works for service-specific subdomains, including *.eu.turn.livekit.cloud and *.eu.sip.livekit.cloud. Region DNS only exists with a service in the name; there is no eu.livekit.cloud without a service prefix.

For example, if your project is region-pinned to the US and an end user connects from London, the default <subdomain>.livekit.cloud lookup might resolve to a London cluster outside the static IP range. Pointing the client to wss://<subdomain>.us.rtc.livekit.cloud keeps the connection on US infrastructure and inside the static range.

For details on protocol-level region selection, see Region pinning.

Static IP coverage for TURN

In regions with static IPs, traffic for all services, including TURN, egresses from the static IP ranges as long as the client connects via a regional endpoint such as *.eu.turn.livekit.cloud.

Outside those regions, traffic for TURN and other services egresses from cluster IPs that aren't part of the static guarantee.

Agent deployment regions

An agent deployment is isolated to a single region, but you can deploy an agent to multiple regions. The following regions are currently available for agent deployments:

Additional resources

The following topics provide more information about regions, endpoints, and firewalls.