MongoDB incident

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Minor Ongoing View vendor source →

MongoDB is currently experiencing a minor incident affecting MongoDB Cloud, which began 1d ago. The vendor's full update timeline is below.

Started
May 08, 2026, 02:24 AM UTC
Resolved
Ongoing
Duration
● 1d
Detected by Pingoru
May 08, 2026, 02:24 AM UTC

Affected components

MongoDB Cloud

Update timeline

  1. identified May 08, 2026, 02:24 AM UTC

    AWS Availability Zone use1-az4 in US-EAST-1 region is impaired. For some clusters in AWS US-EAST-1 region, cluster nodes in that availability zone may have impaired health. Some Atlas operations, including instance scaling and cluster configuration changes, may also be delayed for clusters in AWS US-EAST-1. Please see https://health.aws.amazon.com/health/status for more information.

  2. monitoring May 08, 2026, 03:12 AM UTC

    AWS Availability Zone use1-az4 in US-EAST-1 region is still impaired and AWS is working to restore the full availability of the availability zone. The Atlas system is taking healing actions on impacted nodes where possible to restore node health. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.

  3. monitoring May 08, 2026, 12:34 PM UTC

    AWS continues to make progress to restore the full availability of the availability zone. The Atlas system is taking healing actions on impacted nodes where possible to restore node health. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.

  4. monitoring May 08, 2026, 08:41 PM UTC

    AWS continues to work towards full recovery. The Atlas system has been successfully taking healing actions on impacted nodes to restore node health and using healthy availability zones for provisioning new nodes. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.