Cloud SQL private IP: allocated IP range is exhausted / private services access not configured
Creating a private-IP instance fails because the VPC peering range is missing, too small or conflicts.
Cloud SQL private IP allocated range exhaustedPrivate service access not configuredAn allocated IP range was exhaustedFailed to create subnetwork. Couldn't find free blocks in allocated IP rangesservicenetworking.googleapis.com peering Meaning
Reserve an IP range for private services access (gcloud compute addresses create --purpose=VPC_PEERING --prefix-length=16) and create the peering (gcloud services vpc-peerings connect). Increase or add ranges if full; ensure ranges don't overlap with on-prem or other peerings.
Common causes
- No private services access configured
- Allocated range too small or used up
- Overlapping ranges
- Peering deleted by mistake
- Org policy blocking peering
⚡ Quick fix
- Allocate a /16 range and create the VPC peering
- Add another allocated range if exhausted
- Resolve overlaps
Detailed fix by platform
Shell
- bash
gcloud compute addresses create google-managed-services --global --purpose=VPC_PEERING --prefix-length=16 --network=NET gcloud services vpc-peerings connect --service=servicenetworking.googleapis.com --ranges=google-managed-services --network=NET
How to diagnose
- Range — Allocated?
- Peering — Active?
- Overlap — None?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- CannotPullContainerError ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried
- Cloud NAT Cloud NAT: OUT_OF_RESOURCES dropped connections (port exhaustion)
- Cloud SQL: failed to connect to instance Cloud SQL: failed to connect to `host=PROJECT:REGION:INSTANCE user=app database=db`: dial error (timeout) / Cloud SQL Auth Proxy: failed to connect to instance
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026