Provider
MongoDB AtlasIncident detail
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
Resolved incidentMinor1 affected service
Timeline window
to
Outage alerts
Get alerted the next time MongoDB Atlas breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update MongoDB Atlas posted, oldest to newest, exactly as it appeared on their official status page.
Identified
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.
Monitoring
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.
Monitoring
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.
Monitoring
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.
Resolved
This incident has been resolved.
Keep exploring
More from MongoDB Atlas
Neighboring incidents on MongoDB Atlas's timeline and the rest of their record on OutageDeck.