Firestore Regional Endpoints Hit GA

Firestore’s regional and multi-regional API endpoints are now generally available. If your workload has data-residency requirements, the feature you’ve been waiting for is finally in production.

Key Takeaways

• Regional and multi-regional endpoints for the Firestore API are now GA, out of preview (Firebase Release Notes, June 2026).
• These endpoints enforce that requests are transmitted, stored, and processed within a single designated region — not just stored there.
• Support is limited to server-side SDKs: C#, Go, Java, Node.js, PHP, Python, and Ruby. Mobile and web SDKs are not supported.
• Locational endpoints are deprecated. If your server code targets one, migrate to a regional or multi-regional endpoint now.
• Private Service Connect backends work with the new regional endpoints for setups that need traffic off the public internet entirely.

What a regional endpoint actually enforces

A standard Firestore client routes through Google’s global infrastructure. Traffic may transit regions outside your database’s home location before a request completes. For most apps, that’s fine. For apps under GDPR, HIPAA, or data-sovereignty mandates specific to a country or jurisdiction, it’s a compliance gap.

A regional endpoint changes that: transmission, processing, and storage must all occur in the designated region. The endpoint format encodes the location directly — firestore.us-central1.rep.googleapis.com routes all traffic through us-central1, and the server enforces it. Multi-regional endpoints follow the same pattern but cover a broader geographic zone. GA status means SLAs now back it in production.

SDK support and the mobile gap

Configure the regional endpoint when you initialize the server client library. The method is the same across all supported server SDKs — pass the endpoint string at init time. Firebase’s regional endpoints documentation has initialization examples for each supported language.

Mobile and web SDKs are not supported. Android, iOS, and JavaScript clients route through the standard global endpoint regardless of any server-side configuration. If true regional isolation is required end-to-end, you need a server-side intermediary that uses the regional endpoint; the client alone can’t enforce it.

Action item: locational endpoints are deprecated

The older locational endpoint format is out. If your server code targets one of those, migrate to the new regional or multi-regional format. Firebase hasn’t published a shutdown date yet, but GA for the replacement usually means the deprecated path is on a clock. Migrate now.

Private Service Connect users can connect to regional and multi-regional endpoints through PSC backends, keeping traffic entirely within private network boundaries while still enforcing regional routing.

The change is available now across all supported server SDKs. If you have residency requirements, switch the endpoint string. There’s nothing else to wait for.