What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with MongoDB Atlas now? Check the current status

Affected services

MongoDB Cloud

Updates (5)

May 9, 2026, 02:24 PM
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
This incident has been resolved.
MongoDB Atlas ↗
May 8, 2026, 08:41 PM
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
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.
MongoDB Atlas ↗
May 8, 2026, 12:34 PM
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
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.
MongoDB Atlas ↗
May 8, 2026, 03:12 AM
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
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.
MongoDB Atlas ↗
May 8, 2026, 02:24 AM
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
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.
MongoDB Atlas ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow MongoDB Atlas's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.