Capella Operations Impacted by GCP us-central1 region capacity issues
Ongoing · last updateidentifiedOct 15 · 14:27 UTC
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.
Reported by Couchbase Capella on their status page.