Rewindex

ChangesCouchbaseCapella Operations Impacted by GCP capacity issues

Couchbase: Major incident: Capella Operations Impacted by GCP capacity issues

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
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.

AddedTitle#1
Before: not present
After: Capella Operations Impacted by GCP capacity issues
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-04 23:26 UTC
AddedResolved time#5
Before: not present
After: 2026-08-05 19:21 UTC
AddedAffected components#6
Before: not present
After: GCP - Google Cloud Platform Google Compute Engine, Google Cloud Platform Google Compute Engine
AddedUpdateinvestigating#7
Before: not present
After: GCP us-central1 capacity issue impacting Operational Cluster lifecycle operations, including new cluster creation, turn-on, and backup. Existing clusters are unaffected, and we are actively working with the GCP team on the next steps.
AddedUpdateidentified#8
Before: not present
After: We are in direct contact with GCP support to monitor us-central1 and will provide another update as soon as capacity stabilizes. Recommended Workarounds: * New Deployments: Select an alternate GCP region (such as us-east1, us-east4, or us-west1) for new cluster creation. * Existing Clusters: Avoid pausing, stopping, or modifying existing us-central1 clusters until GCP resolves the capacity constraint, as turning them back on or adding nodes may temporarily fail.
AddedUpdateidentified#9
Before: not present
After: The capacity issues impacting the GCP regions and resulting operational Cluster lifecycle operations, including new cluster creation, turn-on, and backup failures: us-central1 asia-southeast1 us-east1 Recommended Workarounds: * New Deployments: Select an alternate GCP region for new cluster creation. * Existing Clusters: Avoid pausing, stopping, or modifying existing us-central1 clusters until GCP resolves the capacity constraint, as turning them back on or adding nodes may temporarily fail. * Backups: Support Team will perform cluster backups to continue to maintain backups. We continue to work closely with the GCP team on mitigation.
AddedUpdatemonitoring#10
Before: not present
After: We have seen signs of recovery and failure rates have drastically reduced. We continue to monitor the situation closely.
AddedUpdatemonitoring#11
Before: not present
After: We are continuing to monitor for any further issues.
AddedUpdateresolved#12
Before: not present
After: Across us-central1, asia-southeast1, and us-east1 regions, we have verified that all Cluster lifecycle operations—including new cluster creations, turn-ons, and backups—are now functioning normally and completing successfully. Failure rates have returned to the standard baseline level.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

Tuesday, August 4

1 incident change

All Couchbase changesCouchbase profileMarkdownJSON