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.
March 2026
MongoDB Atlas: Clusters page failing to load
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified an issue affecting the Clusters page in MongoDB Atlas. Affected users may see a blank page when trying to view their Clusters page.
Cluster health is unaffected.
MongoDB Atlas for Government: SSO login failures for some users
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results. Users who were previously unable to log in via SSO should now be able to authenticate successfully.
identified
Impact: Some users may be unable to log into the Atlas for Government UI using SSO. Specifically, users accessing Atlas for Government via a saved SSO login URL may receive an error, and users attempting to log in via a federated identity provider link may be unable to complete authentication.
Root cause: We have identified an issue with SSO routing that is preventing some federated login flows from completing successfully. These issues started around 2026-03-18 2:30 UTC.
What you might see...
Cluster Provisioning Impaired in Azure Virginia-East2 (eastus2)
majorSource not attested
Last archived state: resolved
View archived record details
identified
Azure has an active service issue for virtual machines in East US 2. According to their service health page, "customers using Virtual Machines in East US 2 may have encountered errors when performing service management operations - such as create, update, scale, or start - for resources in this region. [...] During peak impact, an unexpected surge in usage caused backend Virtual Machine components to reach operational limits, resulting in deployment failures for some VMs. We are actively miti...
investigating
We are experiencing high failure rates when provisioning clusters in Azure Virginia-East2 (eastus2). Please note that cluster creation in this region will likely experience delays until the issue is resolved.
