Snapshot 258395
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Couchbase Capella - Status Page Experiencing partially degraded performance Capella Operations Impacted by GCP us-central1 region capacity issues Monitoring MonitoringNovember 05, 2026 at 6:47 PMUTC Update: Compute Fallback Now Available for GCP us-central1 Couchbase has rolled out automated compute fallback for Capella clusters on GCP. When the requested machine type isn't available in us-central1, Capella now automatically provisions the node using a compatible machine type instead. This significantly increases the capacity Capella can draw on in the region. What this means for customers: Improved reliability: Cluster creation, turn-on, scaling, and upgrades in us-central1 are now much less likely to fail because of instance capacity constraints. No action required: Fallback happens automatically. Recommended Customer Guidance: Existing Clusters: Lifecycle operations, including scaling and upgrades, can resume. New Deployments: While we monitor the situation, us-central1 remains flagged as capacity-constrained for new cluster creation. Backups: Continue taking regular cluster snapshot backups as a standard best practice. Couchbase Support will continue to perform cluster backups where bucket backups continue to experience failures. We are monitoring operations in us-central1 and remain in close coordination with the GCP team. UpdateOctober 26, 2026 at 1:17 PMUTC Update: GCP us-central1 Compute Engine capacity constraints continue. Live provider status is reflected on the GCP components on this page. Customer Impact: Affected Operations: Cluster creation, turn-on, upgrades, scaling, and bucket backups in us-central1 may fail while constraints last. Backups: Couchbase Support will perform cluster backups where customer backups fail. Guidance: Standing recommendations and the actions taken by Couchbase are published in the general notice "GCP us-central1 Capacity Constraints: Guidance for Capella Customers" on this page, directly below this incident, and will be kept current there. We will post here when GCP restores capacity in the region. UpdateOctober 15, 2026 at 2:27 PMUTC 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. IdentifiedOctober 06, 2026 at 8:50 PMUTC 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. EmailWebhook GCP us-central1 Capacity Constraints: Guidance for Capella Customers Posted 16 days agoOctober 26, 20261:13 PMUTC Update (5 Nov 2026): Automated compute fallback is now available for Capella clusters in GCP us-central1. When the requested machine type isn't available, Capella automatically provisions the node using a compatible machine type instead. Live provider status is shown on the GCP components below. Actions Taken by Couchbase: Compute Fallback: Rolled out automated compute fallback so cluster creation, turn-on, scaling, and upgrades in us-central1 are much less likely to fail because of instance capacity constraints. No customer action is required. Instance Capacity Management: We executed capacity reservations where available to help retain and protect resources allocated to active Capella clusters. Region Tagging: us-central1 remains flagged as capacity-constrained in our control plane for new cluster creation while we monitor the situation. Recommended Customer Guidance: Existing Clusters: Lifecycle operations, including scaling and upgrades, can resume. New Deployments: While we monitor the situation, us-central1 remains flagged as capacity-constrained for new cluster creation. Backups: Continue taking regular cluster snapshot backups as a standard best practice. Couchbase Support will continue to perform cluster backups where bucket backups continue to experience failures. We are monitoring operations in us-central1, remain in close coordination with the GCP team, and will update this notice as regional capacity conditions evolve. Couchbase Capella - Operational 100.0% uptime 95.50% uptime Azure - Operational 100.0% uptime 100.0% uptime AWS ec2-ap-south-2 - Operational AWS ec2-us-east-1 - Operational AWS ec2-us-east-2 - Operational AWS ec2-eu-central-1 - Operational AWS ec2-eu-west-1 - Operational AWS ec2-eu-west-2 - Operational AWS ec2-eu-west-3 - Operational AWS ec2-ap-south-1 - Operational AWS ec2-ap-east-1 - Operational AWS ec2-ap-southeast-7 - Operational AWS ec2-me-central-1 - Degraded performance AWS ec2-ca-central-1 - Operational AWS ec2-sa-east-1 - Operational AWS ec2-eu-central-2 - Operational AWS ec2-eu-north-1 - Operational AWS ec2-eu-south-1 - Operational AWS ec2-ap-northeast-1 - Operational AWS ec2-ap-northeast-2 - Operational AWS ec2-ap-northeast-3 - Operational AWS ec2-ap-southeast-1 - Operational AWS ec2-ap-southeast-2 - Operational AWS ec2-ap-southeast-3 - Operational AWS ec2-ap-southeast-4 - Operational AWS ec2-me-south-1 - Degraded performance AWS ec2-af-south-1 - Operational AWS ec2-us-west-2 - Operational AWS ec2-mx-central-1 - Operational AWS ec2-il-central-1 - Operational Capella Control Plane - Operational ~0.0 ms 100.0% uptime Recent notices Show history Show history Show notice history