Capella Operations Impacted by GCP capacity issues

What to do

• Check whether you use Couchbase Capella Google Cloud Platform Google Compute Engine in apac, asia-southeast1, us, us-central1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-08-04 23:26 UTC and 2026-08-04 23:26 UTC may need a replay.

• Subscribe to Couchbase Capella's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=couchbase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Couchbase Capella 1

1. resolvedAug 4, 2026, 11:26 PM UTC

   Type: Incident Affected Components: Google Cloud Platform Google Compute Engine Aug 5, 19:21:39 GMT+0 - Resolved - 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. Aug 5, 19:13:57 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Aug 5, 12:20:43 GMT+0 - Monitoring - We have seen signs of recovery and failure rates have drastically reduced. We continue to monitor the situation closely. Aug 5, 03:09:42 GMT+0 - Identified - 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. Aug 4, 23:39:57 GMT+0 - Identified - 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. Aug 4, 23:26:34 GMT+0 - Investigating - 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.