Daily provider-status observations and published incident history for MongoDB Atlas.
Regional incident
MongoDB Atlas has an active regional incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow MongoDB Atlas for future changes.
73.5%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
66.7%
30
10
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Issue impacting Atlas Search availability on certain clusters
The issue has been identified and a fix is being implemented.
investigating
Ongoing Atlas Search incident known to cause mongot crashes, potential search and vector search outage, impacting a subset of search and vector search users in the Atlas fleet.
We have identified the issue and are working on a fix.
MongoDB Charts: Infinite login loop when creating new Charts projects
Since approximately 23:30 UTC on 2026-10-01, users creating new Charts projects by clicking on the "Visualization" tab will repeatedly be prompted to login and will not be able to view the Charts interface. While these Charts projects will be created, we cannot guarantee the timing at this moment.
Existing Charts projects are not affected.
Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.
investigating
Some users may find that their Atlas Triggers are not firing or are not visible in the Atlas UI. We are investigating both symptoms and working to restore trigger processing. We will provide another update as we learn more.
investigating
We are continuing to investigate this issue.
investigating
As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.
MongoDB customers are currently experiencing degraded or limited access to the MongoDB Customer Support Portal (https://support.mongodb.com/).
If you require assistance with a critical MongoDB Technical Support issue and are unable to access the Customer Support Portal, please contact us using one of the numbers listed below:
North America:
New York: +1 646 201 9247
EMEA:
London, UK: +44 808 281 2632
Barcelona, Spain: +(34) 931227636
Milan, Italy: +(39) 0294756824
Frankfurt, Germany: +(49) 6977044487
Paris, France: +(33) 1 77513208
South Africa: +27 87 550 8991
Turkey: +(90) 850 390 7547
Israel: +972 (0)3 376 8802
APAC:
Australia: +61 2 4022 8861
India: 000-800-100-7387 (for calls originating in India only, please include initial '000' when dialing)
Japan: +(81)5031989417
China: +86-400-120-9258
Hong Kong: +852 3008 3632
Taiwan: 0-2-2656 3464 (for calls originating in Taiwan only, please include initial '0' when dialing)
Singapore: +65 8003211470 (for calls originating in Singapore only)
We appreciate your patience.
Atlas is experiencing issues with issuing certificates from Lets Encrypt
Atlas is seeing elevated errors rates of certificate issuance due to a Let's Encrypt outage (https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/6aa35c1d892d7304f2747e01). Free and flex tier cluster provisioning may be delayed.
investigating
We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1
We are continuing to monitor for any further issues.
monitoring
Please follow <a href="https://status.mongodb.com/incidents/7g5qmxgkc2y4">the original status post</a> for updates on AWS me-central-1 and AWS me-south-1 issues.
Legacy Incident Archive
33 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Impaired Cluster Operations due to Lets Encrypt Outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Lets Encrypt is now reporting as healthy. We will continue monitoring as cluster operations return to a healthy state.
monitoring
Cluster operations are currently impaired due to issues with Lets Encrypt. We are actively monitoring the situation as more updates come in.
AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired
minorSource not attested
Last archived state: resolved
View archived record details
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.
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 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.
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.
AWS Cluster DNS Changes Degraded Performance
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We've identified a bad piece of metadata causing DNS issues. We've since patched this metadata and are seeing recovery in ACME updates for cluster topology changes. We will continue to monitor recovery.
investigating
We are still seeing cases where new cluster update requests are failing to go through due to ACME related DNS issues. We are actively investigating this issue.
identified
Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.
identified
DNS changes for AWS clusters are currently degraded. Cluster topology modifications may be delayed or not able to complete successfully. We've identified the issue and are pushing out a patch.
identified
DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.
Atlas Backup Export Jobs Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.
identified
Identified - We have identified an issue causing failures for a subset of Atlas backup export jobs. We are actively working on a fix. Your cluster health and data are unaffected. We will provide another update by May 7 01:30 UTC
Partial outage in Azure West Europe
Source not attested
Last archived state: resolved
View archived record details
monitoring
We're starting to see instances recover. We will continue to monitor the region's status in Azure and ensure Atlas takes any available steps to maintain cluster health.
investigating
We are observing widespread issues in in Azure West Europe. Customers may see nodes reporting as "down" and delayed cluster modifications for Azure clusters in West Europe. There are three total AZs in Azure West Europe, and primary failover will be handled by MongoDB.
April 2026
Increase in Billing for Backup Usage
majorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified a bug affecting some Atlas customers that resulted in higher-than-expected backup charges on invoices for the billing date of April 24, 2026. This is a billing-only issue; your backup configuration, cluster health, and data are unaffected.
We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end.
Please contact MongoDB Support with any questions. We will post another update by April 27 a...
MongoDB Atlas BI Connector: Connections and queries fail
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results. The launch of the fix should be complete by approximately 13:00 UTC 21 April 2026.
identified
We have identified the issue affecting the Business Intelligence (BI) Connector in MongoDB Atlas for Government. We are working on a fix. While no workaround exists, data remains accessible to MongoDB clients. Affected users will not be able to connect to their clusters' BI Connectors.
Cluster health is unaffected.
investigating
We are currently investigating reports in MongoDB Atlas for Government that the Business Intelligence Connector (BI Connector) is failing. Affected users will have issues connecting to and querying their BI Connectors. No workaround has been identified at this time.
Underlying cluster health is not affected.
March 2026
Delays in cluster creation and adding new cluster nodes in Azure East US 2 region
Source not attested
Last archived state: resolved
View archived record details
identified
Identified: Some clusters in the Azure East US 2 region will see delays provisioning new clusters or adding additional nodes to their existing clusters due to Azure capacity constraints.
What you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region.
User action: As a workaround, users can provision clusters in other Azure regions.
Intermittent 503 Errors on Atlas Admin API and Automation Tooling
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We continue to monitor our systems for intermittent spikes in 503 HTTP errors following our deployed fix. We will provide another update tomorrow by 3 PM UTC.
monitoring
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
investigating
We are currently investigating intermittent spikes of HTTP 503 errors affecting Atlas control plane operations performed via the Atlas Admin API and automation tooling such as Terraform. Impacted requests typically fail for a short period and succeed on retry. Atlas database connectivity and data plane operations remain healthy.
Our engineering teams are working to resolve the issue with high urgency and to prevent recurrence. Customers encountering 503 responses are advised to retry failed ...
Issue querying Azure blob storage containers in Atlas Data Federation
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are working on a fix.
investigating
We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.
