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.
August 2026
Issues rotating certificates for projects containing only Atlas Free and Flex clusters
Source not attested
Last archived state: resolved
View archived record details
MongoDB Cloud
monitoring
We have deployed fix, continuing the monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue.
identified
We have identified an issue impacting certain projects containing only Free or Flex clusters. For those clusters, TLS certificates are not being rotated correctly. This could lead to an inability to connect to your Free or Flex cluster. We are working on remediation steps.
Atlas UI and API Periodic Unavailability
minorSource not attested
Last archived state: resolved
View archived record details
MongoDB Cloud
monitoring
We have disabled the workload and are monitoring the situation
identified
We have identified a new workload that was putting more load than expected on the backing system. We are working on disabling it. Customer clusters remain unaffected.
investigating
We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.
We are investigating an issue with Google Cloud Platform (GCP) capacity that is affecting some MongoDB Atlas customers across multiple GCP regions and geographies. We expect the scope of this issue to continue to expand as our investigation progresses. It currently includes, but is not limited to, multiple GCP regions across North America, Europe, and Asia Pacific/Australia, as well as M50 and S70L instance types.
Customers may experience errors or delays when creating or modifying Atlas clu...
Elevated errors on VoyageAI APIs
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been applied and we are monitoring the system.
investigating
VoyageAI APIs are experiencing elevated 5xx errors. We are investigating the issue.
July 2026
Delayed cluster configuration affecting free and flex users
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.
identified
We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.
investigating
We are investigating an issue with cluster configuration updates getting delayed for a subset of users on free and flex tiers. Cluster access is unaffected.
Atlas Stream Processing errors in Azure West Europe
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue affecting Atlas Stream Processing in Azure West Europe. Some users may see processors in this region encounter internal errors. We are actively investigating and will share another update as soon as we have more information.
VoyageAI elevated errors
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We have fully recovered as of 16:41 PST.
investigating
All VoyageAI models are experiencing elevated errors. We are investigating the issue.
Cluster connectivity issues in Azure westus
majorSource not attested
Last archived state: resolved
View archived record details
identified
Azure is rolling out a mitigation for the ongoing networking incident affecting the West US region, and we are seeing signs of recovery. Some Atlas clusters hosted in Azure West US may continue to experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. We are monitoring recovery closely and will provide additional updates as more information becomes avail...
identified
We are aware of an ongoing Azure networking incident affecting the West US region. Some Atlas clusters hosted in Azure West US may experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. Azure is investigating the issue and evaluating mitigation options. We will provide additional updates as more information becomes available.
identified
Azure has confirmed that there are networking issues in the westus region. Please follow the official azure status post for more detailed updates https://azure.status.microsoft/en-us/status
investigating
We are currently investigating an issue with Azure clusters in westus region. Please refer to the azure status post here for more information https://azure.status.microsoft/en-us/status.
MongoDB Atlas and Atlas for Government: New AWS Backup and AWS Data Transfer costs will be unavailable between July 17 and 20
Source not attested
Last archived state: resolved
View archived record details
monitoring
The upstream issue has been corrected. After approximately 0400 UTC on 2026-07-21, most, if not all, of the updated backup and network consumption on AWS will be reflected in MongoDB Atlas and Atlas for Government. Thank you for your patience during this incident.
identified
Due to an ongoing incident with AWS's billing data, MongoDB Atlas and Atlas for Government will not be updating AWS network or backup consumption data over this weekend, 2026-07-17 through 2026-07-20. The products themselves will remain fully available. When the upstream issue has been resolved, we intend to display and bill for the correct amounts. Charges will have usage dates that correctly express the usage, but will have the billed date of when this is corrected.
Cluster and backup heal...
Atlas Stream Processing is experiencing issues in Azure - West Europe
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the region.
investigating
We are currently investigating an issue affecting Stream Processing Azure West Europe. User initiated commands & workloads may see intermittent failures.
