New Multi-region uptime checks and custom-domain status pages

MongoDB Atlas Outage History

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

Jul 15Oct 12

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 14 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Issue impacting Atlas Search availability on certain clusters
major Observed active window 1h 50m

View incident details and source

Started:

MongoDB Atlas Search
monitoring
A fix has been deployed and we are monitoring.
identified
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
minor Observed active window 5h 3m

View incident details and source

Started:

MongoDB Charts
identified
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.
Trigger processing may be delayed globally
major Observed active window 5h 13m

View incident details and source

Started:

MongoDB Atlas App Services and Device Sync
monitoring
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.
September 2026
Support Portal Outage
major Observed active window 6h 28m

View incident details and source

Started:

MongoDB Support Portal
investigating
We are continuing to investigate this issue.
investigating
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
minor Observed active window 2h 26m

View incident details and source

Started:

MongoDB Cloud MongoDB Atlas for Government
monitoring
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
major

View incident details and source

Started:

MongoDB Cloud
monitoring
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.

July 2026
Atlas is experiencing issues with issuing certificates from Lets Encrypt
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are no longer seeing failures with cert issuance from Lets Encrypt. We are still investigating the root cause of the original errors and will continue to monitor.
investigating
We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Tenant cluster provisioning is currently impacted.
Atlas Data Federation and Online Archive cloud-provider IAM authentication error
minor Source 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 that the issue is caused by a recent configuration change to IAM authentication and are working on a fix.
investigating
Users of Atlas Data Federation and Online Archive using cloud-provider IAM authentication may see pipelines fail with an error when querying backing Atlas clusters. Other authentication methods are unaffected. As a temporary workaround, users can use SCRAM authentication.
Impaired Cluster Operations due to Lets Encrypt Service Degradation
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are currently monitoring the status of Lets Encrypt after an issue with their API. Tenant clusters and Atlas for Government clusters will experience delays in provisioning due to Lets Encrypt service degradation.
Impaired Cluster Operations due to Lets Encrypt Outage
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are currently monitoring the status of Lets Encrypt. Tenant clusters and Atlas for Government clusters will experience delays in provisioning due to Lets Encrypt service degradation.
AWS cluster backup and restore operations are failing
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 currently investigating the issue where AWS cluster backup and restores are failing. This includes exports and manual downloads as well as restoring to another cluster. We are also investigation potential impact to other operations on AWS clusters such as modifying instance size.
June 2026
Increased error rate creating and managing Search and Vector Search indexes
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results
Investigating connection issues to ADFA in GCP
major Source not attested
Last archived state: resolved
View archived record details
monitoring
All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.
identified
Issues connecting to ADF and OA instances in GCP belgium-eu region has been mitigated, and working on other GCP regions.
identified
We've identified an issue with networking in GCP regions and are working on fix
investigating
We are currently investigating issues connecting and querying to Atlas Data Federation and Online Archive instances in GCP regions
May 2026
Metrics may fail to send to DataDog Gov integrations
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Starting approximately 17:00 UTC, some Atlas for Government users may be experiencing gaps in metrics sent to their DataDog Gov integration. We are investigating this issue.
Authentication failures when running search queries for some clusters
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.
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.
investigating
We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.
[Atlas for Government] Data plane node logs unavailable for last 6 days
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.
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.