Performance Degradation in AWS US-EAST-1 (AZ use1-az4)

What to do

• Check whether you use Couchbase Capella Couchbase Capella Operational, Couchbase Capella App Services, Couchbase Capella Analytics in us, us-east-1. 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-05-08 04:37 UTC and 2026-05-08 04:37 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. resolvedMay 8, 2026, 4:37 AM UTC

   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.

   provider

Corrections

None so far.

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