What changed
On September 8, 2026, Google Cloud made regional endpoints generally available for the Cloud SQL Admin API across MySQL, PostgreSQL and SQL Server. Instead of sending management calls through the global `sqladmin.googleapis.com` endpoint, applications and automation can use a region-specific URL such as `sqladmin.{region}.rep.googleapis.com`. Google says the regional frontend, load balancer, control plane and TLS termination keep the relevant management traffic within the chosen region and isolate one region’s frontend failures from others. The feature had previously been in preview.
Why it matters
Data residency is not only a storage-location question. Provisioning, configuration, metadata and administrative API traffic can cross different infrastructure paths from the database connection itself. Regional Cloud SQL endpoints let teams with sovereignty or regulated-workload requirements keep this control-plane traffic inside the committed region while also reducing dependency on a global API frontend. That gives infrastructure teams a clearer design for workloads governed by controls such as Assured Workloads Regions or ITAR-sensitive regional boundaries.
The regional endpoint replaces a global control-plane route
Cloud SQL automation can now target a regionalized Admin API hostname tied to the database region. Google enforces region matching: requests made through a regional endpoint are scoped to resources in that region rather than behaving as a global inventory surface.
Regional isolation includes frontend and load-balancing infrastructure
Google says each regional endpoint uses regionally isolated frontend and load-balancing infrastructure with a separate regional control plane. A failure in one regional frontend is therefore designed not to affect another region’s endpoint, reducing one class of dependency on global API infrastructure.
TLS terminates inside the region
Certificate management and TLS termination for the endpoint occur on the regional load balancer. Google’s stated design is that API traffic remains encrypted until it reaches the destination region and stays within that region while being processed there.
GA now covers all three Cloud SQL engines
The September release applies to Cloud SQL for MySQL, PostgreSQL and SQL Server. That makes the regional control-plane pattern consistent across mixed database estates rather than forcing one engine onto a different management architecture.
This does not automatically regionalize every dependency
Using a regional Admin API endpoint does not mean every service involved in an application is region-bound. Infrastructure-as-code runners, secrets, logging, monitoring, identity systems and third-party integrations can still create cross-region data paths. Teams should map the full management workflow before treating a database deployment as sovereignty-complete.