Couchbase Capella - Notice history

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.