MongoDB Cloud

All Systems Operational

MongoDB Cloud Operational
MongoDB Support Portal Operational
MongoDB Atlas App Services and Device Sync Operational
MongoDB Atlas Data Federation and Online Archive Operational
MongoDB Atlas Search Operational
MongoDB Charts Operational
MongoDB Atlas Stream Processing Operational
MongoDB Atlas for Government Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Courtesy Notice - Intermediate Certificate Authority (CA) change notification from Let’s Encrypt (LE) and Google Trust Services (GTS) Jan 29, 2026 00:00 - Feb 1, 2026 00:00 UTC

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.
Posted on Jan 28, 2026 - 19:41 UTC
Feb 26, 2026
DataDog Integration Degraded Experience
Resolved - The issue has been resolved
Feb 26, 20:04 UTC
Monitoring - A fix has been implemented and we're monitoring the results.
Feb 26, 19:51 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 26, 19:21 UTC
Feb 25, 2026

No incidents reported.

Feb 24, 2026

No incidents reported.

Feb 23, 2026

No incidents reported.

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026
MongoDB Atlas Data Federation and Online Archive: Schema Table fails to load
Resolved - This incident has been resolved.
Feb 20, 16:59 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 20, 16:54 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 19, 21:35 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
Feb 19, 18:50 UTC
Feb 19, 2026
Feb 18, 2026

No incidents reported.

Feb 17, 2026

No incidents reported.

Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026
DNS Resolution failures for public IP addresses within 31.89.0.0/24
Resolved - The DNS records have been backfilled and clusters that had these IP addresses should be recovered.
Feb 13, 17:57 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 13, 16:42 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.
Feb 13, 16:11 UTC
MongoDB Atlas: Atlas UI loading slowly
Resolved - We have identified and resolved the issue. Atlas UI will load without a delay now.
Feb 13, 07:55 UTC
Investigating - We are currently investigating reports of the slow loading of the Atlas web UI.
Feb 13, 07:20 UTC
Feb 12, 2026
Elevated errors for cluster creation on AWS
Resolved - This incident has been resolved.
Feb 12, 23:10 UTC
Monitoring - We have implemented the fix. Customers will now be able to create new clusters on AWS.
Feb 12, 23:08 UTC
Identified - We have identified the root cause and are implementing a fix to remediate the situation
Feb 12, 23:00 UTC
Investigating - We are currently investigating elevated errors for customers attempting to create a cluster on AWS
Feb 12, 22:10 UTC
← Incident History Powered by Atlassian Statuspage