Mongodb

Mar 9, 16:02 UTC
Update - According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.

We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed.

We will provide another update by March 10 at 16:00 UTC, or sooner if new information becomes available.

If …

Mar 2, 16:28 UTC
Resolved - This incident has been resolved. Email notifications are being sent successfully.

Mar 2, 15:50 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.

Mar 2, 03:05 UTC
Resolved - This incident has been resolved.

Mar 1, 05:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 28, 19:53 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.

Feb 26, 20:04 UTC
Resolved - The issue has been resolved

Feb 26, 19:51 UTC
Monitoring - A fix has been implemented and we're monitoring the results.

Feb 26, 19:21 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 20, 16:59 UTC
Resolved - This incident has been resolved.

Feb 20, 16:54 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 19, 21:35 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, 18:50 UTC
Investigating - We are …

Feb 13, 17:57 UTC
Resolved - The DNS records have been backfilled and clusters that had these IP addresses should be recovered.

Feb 13, 16:42 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:11 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, 07:55 UTC
Resolved - We have identified and resolved the issue. Atlas UI will load without a delay now.

Feb 13, 07:20 UTC
Investigating - We are currently investigating reports of the slow loading of the Atlas web UI.

Feb 12, 23:10 UTC
Resolved - This incident has been resolved.

Feb 12, 23:08 UTC
Monitoring - We have implemented the fix. Customers will now be able to create new clusters on AWS.

Feb 12, 23:00 UTC
Identified - We have identified the root cause and are implementing a fix to remediate the situation

Feb 12, 22:10 UTC
Investigating - We are currently investigating elevated errors for customers attempting to create a cluster on AWS