Couchbase Capella

Affected: Google Cloud Platform Google Compute Engine

Names an upstream provider: Google Cloud.

1. identified 2026-10-06 20:50 UTC

   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...

2. identified 2026-10-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...

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Google Cloud Platform Google Compute Engine

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-04 23:26 UTC

   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.

2. identified 2026-08-04 23:39 UTC

   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. *...

3. identified 2026-08-05 03:09 UTC

   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...

4. monitoring 2026-08-05 12:20 UTC

   We have seen signs of recovery and failure rates have drastically reduced. We continue to monitor the situation closely.

5. monitoring 2026-08-05 19:13 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-08-05 19:21 UTC

   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...

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Couchbase Capella Operational, Couchbase Capella App Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-29 14:16 UTC

   GCP Global Network Resources issue impacting Operational Cluster and App Services lifecycle operations, including new cluster creation and turn-on operations. Existing clusters are unaffected, and we are actively working with the GCP team on the resolution.

2. monitoring 2026-06-29 17:07 UTC

   GCP reported that mitigation efforts are still underway to restore affected Global Network Resources across dependent services, including Google Compute Engine and Cloud Load Balancing. We are closely monitoring the situation and will provide updates as GCP shares further...

3. resolved 2026-06-29 23:03 UTC

   The issue impacting Google Cloud Platform (GCP) Global Network Resources has been fully resolved. Capella Operational Cluster, App Services lifecycle, and turn-on operations have returned to normal functionality.

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Couchbase Capella Operational, Azure Virtual Machines, Couchbase Capella Analytics, Couchbase Capella App Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Azure OpenAI Service – Latency and intermittent failures in multiple regions.

Started during Azure: Multiple services – Power/cooling issues in West US 2.

1. identified 2026-05-29 09:18 UTC

   Azure West US 2 region is currently experiencing degradation.Some Capella operations for resources within the region have been identified as impacted, we are continuing to monitor the situation. Please refer to https://azurestatusprodaus.azurewebsites.net/en-us/status/ for...

2. monitoring 2026-05-29 11:13 UTC

   Azure has reported that mitigation efforts are underway to restore affected components across dependent services. Customers may begin to see signs of recovery as these actions progress. We are closely monitoring the situation and will provide updates as Azure shares further...

3. monitoring 2026-05-29 14:34 UTC

   Azure reported that mitigation efforts are still underway to restore affected network components across dependent services, including Storage and Compute. We are closely monitoring the situation and will provide updates as Azure shares further progress.

4. monitoring 2026-05-29 14:35 UTC

   Azure reported that mitigation efforts are still underway to restore affected network components across dependent services, including Storage and Compute. We are closely monitoring the situation and will provide updates as Azure shares further progress.

5. monitoring 2026-05-29 15:47 UTC

   Azure teams are actively working to address the issue, with manual intervention and inspections ongoing to stabilize remaining scale units and restore full service. We are closely monitoring and will provide updates as Azure shares further progress.

6. monitoring 2026-05-29 18:32 UTC

   Azure Datacenter power and network infrastructure have been fully restored. The majority of services have recovered, with residual impact limited to storage-dependent workloads on two remaining storage stamps undergoing tail recovery. We are closely monitoring the situation and...

7. resolved 2026-05-29 22:40 UTC

   Azure has marked this incident as resolved, and Capella services are operational.

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Couchbase Capella Operational, Couchbase Capella Analytics, Couchbase Capella App Services

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-08 04:37 UTC

   AWS Availability Zone use1-az4 (Region: US-EAST-1) is currently experiencing degradation. Resulting in node unhealthiness, rebalance operations. Please refer to https://health.aws.amazon.com/health/status for additional details.

2. monitoring 2026-05-08 05:22 UTC

   AWS has observed early signs of recovery. They continue to work towards restoring services in the affected Availability Zone (use1-az4) (Region: US-EAST-1). We are closely monitoring the situation and will provide updates as AWS shares further progress.

3. monitoring 2026-05-08 06:54 UTC

   AWS continues to make progress in resolving the impaired EC2 instances in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, and are working towards full recovery. We are closely monitoring the situation and will provide updates as AWS shares further progress.

4. monitoring 2026-05-08 09:43 UTC

   AWS continues to work on mitigation efforts to resolve the underlying issues in a single Availability Zone (use1-az4) in the US-EAST-1 Region. The EC2 instances and EBS volumes were impacted due to a loss of power during the thermal event. Mitigation efforts are taking longer...

5. monitoring 2026-05-08 11:31 UTC

   AWS continues to make progress towards resolving the issue. Based on their current mitigation efforts, they expect full recovery to take several hours. For more details, please refer to https://health.aws.amazon.com/health/status. We are continuing to monitor for any further...

6. monitoring 2026-05-08 14:11 UTC

   AWS is continuing remediation efforts for impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region caused by a thermal event. Our team is actively monitoring the situation. We will continue to share updates as AWS provides...

7. monitoring 2026-05-08 17:57 UTC

   AWS is continuing its efforts to recover the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. Our team is actively monitoring the situation, and we will continue to share updates as AWS provides additional...

8. monitoring 2026-05-08 20:58 UTC

   AWS continues to work towards the full recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are closely monitoring the situation internally and will provide updates as AWS shares further progress.

9. resolved 2026-05-09 05:17 UTC

   AWS has marked this incident as Resolved. A small number of instances and EBS volumes remain impaired and AWS continue to work to recover all affected remaining resources. The issue was caused by a thermal event resulting in a loss of power. As part of the recovery effort, AWS...

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-26 11:30 UTC

   Between 12:37 PM – 11:15 PM UTC, Couchbase Capella experienced an authentication issue with our third-party email provider, causing a temporary disruption to automated system emails (e.g., registration confirmations and cluster health alerts). The service connection has been...

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Couchbase Capella Operational, Azure Virtual Machines, Couchbase Capella App Services

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Control plane issues in East US.

1. identified 2026-04-24 16:48 UTC

   Azure East US Outage is partially impacting lifecycle operations, including new virtual machine creations, backups, and turn-on operations. Ref: https://azure.status.microsoft/en-us/status.

2. resolved 2026-04-25 03:06 UTC

   This incident has been resolved as updated in Azure status: https://azure.status.microsoft/en-us/status. All the Capella services are operational in the East US.

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Couchbase Capella Operational, Couchbase Capella Analytics, Couchbase Capella App Services, Couchbase Capella UI, Couchbase Capella Management API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 12:02 UTC

   We are aware of an outage that impacted a large number of AWS services in the us-east-1 region, including several for which Couchbase Capella’s management infrastructure had dependencies. This outage primarily impacted between 7 AM and 11 AM UTC on October 20th. More information...

2. monitoring 2025-10-20 14:16 UTC

   AWS is continuing to address remaining issues with EC2 instance launches in the US-EAST-1 region. Due to this, some Capella operations such as Turn On and Backups might still be impacted. We are closely monitoring the situation and will provide updates as soon as more...

3. monitoring 2025-10-20 16:57 UTC

   AWS continues to apply additional mitigations to address throttling of new EC2 instance launches. Some Capella operations may still experience intermittent delays. We are closely monitoring the situation and will provide updates as AWS shares further progress.

4. monitoring 2025-10-20 19:04 UTC

   AWS reports continued progress in resolving EC2 instance launch failures, with increased instance launches and improved network connectivity in the US-EAST-1 region. Capella operations are showing signs of recovery, and we continue to monitor closely.

5. monitoring 2025-10-20 20:12 UTC

   AWS service recovery continues to improve across all services. Throttling for new EC2 instance launches in the US-EAST-1 region is being reduced, and Capella operations are steadily returning to normal.

6. resolved 2025-10-20 21:30 UTC

   All services are operational.

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Couchbase Capella UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-18 04:59 UTC

   We have identified an issue impacting the Capella web console and functionalities including login. No impact to cluster operations has been identified. Further investigation is in progress.

2. identified 2025-10-18 05:22 UTC

   The issue affecting the Capella Web Console has been identified and a fix has been successfully applied. All services are operating normally, and we will continue to monitor the system closely.

3. monitoring 2025-10-18 05:23 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-19 02:16 UTC

   This incident has been resolved and we are adding safeguards to help prevent similar issues in the future.

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-06-19 18:30 UTC

   Between 6:42 PM and 8:02 PM UTC, Capella clusters experienced a temporary interruption in monitoring metrics within the Capella UI. There was no impact on cluster availability, performance, or data during this time. The issue was quickly identified and resolved, and we are...

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Affected: Google Cloud Platform Google Compute Engine, Couchbase Capella Operational, Couchbase Capella Analytics, Couchbase Capella App Services

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-06-12 19:35 UTC

   We’re currently observing an elevated rate of errors originating from GCP. Existing cluster health remains stable and unaffected. However, backups and new cluster deployments on GCP may experience delays or failures.

2. monitoring 2025-06-12 22:34 UTC

   Rate of errors have dropped to normal levels, we are closely monitoring the ongoing Capella operations. For latest updates from GCP: https://status.cloud.google.com/.

3. resolved 2025-06-13 01:45 UTC

   This incident has been resolved as updated in GCP status: https://status.cloud.google.com/.

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-08-30 09:00 UTC

   An issue was identified in Capella Control Plane that was creating a backpressure on one of the internal services and causing delays in processing certain Cluster Operations. Affected users would have observed delays in the Scheduled On/Off operations on the cluster, or delay in...

Excerpts are shortened. Read the full incident on Couchbase Capella's status page.