ChangesCouchbaseCapella Operations Impacted by GCP us-central1 region capacity issues
Couchbase: Major incident: Capella Operations Impacted by GCP us-central1 region capacity issues
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Couchbase removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: Capella Operations Impacted by GCP us-central1 region capacity issues
Before: not present
After: major
Before: not present
After: identified
Before: not present
After: 2026-10-06 20:50 UTC
Before: not present
After: GCP - Google Cloud Platform Google Compute Engine, Google Cloud Platform Google Compute Engine
Before: not present
After: GCP us-central1 capacity constraints are impacting cluster creation, turn-on, upgrades, scaling, and bucket backups.
Recommended Actions:
New Deployments: Select an alternate GCP region.
Existing Clusters: Avoid pausing, stopping, scaling, or upgrading clusters in us-central1 to prevent operation failures.
Backups: Perform cluster snapshot backups where possible. Couchbase Support will perform cluster backups to continue to maintain backups for any failures.
We are working closely with the GCP team on mitigation and will share updates as soon as they become available.
Before: not present
After: Update: Ongoing Mitigation for GCP us-central1 Capacity Constraints
Actions Taken by Couchbase:
Instance Capacity Management: We executed capacity reservations where available to help retain and protect resources allocated to active Capella clusters.
Region Tagging: We have flagged us-central1 as capacity-constrained in our control plane to proactively manage deployment guidance and reduce operational friction.
Platform Enhancements: We are accelerating technical updates, including automated multi-instance fallback capabilities and support for GCP’s newer generation machine families, to unlock broader capacity options and enhance platform resilience.
Recommended Customer Guidance:
Existing Clusters: We recommend minimizing non-essential cluster modifications—such as scaling, node changes, or pausing/resuming—where possible, as these lifecycle operations may experience failures due to underlying GCP instance capacity constraints.
New Deployments: Consider selecting alternate GCP regions for new cluster creation where feasible.
Backups: Continue maintaining regular cluster snapshot backups as a standard high-availability best practice.
We remain in close coordination with the GCP team and will share further updates as additional mitigations are released or regional capacity conditions evolve.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
Tuesday, October 6
1 incident change
- MajorMajor incident
Capella Operations Impacted by GCP us-central1 region capacity issuesthis change