MongoDB Atlas incident: AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Affected components

• MongoDB Cloud

1. resolvedMay 9, 2026, 14:24 UTC

   This incident has been resolved.

2. monitoringMay 8, 2026, 20:41 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.

3. monitoringMay 8, 2026, 12:34 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. monitoringMay 8, 2026, 03:12 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.

5. identifiedMay 8, 2026, 02:24 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in MongoDB Atlas's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Upstash: QStash US Region Service DisruptionCritical · May 8, 2026, 09:46 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• GitBook: Degraded database performanceMajor · May 8, 2026, 15:52 UTC
• Elasticsearch: Issues with Email AlertsMajor · May 8, 2026, 18:10 UTC
• Discord: Increased API ErrorsMajor · May 8, 2026, 19:08 UTC
• Render: Certificate issuance paused for Let's EncryptMajor · May 8, 2026, 20:22 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history