Apr <var data-var='date'> 1</var>, <var data-var='time'>22:46</var> UTC Completed - The scheduled maintenance has been completed.Apr <var data-var='date'> 1</var>, <var data-var='time'>21:47</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'> 1</var>, <var data-var='time'>21:46</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time.Apr <var data-var='date'> 1</var>, <var data-var='time'>21:46</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'> 1</var>, <var data-var='time'>21:45</var> UTC Scheduled - Cluster operations will be delayed due to DNS maintenance activities in MongoDB Atlas for Government

Cluster operations will be delayed due to DNS maintenance activities in MongoDB Atlas for Government

Apr <var data-var='date'> 1</var>, <var data-var='time'>12:55</var> UTC Resolved - Some Atlas users may be unable to access Charts and the Visualization page due to repeated login prompts or unauthorized errors when attempting to sign in. Our engineers have identified a recent change as the likely cause, have rolled it back, and are monitoring the service to confirm that normal access has been restored.

Atlas Charts users unable to login

Mar <var data-var='date'>31</var>, <var data-var='time'>21:19</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'>19</var>, <var data-var='time'>22:15</var> UTC 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.Mar <var data-var='date'>19</var>, <var data-var='time'>00:24</var> UTC 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: - A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL. - An inability to complete login when using a federated identity provider link. Our actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users. User action: As a workaround, users can log in by entering their email address directly at https://account.mongodbgov.com and following the standard prompts. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as we progress toward resolution, or if we observe any change in impact to Atlas for Government.

MongoDB Atlas for Government: SSO login failures for some users

Mar <var data-var='date'>30</var>, <var data-var='time'>23:10</var> UTC Resolved - We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.Mar <var data-var='date'>30</var>, <var data-var='time'>21:47</var> UTC 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.

Delays in cluster creation and adding new cluster nodes in Azure East US 2 region

Mar <var data-var='date'>27</var>, <var data-var='time'>13:21</var> UTC Resolved - We are no longer seeing intermittent spikes in HTTP 503 errors.Mar <var data-var='date'>26</var>, <var data-var='time'>19:12</var> UTC Update - 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.Mar <var data-var='date'>25</var>, <var data-var='time'>23:39</var> UTC Monitoring - The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.Mar <var data-var='date'>25</var>, <var data-var='time'>21:31</var> UTC 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 Admin API and Terraform operations with appropriate retry logic and backoff while we continue our investigation.

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

Mar <var data-var='date'>19</var>, <var data-var='time'>19:19</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'>19</var>, <var data-var='time'>19:14</var> UTC Update - We are continuing to monitor for any further issues.Mar <var data-var='date'>19</var>, <var data-var='time'>19:01</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Mar <var data-var='date'>19</var>, <var data-var='time'>18:25</var> UTC Identified - The issue has been identified and we are working on a fix.Mar <var data-var='date'>19</var>, <var data-var='time'>18:11</var> UTC Investigating - We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.

Issue querying Azure blob storage containers in Atlas Data Federation

Mar <var data-var='date'>19</var>, <var data-var='time'>15:28</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'>19</var>, <var data-var='time'>15:17</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Mar <var data-var='date'>19</var>, <var data-var='time'>14:42</var> UTC 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: Clusters page failing to load

Mar <var data-var='date'>11</var>, <var data-var='time'>20:10</var> UTC Resolved - At approximately 10:30 AM CT, we identified an issue affecting stream processing within the AWS US-EAST-1 region. As of now, normal operations have resumed. We have initiated a full investigation to determine the root cause and prevent future recurrence.

Issue affecting stream processing within the AWS US-EAST-1 region

Mar <var data-var='date'>11</var>, <var data-var='time'>02:30</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'>11</var>, <var data-var='time'>02:21</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Mar <var data-var='date'>11</var>, <var data-var='time'>00:45</var> UTC Identified - The issue has been identified and a fix is being implemented.Mar <var data-var='date'>10</var>, <var data-var='time'>23:18</var> UTC Investigating - Atlas cluster snapshots are failing. We are actively investigating.

Atlas Clusters Snapshot Failures

Mar <var data-var='date'> 2</var>, <var data-var='time'>16:28</var> UTC Resolved - This incident has been resolved. Email notifications are being sent successfully.Mar <var data-var='date'> 2</var>, <var data-var='time'>15:50</var> UTC Investigating - We are currently investigating this issue. Some users may not be receiving emails from MongoDB. We are looking into the cause and will provide an update as soon as we know more.

MongoDB Atlas: Email notifications may be failing

Mar <var data-var='date'> 2</var>, <var data-var='time'>12:00</var> UTC Resolved - Users may have seen tools and integrations that rely on older MongoDB Atlas Admin API versions (for example, 2023-01-01 and 2023-02-01) start failing with HTTP 410 responses indicating that the requested version was no longer available. This affected workflows using the MongoDB Atlas Admin API through the Terraform provider, the Atlas CLI, and custom automation. This behavior was triggered by our planned retirement process for older API versions, but the resulting user impact was unintended because these versions were still in active use. We have extended the end-of-life date for the affected API versions to mid-2027 (tentative date 2027-07-01) and deployed a configuration change to restore compatibility for these workflows. All affected tools and integrations should now be operating normally & will be updated prior to the modified end-of-life-date. From 2026-03-01 00:00 UTC to 2026-03-02 12:01 UTC, users relying on these older API versions may have experienced failed requests and associated automation errors. No user action is required. Previously failed operations can be retried and should now succeed.

MongoDB Atlas Admin API: Temporary failures for tools using older API versions

Mar <var data-var='date'> 2</var>, <var data-var='time'>03:05</var> UTC Resolved - This incident has been resolved.Mar <var data-var='date'> 1</var>, <var data-var='time'>05:37</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Feb <var data-var='date'>28</var>, <var data-var='time'>19:53</var> UTC Investigating - We are currently investigating an issue with Atlas App Services Device Sync. Affected users of this deprecated service may see SSL validation errors. We will update this post with more details as they become available.

MongoDB App Services: Connectivity issues

Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates)  and AWS me-south-1 (Bahrain)

Feb <var data-var='date'>26</var>, <var data-var='time'>20:04</var> UTC Resolved - The issue has been resolvedFeb <var data-var='date'>26</var>, <var data-var='time'>19:51</var> UTC Monitoring - A fix has been implemented and we're monitoring the results.Feb <var data-var='date'>26</var>, <var data-var='time'>19:21</var> UTC Investigating - We are currently experiencing degraded service with our DataDog integration for several DataDog regions. This may result in incomplete metrics, or issues with alerting for customers using the DataDog integration. We are investigating this issue.

DataDog Integration Degraded Experience

Feb <var data-var='date'>20</var>, <var data-var='time'>16:59</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>20</var>, <var data-var='time'>16:54</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Feb <var data-var='date'>19</var>, <var data-var='time'>21:35</var> UTC Update - We are continuing to investigate reports of Atlas Data Federation and Online Archive schema tables failing to load. As a workaround, please connect directly and run the sqlGetSchema command: https://www.mongodb.com/docs/sql-interface/schema/view/ If that does not work, you may need to generate the schema first: https://www.mongodb.com/docs/sql-interface/schema/create/#create-schema-using-mongosh It appears to affect only a very small number of users, but we will keep this alert open until the issue is resolved.Feb <var data-var='date'>19</var>, <var data-var='time'>18:50</var> UTC Investigating - We are investigating reports of Atlas Data Federation and Online Archive schema tables failing to load. As a workaround, please connect directly and run the sqlGetSchema command: https://www.mongodb.com/docs/sql-interface/schema/view/ If that does not work, you may need to generate the schema first: https://www.mongodb.com/docs/sql-interface/schema/create/#create-schema-using-mongosh

MongoDB Atlas Data Federation and Online Archive: Schema Table fails to load

Feb <var data-var='date'>13</var>, <var data-var='time'>17:57</var> UTC Resolved - The DNS records have been backfilled and clusters that had these IP addresses should be recovered.Feb <var data-var='date'>13</var>, <var data-var='time'>16:42</var> UTC Identified - We have identified the root cause and are working on backfilling those records with AWS support. We have also disabled that ip range for new clusters so moving forward this issue will not be hit for new AWS clusters.Feb <var data-var='date'>13</var>, <var data-var='time'>16:11</var> UTC Investigating - We are investigating an issue with DNS resolution for public IP addresses within 31.89.0.0/24. We are engaging with AWS support to remediate the situation.

DNS Resolution failures for public IP addresses within 31.89.0.0/24

Feb <var data-var='date'>13</var>, <var data-var='time'>07:55</var> UTC Resolved - We have identified and resolved the issue. Atlas UI will load without a delay now.Feb <var data-var='date'>13</var>, <var data-var='time'>07:20</var> UTC Investigating - We are currently investigating reports of the slow loading of the Atlas web UI.

MongoDB Atlas: Atlas UI loading slowly

Feb <var data-var='date'>12</var>, <var data-var='time'>23:10</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>12</var>, <var data-var='time'>23:08</var> UTC Monitoring - We have implemented the fix. Customers will now be able to create new clusters on AWS.Feb <var data-var='date'>12</var>, <var data-var='time'>23:00</var> UTC Identified - We have identified the root cause and are implementing a fix to remediate the situationFeb <var data-var='date'>12</var>, <var data-var='time'>22:10</var> UTC Investigating - We are currently investigating elevated errors for customers attempting to create a cluster on AWS

Elevated errors for cluster creation on AWS

Feb <var data-var='date'> 7</var>, <var data-var='time'>11:43</var> UTC Resolved - Many nodes have recovered in the impacted region, however there are still some impacted nodes that are recovering. Azure's latest update at 11:05 UTC on 07 February 2026 indicates they are observing signs of partial recovery and that recovery efforts remain in progress. We are resolving the status post as we expect our system to automatically remediate any lingering issues. Please follow the Azure status post for further updates on the regional outage remediation efforts from their end.Feb <var data-var='date'> 7</var>, <var data-var='time'>10:11</var> UTC Monitoring - We are seeing some nodes in the impacted Azure West US region recovering. We will continue to monitor and provide updates.Feb <var data-var='date'> 7</var>, <var data-var='time'>09:15</var> UTC Identified - Azure has posted the following to their public Status Page: https://azure.status.microsoft/en-us/status Ongoing Service Degradation in West US We are aware of an issue impacting a subset of customers in West US, Our Engineering team is actively investigating and working on mitigation. We will provide more information shortly. This message was last updated at 09:10 UTC on 07 February 2026Feb <var data-var='date'> 7</var>, <var data-var='time'>09:07</var> UTC Investigating - We are observing widespread issues in Azure West US. Customers may see nodes reporting as “down” and delayed cluster modifications for Azure clusters in West US.

Partial outage in Azure West US

Feb <var data-var='date'> 4</var>, <var data-var='time'>21:06</var> UTC Resolved - The root cause has been identified and the issue is now resolved.Feb <var data-var='date'> 3</var>, <var data-var='time'>16:12</var> UTC Update - We are continuing to investigate the issue. A subset of customers may experience incomplete metric data in their DataDog integration. We'll share updates as more information becomes available.Jan <var data-var='date'>30</var>, <var data-var='time'>01:00</var> UTC Investigating - We are currently experiencing degraded service with our DataDog integration for several DataDog regions. This may result in incomplete metrics, or issues with alerting for customers using the DataDog integration. We are investigating this issue.

Feb <var data-var='date'> 3</var>, <var data-var='time'>19:15</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'> 3</var>, <var data-var='time'>18:50</var> UTC Update - We are continuing to work on a fix for this issue.Feb <var data-var='date'> 3</var>, <var data-var='time'>18:49</var> UTC Identified - Users may be unable to access the MongoDB Atlas App Services triggers page and may see authentication failures when using the Admin API. As a result, some users may be unable to create, update, or manage App Services resources. We have identified an issue with a recent change to authentication and are working to revert those changes.

Triggers UI and Admin API authentication issues

Jan <var data-var='date'>29</var>, <var data-var='time'>23:55</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>29</var>, <var data-var='time'>23:54</var> UTC Monitoring - We have deployed a fix and are seeing activity feed pages load again.Jan <var data-var='date'>29</var>, <var data-var='time'>23:34</var> UTC Update - The revert of the recent change did not meaningfully help the situation. However, we have looked into the issue more and have a better idea of the root cause. We will have another update shortly.Jan <var data-var='date'>29</var>, <var data-var='time'>23:24</var> UTC Update - We are reverting a recent change in one of the impacted services. We will have an update after that rolls out.Jan <var data-var='date'>29</var>, <var data-var='time'>22:30</var> UTC Investigating - We are currently investigating an issue with the activity feed. We will update as the we learn more.

Activity Feed is experiencing degraded performance

THIS IS A SCHEDULED EVENT Jan <var data-var='date'>29</var>, <var data-var='time'>00:00</var> UTC &nbsp;-&nbsp; Feb <var data-var='date'>1</var>, <var data-var='time'>00:00</var> UTCJan <var data-var='date'>28</var>, <var data-var='time'>19:41</var> UTC Scheduled - Please note that this is courtesy notice and no action is required from you if you do not pin intermediate certificates from Let's Encrypt (LE) and/or Google Trust Services (GTS) in your environment when connecting to Atlas dedicated clusters. Let's Encrypt (LE) and Google Trust Services (GTS) have issued additional intermediate certificates to their services. Intermediate certificates act as a secure bridge between root CAs (e.g. LE/GTS) and end entities to streamline management and reduce risk. We want to emphasize that the changes mentioned below related to intermediate certificate authority are not made by MongoDB but by LE and GTS sometime in 2026 which are the Certificate Authority (CA) providers for TLS certificates for all MongoDB Atlas clusters. Let’s Encrypt: https://letsencrypt.org/2025/11/24/gen-y-hierarchy Google Trust Service: https://pki.goog/updates/august2025-intermediate-update.html MongoDB does not recommend hardcoding or pinning intermediate CAs in your application; please refer to the best practices recommended by MongoDB here. If you have any questions or need assistance, please use the chat (https://www.mongodb.com/company/contact) in the Atlas UI or contact Support (https://support.mongodb.com/welcome) to talk to someone on our team.

Courtesy Notice - Intermediate Certificate Authority (CA) change notification from Let’s Encrypt (LE) and Google Trust Services (GTS)

Dec <var data-var='date'>20</var>, <var data-var='time'>00:28</var> UTC Resolved - Issue is resolved, and affected components are confirmed to be operational again.Dec <var data-var='date'>19</var>, <var data-var='time'>22:42</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Dec <var data-var='date'>19</var>, <var data-var='time'>21:57</var> UTC Update - We have identified an issue causing the following symptoms: - Atlas Data Explorer connections and queries failing - Atlas Data Federation and Online Archive queries failing, as well as the creation of new Data Federation or Online Archive instances - Atlas Stream Processing being interrupted - MongoDB Charts data being delayed Affected users will see the above symptoms, often with timeout or host not found errors. Underlying cluster health is unaffected, including Atlas search queries. Additionally, Vercel users may not be able to get directly to Atlas from within Vercel. As a workaround, users are encouraged to login directly to Atlas at cloud.mongodb.comDec <var data-var='date'>19</var>, <var data-var='time'>21:51</var> UTC Identified - We have identified an issue causing the following symptoms: - Atlas Data Explorer connections and queries failing - Atlas Data Federation and Online Archive queries failing - Atlas Stream Processing being interrupted - MongoDB Charts data being delayed Affected users will see the above symptoms, often with timeout or host not found errors. Underlying cluster health is unaffected, including Atlas search queries.Dec <var data-var='date'>19</var>, <var data-var='time'>21:46</var> UTC Update - We are continuing to investigate this issue.Dec <var data-var='date'>19</var>, <var data-var='time'>21:45</var> UTC Investigating - We are investigating report of issues connecting and authenticating to Atlas Data Federation and Online Archive instances.

Issue connecting to Atlas Data Federation and Online Archive

Dec <var data-var='date'>16</var>, <var data-var='time'>00:30</var> UTC Resolved - This incident has been resolved.Dec <var data-var='date'>10</var>, <var data-var='time'>01:51</var> UTC Monitoring - This status alert only applies to customers who deployed MongoDB Atlas via the Vercel Marketplace. We are asking customers to promptly redeploy their Vercel applications. As part of our response to the React’s CVE-2025-55182 (https://vercel.com/changelog/cve-2025-55182) the critical security advisory affecting React Server Components, some MongoDB customers will need to take action. Specifically, MongoDB Atlas customers who deployed clusters via the Vercel Marketplace will need to ensure their applications are running on an unaffected version of Next.js (instructions here: https://vercel.com/kb/bulletin/react2shell) and redeploy their Vercel applications (instructions here: https://vercel.com/docs/deployments/managing-deployments). This is to avoid a loss of database connectivity from your Vercel deployment. All other Atlas functionality is unaffected. Users who have not deployed MongoDB Atlas via the Vercel Marketplace are not affected.

Is Mongo DB Atlas down?

Mongo DB Atlas status is PARTIAL OUTAGE

Components with issues

Lastest published events

Cluster operations will be delayed due to DNS maintenance activities in MongoDB Atlas for Government

Atlas Charts users unable to login

MongoDB Atlas for Government: SSO login failures for some users

Mongo DB Atlas Services, Components and Regions

Recent Mongo DB Atlas events

Cluster operations will be delayed due to DNS maintenance activities in MongoDB Atlas for Government

Atlas Charts users unable to login

MongoDB Atlas for Government: SSO login failures for some users

Delays in cluster creation and adding new cluster nodes in Azure East US 2 region

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

Issue querying Azure blob storage containers in Atlas Data Federation

Get your FREE account now,
5 monitors included!

Is Mongo DB Atlas down?

Mongo DB Atlas status is PARTIAL OUTAGE

Components with issues

Lastest published events

Cluster operations will be delayed due to DNS maintenance activities in MongoDB Atlas for Government

Atlas Charts users unable to login

MongoDB Atlas for Government: SSO login failures for some users

Mongo DB Atlas Services, Components and Regions

Recent Mongo DB Atlas events

Cluster operations will be delayed due to DNS maintenance activities in MongoDB Atlas for Government

Atlas Charts users unable to login

MongoDB Atlas for Government: SSO login failures for some users

Delays in cluster creation and adding new cluster nodes in Azure East US 2 region

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

Issue querying Azure blob storage containers in Atlas Data Federation

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!