Snapshot 237768
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/"> <channel> <title>Couchbase Capella Status - Incident history</title> <link>https://status.couchbase.com</link> <description>Couchbase Capella</description> <pubDate>Sat, 7 Nov 2026 00:43:08 +0000</pubDate> <item> <title>Capella Operations Impacted by AWS us-west-2 instance launch failures</title> <description> Type: Incident Duration: 1 hour Affected Components: Couchbase Capella Operational Nov 7, 01:43:26 GMT+0 - Resolved - This incident has been resolved. Capella Operational Cluster lifecycle operations in AWS us-west-2, including new cluster creation, turn-on, and backup, are operating normally. The issue was caused by elevated EC2 instance launch failures in the AWS us-west-2 region, which AWS attributed to an issue with its EBS service. For additional incident details, please refer to <https://health.aws.amazon.com/health/status>. Nov 7, 00:43:08 GMT+0 - Investigating - AWS us-west-2 instance launch failures are intermittently impacting Operational Cluster lifecycle operations, including new cluster creation, turn-on, and backups. Existing clusters are unaffected. Please refer to the AWS incident for the latest status: <https://health.aws.amazon.com/health/status>. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour</p> <p><strong>Affected Components:</strong> </p> <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>01:43:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Capella Operational Cluster lifecycle operations in AWS us-west-2, including new cluster creation, turn-on, and backup, are operating normally. The issue was caused by elevated EC2 instance launch failures in the AWS us-west-2 region, which AWS attributed to an issue with its EBS service. For additional incident details, please refer to <https://health.aws.amazon.com/health/status>..</p> <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>00:43:08</var> GMT+0</small><br><strong>Investigating</strong> - AWS us-west-2 instance launch failures are intermittently impacting Operational Cluster lifecycle operations, including new cluster creation, turn-on, and backups. Existing clusters are unaffected. Please refer to the AWS incident for the latest status: <https://health.aws.amazon.com/health/status>..</p> ]]> </content:encoded> <pubDate>Sat, 7 Nov 2026 00:43:08 +0000</pubDate> <link>https://status.couchbase.com/incident/cmw5ojcon0lx21bs00r8oxclh</link> <guid>https://status.couchbase.com/incident/cmw5ojcon0lx21bs00r8oxclh</guid> </item> <item> <title>Capella Operations Impacted by GCP us-central1 region capacity issues</title> <description> Type: Incident Affected Components: Google Cloud Platform Google Compute Engine Nov 5, 18:47:24 GMT+0 - Monitoring - **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. Oct 26, 13:17:01 GMT+0 - Identified - **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. Oct 15, 14:27:12 GMT+0 - Identified - **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. Oct 6, 20:50:14 GMT+0 - Identified - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>18:47:24</var> GMT+0</small><br><strong>Monitoring</strong> - **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..</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>13:17:01</var> GMT+0</small><br><strong>Identified</strong> - **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..</p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>14:27:12</var> GMT+0</small><br><strong>Identified</strong> - **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..</p> <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>20:50:14</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> </content:encoded> <pubDate>Tue, 6 Oct 2026 20:50:14 +0000</pubDate> <link>https://status.couchbase.com/incident/cmvivwv6a08vo1fnzk6eaqqp9</link> <guid>https://status.couchbase.com/incident/cmvivwv6a08vo1fnzk6eaqqp9</guid> </item> <item> <title>Capella Operations Impacted by GCP capacity issues</title> <description> 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>19:21:39</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>19:13:57</var> GMT+0</small><br><strong>Monitoring</strong> - We are continuing to monitor for any further issues..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>12:20:43</var> GMT+0</small><br><strong>Monitoring</strong> - We have seen signs of recovery and failure rates have drastically reduced. We continue to monitor the situation closely..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>03:09:42</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>23:39:57</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>23:26:34</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> ]]> </content:encoded> <pubDate>Tue, 4 Aug 2026 23:26:34 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019ef0wpqenee3nne-mz5445ylrwkx</link> <guid>https://status.couchbase.com/incident/cmtun7yf019ef0wpqenee3nne-mz5445ylrwkx</guid> </item> <item> <title>Capella Operations Impacted by GCP Global Network Resources issue</title> <description> Type: Incident Affected Components: Couchbase Capella Operational, Couchbase Capella App Services Jun 29, 23:03:15 GMT+0 - Resolved - 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. Jun 29, 17:07:29 GMT+0 - Monitoring - 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 progress. Jun 29, 14:16:02 GMT+0 - Investigating - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>23:03:15</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>17:07:29</var> GMT+0</small><br><strong>Monitoring</strong> - 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 progress..</p> <p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>14:16:02</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> ]]> </content:encoded> <pubDate>Mon, 29 Jun 2026 14:16:02 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019en0wpq5ywd5n9r-262s74tv3808</link> <guid>https://status.couchbase.com/incident/cmtun7yf019en0wpq5ywd5n9r-262s74tv3808</guid> </item> <item> <title>Performance Degradation in Azure West US 2 region.</title> <description> Type: Incident Affected Components: Couchbase Capella Operational, Couchbase Capella App Services, Azure Virtual Machines, Couchbase Capella Analytics May 29, 22:40:44 GMT+0 - Resolved - Azure has marked this incident as resolved, and Capella services are operational. May 29, 18:32:24 GMT+0 - Monitoring - 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 will provide updates as Azure shares further progress. May 29, 15:47:15 GMT+0 - Monitoring - 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. May 29, 14:35:05 GMT+0 - Monitoring - 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. May 29, 14:34:50 GMT+0 - Monitoring - 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. May 29, 11:13:07 GMT+0 - Monitoring - 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 progress. May 29, 09:18:25 GMT+0 - Identified - 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 additional details. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>22:40:44</var> GMT+0</small><br><strong>Resolved</strong> - Azure has marked this incident as resolved, and Capella services are operational..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>18:32:24</var> GMT+0</small><br><strong>Monitoring</strong> - 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 will provide updates as Azure shares further progress..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>15:47:15</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>14:35:05</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>14:34:50</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>11:13:07</var> GMT+0</small><br><strong>Monitoring</strong> - 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 progress..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>09:18:25</var> GMT+0</small><br><strong>Identified</strong> - 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 additional details..</p> ]]> </content:encoded> <pubDate>Fri, 29 May 2026 11:13:07 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019et0wpq3ukl7ory-y0fxjp877lsh</link> <guid>https://status.couchbase.com/incident/cmtun7yf019et0wpq3ukl7ory-y0fxjp877lsh</guid> </item> <item> <title>Performance Degradation in AWS US-EAST-1 (AZ use1-az4)</title> <description> Type: Incident Affected Components: Couchbase Capella Operational, Couchbase Capella App Services, Couchbase Capella Analytics May 9, 05:17:37 GMT+0 - Resolved - 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 shifted traffic away from the impacted Availability Zone use1-az4 (Region: US-EAST-1). Please refer to https://health.aws.amazon.com/health/status for additional details. May 8, 20:58:09 GMT+0 - Monitoring - 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. May 8, 17:57:50 GMT+0 - Monitoring - 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 information and recovery progress. May 8, 14:11:24 GMT+0 - Monitoring - 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 additional information and recovery progress. May 8, 11:31:01 GMT+0 - Monitoring - 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 issues or updates. May 8, 09:43:21 GMT+0 - Monitoring - 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 than AWS originally anticipated. We are closely monitoring the situation internally and will provide updates as AWS shares further progress. May 8, 06:54:37 GMT+0 - Monitoring - 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. May 8, 05:22:34 GMT+0 - Monitoring - 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. May 8, 04:37:21 GMT+0 - Identified - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>May <var data-var='date'> 9</var>, <var data-var='time'>05:17:37</var> GMT+0</small><br><strong>Resolved</strong> - 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 shifted traffic away from the impacted Availability Zone use1-az4 (Region: US-EAST-1). Please refer to https://health.aws.amazon.com/health/status for additional details..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>20:58:09</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>17:57:50</var> GMT+0</small><br><strong>Monitoring</strong> - 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 information and recovery progress..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>14:11:24</var> GMT+0</small><br><strong>Monitoring</strong> - 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 additional information and recovery progress..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>11:31:01</var> GMT+0</small><br><strong>Monitoring</strong> - 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 issues or updates..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>09:43:21</var> GMT+0</small><br><strong>Monitoring</strong> - 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 than AWS originally anticipated. We are closely monitoring the situation internally and will provide updates as AWS shares further progress..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>06:54:37</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:22:34</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>04:37:21</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> </content:encoded> <pubDate>Fri, 8 May 2026 04:37:21 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019f30wpq42et7eoo-v7cwj18mj21r</link> <guid>https://status.couchbase.com/incident/cmtun7yf019f30wpq42et7eoo-v7cwj18mj21r</guid> </item> <item> <title>Notifications Delivery Interruption</title> <description> Type: Incident Apr 26, 11:30:00 GMT+0 - Resolved - 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 restored, and all email delivery is operating normally. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Resolved</strong> - 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 restored, and all email delivery is operating normally..</p> ]]> </content:encoded> <pubDate>Mon, 27 Apr 2026 04:03:49 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019fd0wpq9pazg9aa-zhqygfjpch5q</link> <guid>https://status.couchbase.com/incident/cmtun7yf019fd0wpq9pazg9aa-zhqygfjpch5q</guid> </item> <item> <title>Capella Operations Impacted by Azure East US Outage</title> <description> Type: Incident Affected Components: Couchbase Capella Operational, Couchbase Capella App Services, Azure Virtual Machines Apr 25, 03:06:54 GMT+0 - Resolved - 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. Apr 24, 16:48:03 GMT+0 - Identified - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>03:06:54</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>16:48:03</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> </content:encoded> <pubDate>Fri, 24 Apr 2026 16:48:03 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019ff0wpqgg091mcj-32y8sy9z0yz2</link> <guid>https://status.couchbase.com/incident/cmtun7yf019ff0wpqgg091mcj-32y8sy9z0yz2</guid> </item> <item> <title>Capella Operations Impacted by AWS Outage</title> <description> Type: Incident Affected Components: Couchbase Capella Operational, Couchbase Capella App Services, Couchbase Capella Analytics, Couchbase Capella UI, Couchbase Capella Management API Oct 20, 21:30:44 GMT+0 - Resolved - All services are operational. Oct 20, 20:12:05 GMT+0 - Monitoring - 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. Oct 20, 19:04:35 GMT+0 - Monitoring - 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. Oct 20, 16:57:57 GMT+0 - Monitoring - 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. Oct 20, 14:16:42 GMT+0 - Monitoring - 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 information is available. Oct 20, 12:02:57 GMT+0 - Monitoring - 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 on the scope of this outage can be seen on the relevant AWS status page (https://health.aws.amazon.com/health/status). No direct impact to Capella Operational clusters, App Services, or other Couchbase Capella resources that were in a healthy state prior to the outage has been identified. Scheduled activity, primarily backups and cluster hibernation, as well as Capella UI and Management API functionality, during the outage period were seen to be impacted. We are actively reviewing and working on mitigating any remaining impact and will notify affected users accordingly. It is recommended to open a support ticket for any specific questions or to highlight any unexpected behavior observed. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>21:30:44</var> GMT+0</small><br><strong>Resolved</strong> - All services are operational..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>20:12:05</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>19:04:35</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:57:57</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>14:16:42</var> GMT+0</small><br><strong>Monitoring</strong> - 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 information is available..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>12:02:57</var> GMT+0</small><br><strong>Monitoring</strong> - 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 on the scope of this outage can be seen on the relevant AWS status page (https://health.aws.amazon.com/health/status). No direct impact to Capella Operational clusters, App Services, or other Couchbase Capella resources that were in a healthy state prior to the outage has been identified. Scheduled activity, primarily backups and cluster hibernation, as well as Capella UI and Management API functionality, during the outage period were seen to be impacted. We are actively reviewing and working on mitigating any remaining impact and will notify affected users accordingly. It is recommended to open a support ticket for any specific questions or to highlight any unexpected behavior observed..</p> ]]> </content:encoded> <pubDate>Mon, 20 Oct 2025 12:02:57 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019fi0wpq6yl0dqdm-21wj2d5b545h</link> <guid>https://status.couchbase.com/incident/cmtun7yf019fi0wpq6yl0dqdm-21wj2d5b545h</guid> </item> <item> <title>Capella Web Console issues</title> <description> Type: Incident Affected Components: Couchbase Capella UI Oct 19, 02:16:06 GMT+0 - Resolved - This incident has been resolved and we are adding safeguards to help prevent similar issues in the future. Oct 18, 05:23:02 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Oct 18, 05:22:53 GMT+0 - Identified - 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. Oct 18, 04:59:37 GMT+0 - Investigating - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>02:16:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and we are adding safeguards to help prevent similar issues in the future..</p> <p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>05:23:02</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>05:22:53</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>04:59:37</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> ]]> </content:encoded> <pubDate>Sat, 18 Oct 2025 04:59:36 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019fr0wpq5t3o9srx-cf8prp5mzb50</link> <guid>https://status.couchbase.com/incident/cmtun7yf019fr0wpq5t3o9srx-cf8prp5mzb50</guid> </item> <item> <title>Brief Interruption In Monitoring Metrics</title> <description> Type: Incident Jun 19, 18:30:00 GMT+0 - Resolved - 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 adding safeguards to help prevent similar issues in the future. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Resolved</strong> - 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 adding safeguards to help prevent similar issues in the future..</p> ]]> </content:encoded> <pubDate>Wed, 25 Jun 2025 06:03:10 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019fw0wpqds9e5ihl-khq1qchw4gtl</link> <guid>https://status.couchbase.com/incident/cmtun7yf019fw0wpqds9e5ihl-khq1qchw4gtl</guid> </item> <item> <title>Ongoing issues with GCP may impact functionality</title> <description> Type: Incident Affected Components: Couchbase Capella Operational, Couchbase Capella App Services, Couchbase Capella Analytics, Google Cloud Platform Google Compute Engine Jun 13, 01:45:28 GMT+0 - Resolved - This incident has been resolved as updated in GCP status: https://status.cloud.google.com/. Jun 12, 22:34:46 GMT+0 - Monitoring - 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/. Jun 12, 19:35:02 GMT+0 - Investigating - 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. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>01:45:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved as updated in GCP status: https://status.cloud.google.com/..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>22:34:46</var> GMT+0</small><br><strong>Monitoring</strong> - 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/..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:35:02</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> ]]> </content:encoded> <pubDate>Thu, 12 Jun 2025 19:35:01 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019fy0wpq7reh1wkf-q98jkf6f2tfn</link> <guid>https://status.couchbase.com/incident/cmtun7yf019fy0wpq7reh1wkf-q98jkf6f2tfn</guid> </item> <item> <title>Capella Cluster Operations Experiencing Delays</title> <description> Type: Incident Aug 30, 09:00:00 GMT+0 - Resolved - 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 backups. The issue has been mitigated now and all services are operational now. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Resolved</strong> - 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 backups. The issue has been mitigated now and all services are operational now..</p> ]]> </content:encoded> <pubDate>Fri, 30 Aug 2024 09:00:00 +0000</pubDate> <link>https://status.couchbase.com/incident/cmtun7yf019g20wpqdvmfbzjc-f5t13kc0fzt4</link> <guid>https://status.couchbase.com/incident/cmtun7yf019g20wpqdvmfbzjc-f5t13kc0fzt4</guid> </item> </channel> </rss>