# Japan-only pinning on Scale, and a Japan data region: follow-up to #1798

**URL:** <https://community.livekit.io/t/japan-only-pinning-on-scale-and-a-japan-data-region-follow-up-to-1798/2088>\
**Category:** Getting Started\
**Tags:** livekit-cloud\
**Created:** [September 18, 2026, 5:32am UTC](https://community.livekit.io/t/japan-only-pinning-on-scale-and-a-japan-data-region-follow-up-to-1798/2088 "2026-09-18T05:32:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![m.yusa](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@m.yusa](https://community.livekit.io/u/m.yusa)\
**Post date:** [September 18, 2026, 5:32am UTC](https://community.livekit.io/t/japan-only-pinning-on-scale-and-a-japan-data-region-follow-up-to-1798/2088/1 "2026-09-18T05:32:13Z")

</div>

Hi,

In this thread, a LiveKit staff member mentioned that pinning a project to Japan specifically is possible:

> [@Scoping UDP media ports to the static IP ranges — and what asia pinning actually covers](https://community.livekit.io/t/scoping-udp-media-ports-to-the-static-ip-ranges-and-what-asia-pinning-actually-covers/1798):
>
> Hi all, We’ve just finished a PoC on LiveKit Cloud for our video conferencing product and are preparing to move it into production. We’re on Build today and will upgrade to Scale. Our users are all in South Korea, so we plan to request region pinning. We’re now at the stage of getting corporate firewalls opened, both on our own network and at enterprise customers with strict egress allowlists. Those requests take time and are hard to revise later, so I’d like to get the details right first…

We’re moving a 1:1 video app with users only in Japan to LiveKit Cloud, and plan to upgrade our production project from Build to Scale. We need to keep realtime traffic within Japan and, if possible, stored data as well. We understand and accept that a pinned project has no cross-region failover.

What we’ve checked in the docs:

- “Region pinning”: pinning is on Scale and is enabled via Support
- “Regions, regional endpoints, and static IPs”: the region groups table lists Japan only inside `asia`; the static IPs section documents regional addresses such as `<subdomain>.japan.rtc.livekit.cloud` ([https://docs.livekit.io/deploy/admin/regions/endpoints.md#static-ips](https://docs.livekit.io/deploy/admin/regions/endpoints.md#static-ips))
- “Configuring firewalls”: the hostname list includes otokyo1a, otokyo1b, oosaka1a and oosaka1b
- “EU data residency”: the project data region can be US or EU, fixed at creation

1. Is Japan-only pinning available as a supported option on Scale (yes / no / case by case)?
2. Which locations would serve a Japan-pinned project: Tokyo only, or Tokyo and Osaka? Is there any failover within Japan?
3. Roughly how long does it take to enable after a Support request, and does the Project URL change?
4. Is there any way, on any plan including Enterprise, to have the project data region (session analytics) in Japan? If not, is one planned?
5. Does connecting through `<subdomain>.japan.rtc.livekit.cloud` keep realtime traffic in Japan on any plan (including Build and Ship)? And how does it relate to region pinning: is it a complement to pinning, or an alternative to it?

Thanks!

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [September 28, 2026, 8:57am UTC](https://community.livekit.io/t/japan-only-pinning-on-scale-and-a-japan-data-region-follow-up-to-1798/2088/2 "2026-09-28T08:57:03Z")

</div>

Hi, to give you an honest answer, you are asking about specific details about our infrastructure to a level that isn’t publicly documented so if I answer with specifics, what is accurate today may not be accurate to someone reading this answer in the future.

The official answer would be that we only offer protocol-based region-pinning for `asia` which covers Japan and Singapore.

> [@m.yusa](#):
>
> 1. Does connecting through `<subdomain>.japan.rtc.livekit.cloud` keep realtime traffic in Japan on any plan (including Build and Ship)?

If your users are outside of Japan, this will cause them to connect through the Japan endpoint, I would then expect all traffic to remain within Japan, but it would not be strictly guaranteed.

> [@m.yusa](#):
>
> 1. Is there any way, on any plan including Enterprise, to have the project data region (session analytics) in Japan? If not, is one planned?

Session analytics is stored in the **project’s data region** , which is either the US or EU - we do not currently offer other data regions outside of this.

Are you looking to meet some compliance requirements by limiting your data to Japan-only?

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\
**Post date:** [October 13, 2026, 8:57am UTC](https://community.livekit.io/t/japan-only-pinning-on-scale-and-a-japan-data-region-follow-up-to-1798/2088/3 "2026-10-13T08:57:20Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
