LiveKit docs › Administration › Regions › Region pinning

---

# Region pinning

> Learn how to isolate LiveKit traffic to a specific region.

## Overview

Region pinning restricts network traffic to a specific geographical region. Use this feature to comply with local telephony regulations or data residency requirements.

There are two options for restricting traffic to a specific region:

- **Protocol-based region pinning**

Signaling and transport protocols include region selection. Use this option with LiveKit realtime SDKs.
- **Region-based endpoint**

Clients connect to a region-specific endpoint. Use this option for telephony applications. To learn more, see [Region pinning for telephony](https://docs.livekit.io/telephony/features/region-pinning.md).

> ℹ️ **Agent deployment regions**
> 
> Region pinning only applies to LiveKit Cloud network traffic. To manage the regions where your agents themselves are deployed, see [Agent deployment regions](https://docs.livekit.io/deploy/admin/regions/agent-deployment.md).

### Protocol-based region pinning

In protocol-based region pinning, region selection information is embedded in the initial signaling and transport messages. When pinning is enabled, if the initial connection is routed to a server outside the allowed regions, the request is rejected. The client then retries the connection using a server in one of the pinned regions.

Region pinning is available for customers on the [Scale plan](https://livekit.com/pricing) or higher.

> 🔥 **Protocol-based region pinning only works with LiveKit realtime SDKs**
> 
> For SIP requests, the server rejects the connection and doesn't retry it. Use [region-based endpoints](https://docs.livekit.io/telephony/features/region-pinning.md#region-based-endpoint) for SIP.

> ℹ️ **When to use protocol-based region pinning**
> 
> When connecting with LiveKit realtime SDKs or when regional data residency (for example, GDPR compliance) is required.

### Enabling protocol-based region pinning

LiveKit must enable region pinning for your project. To request region pinning, sign in to [LiveKit Cloud](https://cloud.livekit.io) and select the **Support** option in the menu.

### Considerations

When you enable region pinning, you turn off automatic failover to the nearest region in the case of an outage.

### Available regions

Regions with more than one location offer automatic **in-region redundancy**, meaning if one location has an outage, traffic reroutes to another location within the same pinned region. Single-location regions keep your traffic in region but don't have in-region redundancy today.

The following regions are available for region pinning:

| ID | Name | Locations | Location count | In-region redundancy |
| `us` | United States | US Central, US East 1, US West | 3 | ✅ |
| `asia` | Asia Pacific | Japan, Singapore | 2 | ✅ |
| `eu` | Europe | France, Germany | 2 | ✅ |
| `india` | India | Mumbai, South India | 2 | ✅ |
| `me` | Middle East | Saudi Arabia, UAE | 2 | ✅ |
| `africa` | Africa | South Africa | 1 |  |
| `aus` | Australia | Australia | 1 |  |
| `il` | Israel | Israel | 1 |  |
| `sa` | South America | Brazil | 1 |  |
| `uk` | United Kingdom | UK | 1 |  |

> ℹ️ **Last updated**
> 
> This list of regions is subject to change. Last updated 2026-05-14.

---

This document was rendered at 2026-06-07T11:35:51.763Z.
For the latest version of this document, see [https://docs.livekit.io/deploy/admin/regions/region-pinning.md](https://docs.livekit.io/deploy/admin/regions/region-pinning.md).

To explore all LiveKit documentation, see [llms.txt](https://docs.livekit.io/llms.txt).