MongoDB Atlas Status · History · Incident #2146
RESOLVEDAWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
Minor · Started May 8, 2026 · 2:24 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
MongoDB Atlas Status · History · Incident #2146
RESOLVEDMinor · Started May 8, 2026 · 2:24 AM
Duration
1d 12h
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
May 8, 2026 · 2:24 AM
Resolved
May 9, 2026 · 2:24 PM
Duration
1d 12h
Severity
Minor
Event timeline
Identified
May 8 · 2:24 AM MongoDB AtlasAWS 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
May 8 · 3:12 AM MongoDB AtlasAWS 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
May 8 · 12:34 PM MongoDB AtlasAWS 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
May 8 · 8:41 PM MongoDB AtlasAWS 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
May 9 · 2:24 PM MongoDB AtlasThis incident has been resolved.
Pattern
Increased error rate creating and managing Search and Vector Search indexes
Jun 4, 2026 · 2h 6m
View incident →Investigating connection issues to ADFA in GCP
Jun 2, 2026 · 1h 11m
View incident →Metrics may fail to send to DataDog Gov integrations
May 28, 2026 · 1h 12m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT