May <var data-var='date'>24</var>, <var data-var='time'>02:05</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>24</var>, <var data-var='time'>00:14</var> UTC Monitoring - We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact. May <var data-var='date'>23</var>, <var data-var='time'>20:14</var> UTC Identified - We have identified the root cause of the search query failures and are working on a mitigation for impacted clusters. Clusters with dedicated search nodes are unaffected. Some clusters with colocated search nodes may see search query failures. May <var data-var='date'>23</var>, <var data-var='time'>19:48</var> UTC Investigating - We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.

Authentication failures when running search queries for some clusters

May <var data-var='date'>22</var>, <var data-var='time'>22:17</var> UTC Resolved - The data plane node log download has recovered. May <var data-var='date'>22</var>, <var data-var='time'>21:17</var> UTC Monitoring - We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes. May <var data-var='date'>22</var>, <var data-var='time'>20:32</var> UTC Investigating - The data plane node logs (mongod, audit logs, etc.) are unavailable since May 14th 4am UTC for clusters in GCP and AWS gov-cloud regions. We have identified the root cause and are actively working on a fix.

[Atlas for Government] Data plane node logs unavailable for last 6 days

May <var data-var='date'> 9</var>, <var data-var='time'>14:24</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>20:41</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>12:34</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>03:12</var> UTC 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. May <var data-var='date'> 8</var>, <var data-var='time'>02:24</var> UTC 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 Availability Zone use1-az4 in US-EAST-1 Region is Impaired

May <var data-var='date'> 8</var>, <var data-var='time'>22:07</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>21:39</var> UTC Update - Lets Encrypt is now reporting as healthy. We will continue monitoring as cluster operations return to a healthy state. May <var data-var='date'> 8</var>, <var data-var='time'>19:33</var> UTC Monitoring - Cluster operations are currently impaired due to issues with Lets Encrypt. We are actively monitoring the situation as more updates come in.

Impaired Cluster Operations due to Lets Encrypt Outage

May <var data-var='date'> 7</var>, <var data-var='time'>22:15</var> UTC Resolved - DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected. May <var data-var='date'> 7</var>, <var data-var='time'>19:47</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'> 7</var>, <var data-var='time'>19:47</var> UTC 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. May <var data-var='date'> 7</var>, <var data-var='time'>17:50</var> UTC 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. May <var data-var='date'> 7</var>, <var data-var='time'>16:58</var> UTC Update - Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun. May <var data-var='date'> 7</var>, <var data-var='time'>15:20</var> UTC Update - 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. May <var data-var='date'> 7</var>, <var data-var='time'>15:17</var> UTC Identified - DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.

AWS Cluster DNS Changes Degraded Performance

May <var data-var='date'> 7</var>, <var data-var='time'>20:55</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 7</var>, <var data-var='time'>20:02</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 7</var>, <var data-var='time'>01:20</var> UTC Update - We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC. May <var data-var='date'> 6</var>, <var data-var='time'>21:48</var> 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

Atlas Backup Export Jobs Degraded Performance

May <var data-var='date'> 5</var>, <var data-var='time'>17:28</var> UTC Resolved - We are no longer observing these issues in Azure West Europe. Atlas Clusters in the region should be healthy and fully operational. May <var data-var='date'> 3</var>, <var data-var='time'>20:19</var> UTC 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. May <var data-var='date'> 3</var>, <var data-var='time'>17:33</var> UTC 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.

Partial outage in Azure West Europe

Apr <var data-var='date'>27</var>, <var data-var='time'>20:50</var> UTC Resolved - We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us. Apr <var data-var='date'>27</var>, <var data-var='time'>17:16</var> UTC 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 at 22:00 UTC.

Increase in Billing for Backup Usage

Apr <var data-var='date'>21</var>, <var data-var='time'>13:45</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>20</var>, <var data-var='time'>19:17</var> UTC 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. Apr <var data-var='date'>17</var>, <var data-var='time'>20:24</var> UTC 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. Apr <var data-var='date'>17</var>, <var data-var='time'>17:03</var> UTC 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.

MongoDB Atlas BI Connector: Connections and queries fail

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 resolved Feb <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.

Is Mongo DB Atlas down?

Mongo DB Atlas status is UP

Lastest published events

Authentication failures when running search queries for some clusters

[Atlas for Government] Data plane node logs unavailable for last 6 days

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Mongo DB Atlas Services, Components and Regions

Recent Mongo DB Atlas events

Authentication failures when running search queries for some clusters

[Atlas for Government] Data plane node logs unavailable for last 6 days

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Impaired Cluster Operations due to Lets Encrypt Outage

AWS Cluster DNS Changes Degraded Performance

Atlas Backup Export Jobs Degraded Performance

Get your FREE account now,
5 monitors included!

Is Mongo DB Atlas down?

Mongo DB Atlas status is UP

Lastest published events

Authentication failures when running search queries for some clusters

[Atlas for Government] Data plane node logs unavailable for last 6 days

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Mongo DB Atlas Services, Components and Regions

Recent Mongo DB Atlas events

Authentication failures when running search queries for some clusters

[Atlas for Government] Data plane node logs unavailable for last 6 days

AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired

Impaired Cluster Operations due to Lets Encrypt Outage

AWS Cluster DNS Changes Degraded Performance

Atlas Backup Export Jobs Degraded Performance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!