{"provider":"mongodb","label":"MongoDB","source":"https://status.mongodb.com","license":"CC BY 4.0","citeAs":"Repose, \"MongoDB incident history\", https://repose.sh/upstream/mongodb","generatedAt":"2026-09-25T19:45:35.836Z","count":50,"incidents":[{"id":"bm948zqk8djr","title":"Support Portal Outage","impact":"major","status":"resolved","startedAt":"2026-09-16T09:06:55.000Z","resolvedAt":"2026-09-16T15:31:51.174Z","updatedAt":"2026-09-16T15:32:24.880Z","components":["MongoDB Support Portal"],"url":"https://stspg.io/yc66h52gr7zg","updates":[{"at":"2026-09-16T09:06:55.000Z","body":"MongoDB customers are currently experiencing degraded or limited access to the MongoDB Customer Support Portal (https://support.mongodb.com/).\n\nIf 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:\n\n[These numbers have been removed. Active MongoDB customers can access them at the support portal.]\n\nWe appreciate your patience.","status":"investigating"},{"at":"2026-09-16T09:09:18.687Z","body":"We are continuing to investigate this issue.","status":"investigating"},{"at":"2026-09-16T15:31:51.174Z","body":"The MongoDB Support Portal experienced service degradation issues between approximately 2026-09-16 09:00 UTC and 2026-09-16 15:15 UTC.  These platform issues have been resolved.\n\nWe apologize for the service interruption and greatly appreciate your patience. \n\nRegards, \nThe MongoDB Team","status":"resolved"}]},{"id":"x8kqzkjlz8gd","title":"Atlas is experiencing issues with issuing certificates from Lets Encrypt","impact":"minor","status":"resolved","startedAt":"2026-09-11T01:28:19.000Z","resolvedAt":"2026-09-11T03:51:19.804Z","updatedAt":"2026-09-11T03:51:19.819Z","components":["MongoDB Cloud","MongoDB Atlas for Government"],"url":"https://stspg.io/hxqhp3d2p4nt","updates":[{"at":"2026-09-11T01:28:19.000Z","body":"We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.","status":"investigating"},{"at":"2026-09-11T02:01:46.326Z","body":"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.","status":"monitoring"},{"at":"2026-09-11T03:51:19.804Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"yhvvsfvwyf1h","title":"Impaired Cluster operations in AWS me-central-1 and AWS me-south-1","impact":"major","status":"monitoring","startedAt":"2026-09-03T16:44:43.828Z","resolvedAt":null,"updatedAt":"2026-09-03T16:47:21.743Z","components":["MongoDB Cloud"],"url":"https://stspg.io/jwd31x8yx3q5","updates":[{"at":"2026-09-03T16:44:43.899Z","body":"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.","status":"monitoring"},{"at":"2026-09-03T16:47:21.740Z","body":"We are continuing to monitor for any further issues.","status":"monitoring"}]},{"id":"844wt28jx8z4","title":"MongoDB Atlas Log Integration service degraded","impact":"minor","status":"resolved","startedAt":"2026-08-28T18:34:33.239Z","resolvedAt":"2026-08-28T14:30:00.000Z","updatedAt":"2026-08-28T18:34:39.042Z","components":[],"url":"https://stspg.io/yh337w1rxdlj","updates":[{"at":"2026-08-28T14:30:00.000Z","body":"Between approximately 14:29 UTC and 15:42 UTC on August 28, 2026, log delivery via Atlas Log Integration was impacted due to an internal service issue. Some users may have encountered delayed or missing logs during this window. Log delivery has since returned to normal. We are implementing measures to reduce the risk of this happening again.","status":"resolved"}]},{"id":"84lrdmgxt757","title":"Issues rotating certificates for projects containing only Atlas Free and Flex clusters","impact":"none","status":"resolved","startedAt":"2026-08-19T20:45:49.000Z","resolvedAt":"2026-08-20T22:07:16.414Z","updatedAt":"2026-08-20T22:07:16.430Z","components":["MongoDB Cloud"],"url":"https://stspg.io/qbmmtp87vb40","updates":[{"at":"2026-08-19T20:45:49.000Z","body":"We have identified an issue impacting certain projects containing only Free or Flex clusters. For those clusters, TLS certificates are not being rotated correctly. This could lead to an inability to connect to your Free or Flex cluster. We are working on remediation steps.","status":"identified"},{"at":"2026-08-19T21:50:56.000Z","body":"We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue.","status":"monitoring"},{"at":"2026-08-19T21:57:54.000Z","body":"We are continuing to monitor for any further issues.","status":"monitoring"},{"at":"2026-08-19T21:58:51.847Z","body":"We are continuing to monitor for any further issues.","status":"monitoring"},{"at":"2026-08-19T22:00:16.000Z","body":"We are continuing to monitor for any further issues.","status":"monitoring"},{"at":"2026-08-20T21:39:11.077Z","body":"We have deployed fix, continuing the monitor for any further issues.","status":"monitoring"},{"at":"2026-08-20T22:07:16.414Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"8t1spyy2s5rl","title":"Atlas UI and API Periodic Unavailability","impact":"minor","status":"resolved","startedAt":"2026-08-18T14:10:56.000Z","resolvedAt":"2026-08-18T15:17:11.000Z","updatedAt":"2026-08-18T20:07:15.341Z","components":["MongoDB Cloud"],"url":"https://stspg.io/4nf1gtb8506m","updates":[{"at":"2026-08-18T14:10:56.000Z","body":"We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.","status":"investigating"},{"at":"2026-08-18T14:57:05.540Z","body":"We have identified a new workload that was putting more load than expected on the backing system.  We are working on disabling it.  Customer clusters remain unaffected.","status":"identified"},{"at":"2026-08-18T15:04:19.128Z","body":"We have disabled the workload and are monitoring the situation","status":"monitoring"},{"at":"2026-08-18T15:17:11.000Z","body":"This incident has been resolved.\n\nFollowing the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes.\n\nThe issue was related to this incident \"Atlas UI and API Periodic Unavailability\" which has been remediated.\n\nCustomer clusters and their data were not affected; the impact was limited to the timing of control-plane operations. This jobs issue has been resolved as well.","status":"resolved"}]},{"id":"f90g1tjzpdy2","title":"GCP capacity constraints affecting Atlas deployments","impact":"major","status":"resolved","startedAt":"2026-08-05T05:17:26.000Z","resolvedAt":"2026-08-05T12:14:01.952Z","updatedAt":"2026-08-05T12:14:01.967Z","components":["MongoDB Cloud"],"url":"https://stspg.io/5skglmlv07mf","updates":[{"at":"2026-08-05T05:17:26.000Z","body":"We are investigating an issue with Google Cloud Platform (GCP) capacity that is affecting some MongoDB Atlas customers across multiple GCP regions and geographies. We expect the scope of this issue to continue to expand as our investigation progresses. It currently includes, but is not limited to, multiple GCP regions across North America, Europe, and Asia Pacific/Australia, as well as M50 and S70L instance types.\n\nCustomers may experience errors or delays when creating or modifying Atlas clusters, particularly deployments with search nodes. Some customers may also see host-down alerts while this issue is ongoing.\n\nMongoDB is working with GCP to understand the scope of the issue and restore capacity.\n\nCustomers encountering provisioning issues may retry later or consider using a different GCP region, cloud provider, or instance size. If you are experiencing a time-sensitive production impact, please contact MongoDB Support through the Support Portal or the in-product support chat.\n\nWe will provide another update as more information becomes available.","status":"investigating"},{"at":"2026-08-05T12:14:01.952Z","body":"We believe the symptoms of this have largely subsided, looking at both customer cases and our internal metrics. We will share any more information as we get it, but for now resolving this incident as Atlas is fully operational.","status":"resolved"}]},{"id":"2zp8gbb9dtf7","title":"Elevated errors on VoyageAI APIs","impact":"major","status":"resolved","startedAt":"2026-08-03T18:47:47.650Z","resolvedAt":"2026-08-03T21:18:54.577Z","updatedAt":"2026-08-03T21:18:54.591Z","components":["VoyageAI Embedding and Reranking Models"],"url":"https://stspg.io/1d1g8p97f2g6","updates":[{"at":"2026-08-03T18:47:47.714Z","body":"VoyageAI APIs are experiencing elevated 5xx errors. We are investigating the issue.","status":"investigating"},{"at":"2026-08-03T19:02:33.822Z","body":"A fix has been applied and we are monitoring the system.","status":"monitoring"},{"at":"2026-08-03T21:18:54.577Z","body":"The system has returned to normal operation.","status":"resolved"}]},{"id":"rhj2h4scwdhk","title":"Delayed cluster configuration affecting free and flex users","impact":"minor","status":"resolved","startedAt":"2026-07-29T18:55:32.002Z","resolvedAt":"2026-07-29T19:37:20.776Z","updatedAt":"2026-07-29T19:37:20.792Z","components":["MongoDB Cloud"],"url":"https://stspg.io/wqmybtc16s68","updates":[{"at":"2026-07-29T18:55:32.099Z","body":"We are investigating an issue with cluster configuration updates getting delayed for a subset of users on free and flex tiers.  Cluster access is unaffected.","status":"investigating"},{"at":"2026-07-29T19:06:25.829Z","body":"We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.","status":"identified"},{"at":"2026-07-29T19:31:02.800Z","body":"We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.","status":"monitoring"},{"at":"2026-07-29T19:37:20.776Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"c5mvtstmt6pm","title":"Atlas Stream Processing errors in Azure West Europe","impact":"none","status":"resolved","startedAt":"2026-07-29T18:11:59.174Z","resolvedAt":"2026-07-29T22:47:06.717Z","updatedAt":"2026-07-29T22:47:06.736Z","components":["MongoDB Atlas Stream Processing"],"url":"https://stspg.io/07211g8rn4f0","updates":[{"at":"2026-07-29T18:11:59.246Z","body":"We are investigating an issue affecting Atlas Stream Processing in Azure West Europe. Some users may see processors in this region encounter internal errors. We are actively investigating and will share another update as soon as we have more information.","status":"investigating"},{"at":"2026-07-29T22:35:59.290Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-07-29T22:47:06.717Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"j9qrqtwlq8jg","title":"VoyageAI elevated errors","impact":"major","status":"resolved","startedAt":"2026-07-27T23:37:13.259Z","resolvedAt":"2026-07-27T23:48:13.000Z","updatedAt":"2026-07-28T16:24:10.737Z","components":["VoyageAI Embedding and Reranking Models"],"url":"https://stspg.io/3jdp09pjhycy","updates":[{"at":"2026-07-27T23:37:13.361Z","body":"All VoyageAI models are experiencing elevated errors. We are investigating the issue.","status":"investigating"},{"at":"2026-07-27T23:47:22.814Z","body":"We have fully recovered as of 16:41 PST.","status":"investigating"},{"at":"2026-07-27T23:48:13.000Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"ktcy0km7x49f","title":"Cluster connectivity issues in Azure westus","impact":"major","status":"resolved","startedAt":"2026-07-23T16:21:52.120Z","resolvedAt":"2026-07-23T20:28:31.986Z","updatedAt":"2026-07-23T20:28:32.005Z","components":["MongoDB Cloud"],"url":"https://stspg.io/ycvlxh9rhwkw","updates":[{"at":"2026-07-23T16:21:52.224Z","body":"We are currently investigating an issue with Azure clusters in westus region.  Please refer to the azure status post here for more information https://azure.status.microsoft/en-us/status.","status":"investigating"},{"at":"2026-07-23T16:38:12.249Z","body":"Azure has confirmed that there are networking issues in the westus region.  Please follow the official azure status post for more detailed updates https://azure.status.microsoft/en-us/status","status":"identified"},{"at":"2026-07-23T18:26:11.821Z","body":"We are aware of an ongoing Azure networking incident affecting the West US region. Some Atlas clusters hosted in Azure West US may experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. Azure is investigating the issue and evaluating mitigation options. We will provide additional updates as more information becomes available.","status":"identified"},{"at":"2026-07-23T18:54:50.160Z","body":"Azure is rolling out a mitigation for the ongoing networking incident affecting the West US region, and we are seeing signs of recovery. Some Atlas clusters hosted in Azure West US may continue to experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. We are monitoring recovery closely and will provide additional updates as more information becomes available.","status":"identified"},{"at":"2026-07-23T20:28:31.986Z","body":"Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete.","status":"resolved"}]},{"id":"qjk952jxg2kk","title":"MongoDB Atlas and Atlas for Government: New AWS Backup and AWS Data Transfer costs will be unavailable between July 17 and 20","impact":"none","status":"resolved","startedAt":"2026-07-17T16:14:17.495Z","resolvedAt":"2026-07-21T13:08:15.991Z","updatedAt":"2026-07-21T13:08:16.010Z","components":["MongoDB Cloud","MongoDB Atlas for Government"],"url":"https://stspg.io/klx123hc5vs8","updates":[{"at":"2026-07-17T16:14:17.559Z","body":"Due to an ongoing incident with AWS's billing data, MongoDB Atlas and Atlas for Government will not be updating AWS network or backup consumption data over this weekend, 2026-07-17 through 2026-07-20. The products themselves will remain fully available. When the upstream issue has been resolved, we intend to display and bill for the correct amounts. Charges will have usage dates that correctly express the usage, but will have the billed date of when this is corrected.\n\nCluster and backup health are unaffected. Other cloud providers' billing data is unaffected.\n\nYou can follow the upstream incident at https://health.aws.amazon.com/health/status","status":"identified"},{"at":"2026-07-20T15:06:07.113Z","body":"The upstream issue has been corrected. After approximately 0400 UTC on 2026-07-21, most, if not all, of the updated backup and network consumption on AWS will be reflected in MongoDB Atlas and Atlas for Government. Thank you for your patience during this incident.","status":"monitoring"},{"at":"2026-07-21T13:08:15.991Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"7qbn0jlhvngz","title":"Atlas Stream Processing is experiencing issues in Azure - West Europe","impact":"minor","status":"resolved","startedAt":"2026-07-09T23:03:56.359Z","resolvedAt":"2026-07-10T01:11:09.868Z","updatedAt":"2026-07-10T01:11:09.883Z","components":["MongoDB Atlas Stream Processing"],"url":"https://stspg.io/896391t5m0lb","updates":[{"at":"2026-07-09T23:03:56.434Z","body":"We are currently investigating an issue affecting Stream Processing Azure West Europe. User initiated commands & workloads may see intermittent failures.","status":"investigating"},{"at":"2026-07-10T00:32:37.216Z","body":"A fix has been implemented and we are monitoring the region.","status":"monitoring"},{"at":"2026-07-10T01:11:09.868Z","body":"The issue has been resolved.","status":"resolved"}]},{"id":"0nz8147tgvkk","title":"Atlas is experiencing issues with issuing certificates from Lets Encrypt","impact":"minor","status":"resolved","startedAt":"2026-07-09T19:37:32.787Z","resolvedAt":"2026-07-10T14:56:07.570Z","updatedAt":"2026-07-10T14:56:07.586Z","components":["MongoDB Cloud"],"url":"https://stspg.io/gq098tnc7xd0","updates":[{"at":"2026-07-09T19:37:32.862Z","body":"We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Tenant cluster provisioning is currently impacted.","status":"investigating"},{"at":"2026-07-09T21:22:06.847Z","body":"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.","status":"monitoring"},{"at":"2026-07-10T14:56:07.570Z","body":"Let's Encrypt service has returned to normal.","status":"resolved"}]},{"id":"q5ybj217pv4m","title":"Atlas Data Federation and Online Archive cloud-provider IAM authentication error","impact":"minor","status":"resolved","startedAt":"2026-07-09T10:23:52.209Z","resolvedAt":"2026-07-09T11:06:48.574Z","updatedAt":"2026-07-09T11:06:48.593Z","components":["MongoDB Atlas Data Federation and Online Archive"],"url":"https://stspg.io/djy0g3bcxk3k","updates":[{"at":"2026-07-09T10:23:52.317Z","body":"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.","status":"investigating"},{"at":"2026-07-09T10:57:24.474Z","body":"We have identified that the issue is caused by a recent configuration change to IAM authentication and are working on a fix.","status":"identified"},{"at":"2026-07-09T11:01:46.064Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-07-09T11:06:48.574Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"mdmlfpkp7ngz","title":"Impaired Cluster Operations due to Lets Encrypt Service Degradation","impact":"minor","status":"resolved","startedAt":"2026-07-02T23:09:40.262Z","resolvedAt":"2026-07-02T23:36:13.495Z","updatedAt":"2026-07-02T23:36:13.511Z","components":["MongoDB Cloud","MongoDB Atlas for Government"],"url":"https://stspg.io/7kwsvslt71wz","updates":[{"at":"2026-07-02T23:09:40.340Z","body":"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.","status":"monitoring"},{"at":"2026-07-02T23:36:13.495Z","body":"Let's Encrypt services have returned back to normal. Cluster operations have now returned to normal.","status":"resolved"}]},{"id":"qtn48wjhps74","title":"Impaired Cluster Operations due to Lets Encrypt Outage","impact":"minor","status":"resolved","startedAt":"2026-07-02T19:34:21.000Z","resolvedAt":"2026-07-02T21:06:33.436Z","updatedAt":"2026-07-02T21:06:33.451Z","components":["MongoDB Cloud","MongoDB Atlas for Government"],"url":"https://stspg.io/82n3vh28q1r0","updates":[{"at":"2026-07-02T19:34:21.000Z","body":"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.","status":"monitoring"},{"at":"2026-07-02T21:06:33.436Z","body":"We've confirmed that Lets Encrypt has returned to normal operations. Cluster operations are now back to normal.","status":"resolved"}]},{"id":"m3x674snxdk6","title":"AWS cluster backup and restore operations are failing","impact":"none","status":"resolved","startedAt":"2026-07-02T10:45:57.305Z","resolvedAt":"2026-07-02T11:09:20.121Z","updatedAt":"2026-07-02T11:09:20.138Z","components":["MongoDB Cloud"],"url":"https://stspg.io/6blfthnrwn0p","updates":[{"at":"2026-07-02T10:45:57.385Z","body":"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.\n\nWe are also investigation potential impact to other operations on AWS clusters such as modifying instance size.","status":"investigating"},{"at":"2026-07-02T10:50:36.068Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-07-02T11:09:20.121Z","body":"This incident has been resolved. AWS clusters should no longer encounter errors during backup and restore.","status":"resolved"}]},{"id":"3n6m136ll01g","title":"MongoDB Atlas: Atlas UI loading issues","impact":"none","status":"resolved","startedAt":"2026-06-25T10:16:22.807Z","resolvedAt":"2026-06-25T10:16:22.856Z","updatedAt":"2026-06-25T10:16:22.866Z","components":["MongoDB Cloud"],"url":"https://stspg.io/hdldpwnz35sk","updates":[{"at":"2026-06-25T10:16:22.856Z","body":"From 2026-06-25 06:55 UTC to 2026-06-25 07:10 UTC, some users may have experienced intermittent Atlas UI loading failures. We identified elevated traffic to a number of endpoints that increased latency in the Atlas UI service. This caused internal health checks to fail and temporarily reduced healthy Atlas UI capacity.\n\nWe restored healthy Atlas UI capacity and applied additional rate limiting to the affected traffic paths. We are continuing follow-up work to further  reduce the risk of recurrence.","status":"resolved"}]},{"id":"dk96gn5kc65d","title":"Increased error rate creating and managing Search and Vector Search indexes","impact":"none","status":"resolved","startedAt":"2026-06-04T15:33:24.089Z","resolvedAt":"2026-06-04T17:39:59.830Z","updatedAt":"2026-06-04T17:39:59.847Z","components":["MongoDB Atlas Search"],"url":"https://stspg.io/k90l4z1tq518","updates":[{"at":"2026-06-04T15:33:24.136Z","body":"A fix has been implemented and we are monitoring the results","status":"monitoring"},{"at":"2026-06-04T17:39:59.830Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"gwq51m3r62jc","title":"Investigating connection issues to ADFA in GCP","impact":"major","status":"resolved","startedAt":"2026-06-02T23:00:05.963Z","resolvedAt":"2026-06-03T00:11:32.098Z","updatedAt":"2026-06-03T00:11:32.114Z","components":["MongoDB Atlas Data Federation and Online Archive"],"url":"https://stspg.io/w33p0jhw9mlr","updates":[{"at":"2026-06-02T23:00:06.089Z","body":"We are currently investigating issues connecting and querying to Atlas Data Federation and Online Archive instances in GCP regions","status":"investigating"},{"at":"2026-06-02T23:42:56.000Z","body":"We've identified an issue with networking in GCP regions and are working on fix","status":"identified"},{"at":"2026-06-03T00:01:14.125Z","body":"Issues connecting to ADF and OA instances in GCP belgium-eu region has been mitigated, and working on other GCP regions.","status":"identified"},{"at":"2026-06-03T00:05:36.392Z","body":"All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.","status":"monitoring"},{"at":"2026-06-03T00:11:32.098Z","body":"Issue has been mitigated and connections should be working now to ADF and OA instances in GCP regions.","status":"resolved"}]},{"id":"ydcfcmqzgvf7","title":"Metrics may fail to send to DataDog Gov integrations","impact":"minor","status":"resolved","startedAt":"2026-05-28T22:02:24.847Z","resolvedAt":"2026-05-28T23:15:14.865Z","updatedAt":"2026-05-28T23:15:14.881Z","components":["MongoDB Atlas for Government"],"url":"https://stspg.io/d723sr8ykdyn","updates":[{"at":"2026-05-28T22:02:24.919Z","body":"Starting approximately 17:00 UTC, some Atlas for Government users may be experiencing gaps in metrics sent to their DataDog Gov integration.\n\nWe are investigating this issue.","status":"investigating"},{"at":"2026-05-28T23:15:14.865Z","body":"The issue has been resolved.","status":"resolved"}]},{"id":"t2tkv1n35tx0","title":"Authentication failures when running search queries for some clusters","impact":"minor","status":"resolved","startedAt":"2026-05-23T19:48:03.023Z","resolvedAt":"2026-05-24T02:05:41.608Z","updatedAt":"2026-05-24T02:05:41.624Z","components":["MongoDB Cloud","MongoDB Atlas Search"],"url":"https://stspg.io/9xrc36hrrnmx","updates":[{"at":"2026-05-23T19:48:03.097Z","body":"We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.","status":"investigating"},{"at":"2026-05-23T20:14:02.793Z","body":"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.","status":"identified"},{"at":"2026-05-24T00:14:08.882Z","body":"We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.","status":"monitoring"},{"at":"2026-05-24T02:05:41.608Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"6g80s88xb3fy","title":"[Atlas for Government] Data plane node logs unavailable for last 6 days","impact":"minor","status":"resolved","startedAt":"2026-05-22T20:32:17.000Z","resolvedAt":"2026-05-22T22:17:46.893Z","updatedAt":"2026-05-22T22:17:46.910Z","components":["MongoDB Atlas for Government"],"url":"https://stspg.io/8gv5grsv7r5m","updates":[{"at":"2026-05-22T20:32:17.000Z","body":"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.","status":"investigating"},{"at":"2026-05-22T21:17:42.428Z","body":"We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.","status":"monitoring"},{"at":"2026-05-22T22:17:46.893Z","body":"The data plane node log download has recovered.","status":"resolved"}]},{"id":"mk8wzkvb5ypb","title":"Impaired Cluster Operations due to Lets Encrypt Outage","impact":"minor","status":"resolved","startedAt":"2026-05-08T19:33:45.488Z","resolvedAt":"2026-05-08T22:07:06.889Z","updatedAt":"2026-05-08T22:07:06.905Z","components":["MongoDB Cloud","MongoDB Atlas for Government"],"url":"https://stspg.io/0g307sn27q00","updates":[{"at":"2026-05-08T19:33:45.605Z","body":"Cluster operations are currently impaired due to issues with Lets Encrypt. We are actively monitoring the situation as more updates come in.","status":"monitoring"},{"at":"2026-05-08T21:39:19.783Z","body":"Lets Encrypt is now reporting as healthy. We will continue monitoring as cluster operations return to a healthy state.","status":"monitoring"},{"at":"2026-05-08T22:07:06.889Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"bxbs9mwt4wpc","title":"AWS Availability Zone use1-az4 in US-EAST-1 Region is Impaired","impact":"minor","status":"resolved","startedAt":"2026-05-08T02:24:06.481Z","resolvedAt":"2026-05-09T14:24:23.381Z","updatedAt":"2026-05-09T14:24:23.396Z","components":["MongoDB Cloud"],"url":"https://stspg.io/49mpdjlq4rhp","updates":[{"at":"2026-05-08T02:24:06.525Z","body":"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.\n\nPlease see https://health.aws.amazon.com/health/status for more information.","status":"identified"},{"at":"2026-05-08T03:12:20.673Z","body":"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.   \n\nWe continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.","status":"monitoring"},{"at":"2026-05-08T12:34:20.600Z","body":"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.   \n\nWe continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.","status":"monitoring"},{"at":"2026-05-08T20:41:42.995Z","body":"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.\n\nWe continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.","status":"monitoring"},{"at":"2026-05-09T14:24:23.381Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"1t1nk96wgyx3","title":"AWS Cluster DNS Changes Degraded Performance","impact":"major","status":"resolved","startedAt":"2026-05-07T15:17:23.883Z","resolvedAt":"2026-05-07T22:15:21.896Z","updatedAt":"2026-05-07T22:15:21.916Z","components":["MongoDB Atlas for Government"],"url":"https://stspg.io/ryk5cwxqt8h4","updates":[{"at":"2026-05-07T15:17:23.979Z","body":"DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.","status":"identified"},{"at":"2026-05-07T15:20:14.947Z","body":"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.","status":"identified"},{"at":"2026-05-07T16:58:42.221Z","body":"Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.","status":"identified"},{"at":"2026-05-07T17:50:06.819Z","body":"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.","status":"investigating"},{"at":"2026-05-07T19:47:25.149Z","body":"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.","status":"monitoring"},{"at":"2026-05-07T19:47:33.055Z","body":"We are continuing to monitor for any further issues.","status":"monitoring"},{"at":"2026-05-07T22:15:21.896Z","body":"DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.","status":"resolved"}]},{"id":"z0jcgk6n56s7","title":"Atlas Backup Export Jobs Degraded Performance","impact":"minor","status":"resolved","startedAt":"2026-05-06T21:48:39.650Z","resolvedAt":"2026-05-07T20:55:58.889Z","updatedAt":"2026-05-07T20:55:58.903Z","components":["MongoDB Cloud","MongoDB Atlas for Government"],"url":"https://stspg.io/k8frc31v1800","updates":[{"at":"2026-05-06T21:48:39.708Z","body":"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","status":"identified"},{"at":"2026-05-07T01:20:16.004Z","body":"We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.","status":"identified"},{"at":"2026-05-07T20:02:28.411Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-05-07T20:55:58.889Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"0ng8p9f6lfgx","title":"Partial outage in Azure West Europe","impact":"none","status":"resolved","startedAt":"2026-05-03T17:33:56.258Z","resolvedAt":"2026-05-05T17:28:00.023Z","updatedAt":"2026-05-05T17:28:00.040Z","components":["MongoDB Cloud"],"url":"https://stspg.io/vb4bprknl7vn","updates":[{"at":"2026-05-03T17:33:56.327Z","body":"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.","status":"investigating"},{"at":"2026-05-03T20:19:20.293Z","body":"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.","status":"monitoring"},{"at":"2026-05-05T17:28:00.023Z","body":"We are no longer observing these issues in Azure West Europe. Atlas Clusters in the region should be healthy and fully operational.","status":"resolved"}]},{"id":"32wsqrsbhvh6","title":"Increase in Billing for Backup Usage","impact":"major","status":"resolved","startedAt":"2026-04-27T17:16:46.000Z","resolvedAt":"2026-04-27T20:50:07.135Z","updatedAt":"2026-04-27T20:50:07.150Z","components":["MongoDB Cloud"],"url":"https://stspg.io/ryk00jrqkw7w","updates":[{"at":"2026-04-27T17:16:46.000Z","body":"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.\n\nWe are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end.\n\nPlease contact MongoDB Support with any questions. We will post another update by April 27 at 22:00 UTC.","status":"identified"},{"at":"2026-04-27T20:50:07.135Z","body":"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.","status":"resolved"}]},{"id":"hlhym701zs9m","title":"MongoDB Atlas BI Connector: Connections and queries fail","impact":"major","status":"resolved","startedAt":"2026-04-17T17:03:13.076Z","resolvedAt":"2026-04-21T13:45:37.550Z","updatedAt":"2026-04-21T13:45:37.563Z","components":["MongoDB Atlas for Government"],"url":"https://stspg.io/gg0lkx6qf43g","updates":[{"at":"2026-04-17T17:03:13.141Z","body":"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.\n\nUnderlying cluster health is not affected.","status":"investigating"},{"at":"2026-04-17T20:24:40.000Z","body":"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.\n\nCluster health is unaffected.","status":"identified"},{"at":"2026-04-20T19:17:42.542Z","body":"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.","status":"monitoring"},{"at":"2026-04-21T13:45:37.550Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"d74nshb79dgz","title":"Atlas Charts users unable to login","impact":"none","status":"resolved","startedAt":"2026-04-01T12:55:24.600Z","resolvedAt":"2026-04-01T12:55:24.656Z","updatedAt":"2026-04-01T12:55:24.669Z","components":["MongoDB Charts"],"url":"https://stspg.io/w3mhl4vn1q1t","updates":[{"at":"2026-04-01T12:55:24.656Z","body":"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.","status":"resolved"}]},{"id":"b66vgs5vz8rz","title":"Delays in cluster creation and adding new cluster nodes in Azure East US 2 region","impact":"none","status":"resolved","startedAt":"2026-03-30T21:47:40.509Z","resolvedAt":"2026-03-30T23:10:14.473Z","updatedAt":"2026-03-30T23:10:14.493Z","components":["MongoDB Cloud"],"url":"https://stspg.io/3vjd3s0kkmlm","updates":[{"at":"2026-03-30T21:47:40.555Z","body":"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.\n\nWhat you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region.\n\nUser action: As a workaround, users can provision clusters in other Azure regions.","status":"identified"},{"at":"2026-03-30T23:10:14.473Z","body":"We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.","status":"resolved"}]},{"id":"gch8hbs1yfz5","title":"Intermittent 503 Errors on Atlas Admin API and Automation Tooling","impact":"major","status":"resolved","startedAt":"2026-03-25T21:31:18.107Z","resolvedAt":"2026-03-27T13:21:19.612Z","updatedAt":"2026-03-27T13:21:19.628Z","components":["MongoDB Cloud"],"url":"https://stspg.io/jzjbn35bsc7r","updates":[{"at":"2026-03-25T21:31:18.201Z","body":"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.\n\nOur 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.","status":"investigating"},{"at":"2026-03-25T23:39:37.520Z","body":"The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.","status":"monitoring"},{"at":"2026-03-26T19:12:11.836Z","body":"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.","status":"monitoring"},{"at":"2026-03-27T13:21:19.612Z","body":"We are no longer seeing intermittent spikes in HTTP 503 errors.","status":"resolved"}]},{"id":"cy5vvcwnrgxq","title":"Issue querying Azure blob storage containers in Atlas Data Federation","impact":"major","status":"resolved","startedAt":"2026-03-19T18:11:03.696Z","resolvedAt":"2026-03-19T19:19:57.264Z","updatedAt":"2026-03-19T19:19:57.283Z","components":["MongoDB Atlas Data Federation and Online Archive"],"url":"https://stspg.io/5y67l14lfs1x","updates":[{"at":"2026-03-19T18:11:03.773Z","body":"We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.","status":"investigating"},{"at":"2026-03-19T18:25:28.889Z","body":"The issue has been identified and we are working on a fix.","status":"identified"},{"at":"2026-03-19T19:01:17.916Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-03-19T19:14:04.962Z","body":"We are continuing to monitor for any further issues.","status":"monitoring"},{"at":"2026-03-19T19:19:57.264Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"pwv9vb90vkdc","title":"MongoDB Atlas: Clusters page failing to load","impact":"major","status":"resolved","startedAt":"2026-03-19T14:42:39.215Z","resolvedAt":"2026-03-19T15:28:05.181Z","updatedAt":"2026-03-19T15:28:05.198Z","components":["MongoDB Cloud"],"url":"https://stspg.io/7ql9037sq1yq","updates":[{"at":"2026-03-19T14:42:39.270Z","body":"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.\n\nCluster health is unaffected.","status":"identified"},{"at":"2026-03-19T15:17:03.880Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-03-19T15:28:05.181Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"ts5bjz6km9f9","title":"MongoDB Atlas for Government: SSO login failures for some users","impact":"minor","status":"resolved","startedAt":"2026-03-19T00:24:26.237Z","resolvedAt":"2026-03-31T21:19:47.430Z","updatedAt":"2026-03-31T21:19:47.445Z","components":["MongoDB Atlas for Government"],"url":"https://stspg.io/nhvz9t2hs7s2","updates":[{"at":"2026-03-19T00:24:26.321Z","body":"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.\n\nRoot 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.\n\nWhat you might see:\n- A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL.\n- An inability to complete login when using a federated identity provider link.\n\nOur actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users.\n\nUser 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.\n\nNext 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.","status":"identified"},{"at":"2026-03-19T22:15:18.000Z","body":"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.","status":"monitoring"},{"at":"2026-03-31T21:19:47.430Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"ggrxstpcnljv","title":"Issue affecting stream processing within the AWS US-EAST-1 region","impact":"none","status":"resolved","startedAt":"2026-03-11T20:10:35.157Z","resolvedAt":"2026-03-11T20:10:35.214Z","updatedAt":"2026-03-11T20:10:35.226Z","components":["MongoDB Atlas Stream Processing"],"url":"https://stspg.io/g1nmlyx08f8r","updates":[{"at":"2026-03-11T20:10:35.214Z","body":"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.","status":"resolved"}]},{"id":"rtbthsrxzt6x","title":"MongoDB Atlas Admin API: Temporary failures for tools using older API versions","impact":"none","status":"resolved","startedAt":"2026-03-11T10:00:32.764Z","resolvedAt":"2026-03-02T12:00:00.000Z","updatedAt":"2026-03-11T10:00:32.821Z","components":[],"url":"https://stspg.io/77sj4vmk5dlq","updates":[{"at":"2026-03-02T12:00:00.000Z","body":"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.\n\nThis 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.\n\nWe 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.\n\nFrom 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.\n\nNo user action is required. Previously failed operations can be retried and should now succeed.","status":"resolved"}]},{"id":"3dts1g4b0n7g","title":"Atlas Clusters Snapshot Failures","impact":"major","status":"resolved","startedAt":"2026-03-10T23:18:53.831Z","resolvedAt":"2026-03-11T02:30:15.059Z","updatedAt":"2026-03-11T02:30:15.078Z","components":["MongoDB Cloud"],"url":"https://stspg.io/tyn1fstlpnvb","updates":[{"at":"2026-03-10T23:18:53.916Z","body":"Atlas cluster snapshots are failing. We are actively investigating.","status":"investigating"},{"at":"2026-03-11T00:45:27.789Z","body":"The issue has been identified and a fix is being implemented.","status":"identified"},{"at":"2026-03-11T02:21:04.523Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-03-11T02:30:15.059Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"sx5zh206myxg","title":"MongoDB Atlas: Email notifications may be failing","impact":"major","status":"resolved","startedAt":"2026-03-02T15:50:09.323Z","resolvedAt":"2026-03-02T16:28:53.503Z","updatedAt":"2026-03-02T16:28:53.518Z","components":["MongoDB Cloud"],"url":"https://stspg.io/3fx0hpw59xhw","updates":[{"at":"2026-03-02T15:50:09.373Z","body":"We are currently investigating this issue.\nSome 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.","status":"investigating"},{"at":"2026-03-02T16:28:53.503Z","body":"This incident has been resolved. Email notifications are being sent successfully.","status":"resolved"}]},{"id":"7g5qmxgkc2y4","title":"Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates)  and AWS me-south-1 (Bahrain)","impact":"major","status":"resolved","startedAt":"2026-03-01T19:30:04.000Z","resolvedAt":"2026-09-03T16:47:10.442Z","updatedAt":"2026-09-03T16:47:10.457Z","components":["MongoDB Cloud"],"url":"https://stspg.io/mg7m971rdhw8","updates":[{"at":"2026-03-01T13:48:14.435Z","body":"Impact: Some Atlas customers with deployments in the AWS me-central-1 (United Arab Emirates) region may experience delays in cluster operations (for example, creating, scaling, or modifying clusters and infrastructure-level maintenance tasks).\n\nRoot cause: AWS is reporting connectivity and power issues affecting APIs and instances in a single Availability Zone in the me-central-1 Region, which can cause increased errors and latency for some AWS services and workflows. For the latest details from AWS, see the AWS Health Dashboard.\n\nWhat you might see:\n- Cluster create/scale/modify operations remaining in a pending or in-progress state longer than usual\n- Slower completion of some maintenance and infrastructure operations in the affected region\n\nOur actions:\n- Monitoring the AWS incident and Atlas fleet behavior in me-central-1\n\nCustomer action: No action is required at this time. We expect delayed operations to complete as AWS resolves the underlying issue. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.\n\nNext update: We will provide updates on this page as AWS progresses mitigation or if we observe any change in impact to Atlas customers.","status":"identified"},{"at":"2026-03-01T14:55:50.760Z","body":"Update: One or more instances backing MongoDB Atlas clusters in the AWS ME-CENTRAL-1 (United Arab Emirates) region may have been temporarily unavailable due to an underlying AWS issue in a single Availability Zone . According to AWS, a localized power issue in this Availability Zone has affected connectivity and power for some APIs and instances, and may have caused increased errors, latency, or unavailability for certain workloads. For the latest information from AWS, see the AWS Health Dashboard.\n\nWe continue to closely monitor Atlas deployments in ME-CENTRAL-1 and will provide additional updates if we observe any further impact to Atlas customers.","status":"identified"},{"at":"2026-03-01T19:30:04.000Z","body":"Update: We are continuing to monitor an ongoing issue in AWS me-central-1 (United Arab Emirates) caused by an underlying AWS infrastructure disruption isolated to a single Availability Zone. Please visit the AWS Health Dashboard for detailed information on the Availability Zone outage (https://health.aws.amazon.com/health/status).\n\nIf you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.","status":"identified"},{"at":"2026-03-02T02:17:23.000Z","body":"Update: We are continuing to monitor an ongoing issue in AWS me-central-1 (United Arab Emirates) caused by an underlying AWS infrastructure disruption isolated to a single Availability Zone. Please visit the AWS Health Dashboard for detailed information on the Availability Zone outage (https://health.aws.amazon.com/health/status).\n\nIf you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.","status":"identified"},{"at":"2026-03-02T16:17:30.000Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience outages. The latest information from AWS is available at:  https://health.aws.amazon.com/health/status.\n\nCURRENT IMPACT\nAtlas clusters deployed only in me-central-1 may be fully unavailable.\n\nFor clusters operating solely in me-central-1, backup operations in this region are impaired.\n\nClusters and backups should remain operational in me-south-1 at this time. Clusters in me-south-1 may be running at reduced capacity due to zonal constraints.\n\nAWS has indicated an extended resolution timeline for service in the impacted Regions and Availability Zones.\n\nRECOMMENDED CUSTOMER ACTIONS\nIf you have a multi-region configuration that includes a healthy secondary region, we recommend routing application traffic to that secondary region.\n\nIf you have clusters in me-south-1 taking backups, we recommend enabling \"Additional Snapshot Copies Policy\" to a different region.\n\nIf you have time-sensitive production changes or operations that are blocked and need urgent assistance, please contact MongoDB Support via the Support Portal, Support Chat or in-product support.\n\nWHAT WE ARE DOING\nWe recognize the severity of this situation and the impact it may have on your workloads. The situation continues to evolve, and we are closely monitoring AWS status and regional health signals. We are validating Atlas behavior across affected and unaffected regions, and working to mitigate customer impact where possible.\n\nWe will provide further updates as circumstances continue to change.","status":"identified"},{"at":"2026-03-02T19:58:09.516Z","body":"CURRENT IMPACT\n\nAccording to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nAWS is currently experiencing infrastructure impairments in two Middle East regions:\n* ME-CENTRAL-1 (Middle East – Central): Two Availability Zones are impaired due to an underlying power and facilities issue. This is resulting in elevated error rates and latency across several AWS services. Recovery is currently expected to take at least a day, per AWS.\n* ME-SOUTH-1 (Middle East – Bahrain): A single Availability Zone is experiencing a localized power issue. While some services have shifted traffic to unaffected Availability Zones, resources deployed in the impacted zone may continue to experience availability issues, elevated error rates, or extended recovery timelines. Recovery is also currently expected to take at least a day.\n\nBecause MongoDB Atlas runs on AWS infrastructure, Atlas clusters deployed in the affected Availability Zones may be unavailable or experience operational impact, and certain Atlas management operations (including the Atlas UI, API, and CLI) may show increased error rates during this time.\n\nThe impact of these events depends on your Atlas cluster topology and configuration:\n* Customers using multi–region deployments, global clusters, or replicas located in unaffected Availability Zones or regions may see little to no impact.\n* Customers with clusters or workloads primarily located in the affected Availability Zones may experience reduced availability or degraded performance.\n* Clusters deployed entirely in unaffected Availability Zones or outside the impacted regions are operating normally.\n\nAVAILABLE OPTIONS\n\nDepending on your application requirements and cluster configuration, you may consider the following options:\n1. Move the cluster to another region that is not impacted.\n2. Add electable nodes in another region, which can enable the cluster to establish a minimum viable topology and restore database operations.\n3. Take no action and wait for the affected Availability Zones to be fully recovered.\n\nHOW TO GET HELP\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-03T17:20:01.257Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe 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 the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will provide another update by March 4 at 00:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-03T22:54:43.429Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe 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 the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will provide another update by March 4 at 06:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-04T06:03:24.942Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe 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 the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will provide another update by March 4 at 12:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-04T16:33:33.626Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe 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 the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will provide another update by March 5 at 12:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-05T14:59:38.863Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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 the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will provide another update by March 6 at 14:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-06T14:24:42.926Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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 the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will provide another update by March 7 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-07T15:28:03.319Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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.\n\nWe will provide another update by March 8 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-08T15:42:17.255Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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.\n\nWe will provide another update by March 9 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-09T16:02:22.220Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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.\n\nWe will provide another update by March 10 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-10T15:59:14.881Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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.\n\nWe will provide another update by March 11 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-11T15:48:19.200Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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.\n\nWe expect our guidance to remain unchanged for the immediate future. We will move to a weekly status post update cadence, and provide another update by March 18 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"identified"},{"at":"2026-03-18T15:51:58.341Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments.\n\nWe 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.\n\nWe expect our guidance to remain unchanged for the immediate future. We will continue with a weekly status post update cadence, and provide another update by March 25 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-03-25T15:33:12.964Z","body":"According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe 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.\n\nWe expect our guidance to remain unchanged for the immediate future. We will continue with a weekly status post update cadence, and provide another update by April 1 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-03-26T21:35:42.107Z","body":"Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, clusters in me-south-1 cannot be modified and may be unable to process normal operations.\n\nWe strongly recommend that customers with workloads in the affected regions act now to move their clusters to alternate regions instead of waiting for full availability to be restored.\n\nWe continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should 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 continue to extend their backup snapshot expirations in me-central-1 and me-south-1 as needed.\n\nWe will continue with a weekly status post update cadence, and provide another update by April 1 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-04-01T16:02:48.728Z","body":"Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore.\n\nWe strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region.\n\nWe continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should 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 continue to extend their backup snapshot expirations in me-central-1 as needed.\n\nWe will continue with a weekly status post update cadence, and provide another update by April 8 at 16:00 UTC, or sooner if new information becomes available.\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-04-08T15:33:52.590Z","body":"Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore.\n\nWe strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region.\n\nWe continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should 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 continue to extend their backup snapshot expirations in me-central-1 as needed.\n\nWe will continue with a monthly status post update cadence, and provide another update by May 6 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-05-06T16:02:29.647Z","body":"AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the AWS Service Health Dashboard update from April 30th, recovery is expected to take several months. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region.\n\nWe continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should 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 continue to extend their backup snapshot expirations in me-central-1 as needed.\n\nWe will continue with a monthly status post update cadence, and provide another update by June 3 at 16:00 UTC, or sooner if new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-06-03T15:46:56.705Z","body":"AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the AWS Service Health Dashboard update from April 30th, recovery is expected to take several months. The latest information from AWS is available at: https://health.aws.amazon.com/health/status.\n\nWe strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region.\n\nWe continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should 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 continue to extend their backup snapshot expirations in me-central-1 as needed.\n\nWe will move to an as-needed status post update cadence as new information becomes available.\n\nIf you would like assistance assessing how these events may affect your Atlas deployment, our support team is available:\n* Open a support case through the MongoDB Support Portal\n* Start a chat with Support using the Intercom widget within the MongoDB Atlas interface","status":"monitoring"},{"at":"2026-09-03T16:47:10.442Z","body":"While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status\nWe will update this post as necessary. Thanks in advance for your understanding.","status":"resolved"}]},{"id":"yw96wbq7mtz1","title":"MongoDB App Services: Connectivity issues","impact":"major","status":"resolved","startedAt":"2026-02-28T19:53:36.761Z","resolvedAt":"2026-03-02T03:05:05.384Z","updatedAt":"2026-03-02T03:05:05.399Z","components":["MongoDB Atlas App Services and Device Sync"],"url":"https://stspg.io/dxd0y34wps83","updates":[{"at":"2026-02-28T19:53:36.876Z","body":"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.","status":"investigating"},{"at":"2026-03-01T05:37:28.616Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-03-02T03:05:05.384Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"l705pf8q03t2","title":"DataDog Integration Degraded Experience","impact":"minor","status":"resolved","startedAt":"2026-02-26T19:21:05.481Z","resolvedAt":"2026-02-26T20:04:33.862Z","updatedAt":"2026-02-26T20:04:33.877Z","components":["MongoDB Cloud"],"url":"https://stspg.io/wcxvlsl4tty4","updates":[{"at":"2026-02-26T19:21:05.560Z","body":"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.\n\nWe are investigating this issue.","status":"investigating"},{"at":"2026-02-26T19:51:51.691Z","body":"A fix has been implemented and we're monitoring the results.","status":"monitoring"},{"at":"2026-02-26T20:04:33.862Z","body":"The issue has been resolved","status":"resolved"}]},{"id":"gycfh8b52sgf","title":"MongoDB Atlas Data Federation and Online Archive: Schema Table fails to load","impact":"minor","status":"resolved","startedAt":"2026-02-19T18:50:56.110Z","resolvedAt":"2026-02-20T16:59:34.759Z","updatedAt":"2026-02-20T16:59:34.774Z","components":["MongoDB Atlas Data Federation and Online Archive"],"url":"https://stspg.io/vst7b612n6vx","updates":[{"at":"2026-02-19T18:50:56.186Z","body":"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/\nIf 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","status":"investigating"},{"at":"2026-02-19T21:35:58.388Z","body":"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/\nIf 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\n\nIt appears to affect only a very small number of users, but we will keep this alert open until the issue is resolved.","status":"investigating"},{"at":"2026-02-20T16:54:36.256Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-02-20T16:59:34.759Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"mlzl2k4dcqlt","title":"DNS Resolution failures for public IP addresses within 31.89.0.0/24","impact":"minor","status":"resolved","startedAt":"2026-02-13T16:11:17.105Z","resolvedAt":"2026-02-13T17:57:19.454Z","updatedAt":"2026-02-13T17:57:19.477Z","components":["MongoDB Cloud"],"url":"https://stspg.io/yqb408m81621","updates":[{"at":"2026-02-13T16:11:17.203Z","body":"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.","status":"investigating"},{"at":"2026-02-13T16:42:50.963Z","body":"We have identified the root cause and are working on backfilling those records with AWS support. \n\nWe have also disabled that ip range for new clusters so moving forward this issue will not be hit for new AWS clusters.","status":"identified"},{"at":"2026-02-13T17:57:19.454Z","body":"The DNS records have been backfilled and clusters that had these IP addresses should be recovered.","status":"resolved"}]},{"id":"k85tnjpxlpyg","title":"MongoDB Atlas: Atlas UI loading slowly","impact":"minor","status":"resolved","startedAt":"2026-02-13T07:20:57.721Z","resolvedAt":"2026-02-13T07:55:09.495Z","updatedAt":"2026-02-13T07:55:09.513Z","components":["MongoDB Cloud"],"url":"https://stspg.io/zdbjdfv2gyxq","updates":[{"at":"2026-02-13T07:20:57.851Z","body":"We are currently investigating reports of the slow loading of the Atlas web UI.","status":"investigating"},{"at":"2026-02-13T07:55:09.495Z","body":"We have identified and resolved the issue. Atlas UI will load without a delay now.","status":"resolved"}]},{"id":"tlf395rtc6q1","title":"Elevated errors for cluster creation on AWS","impact":"critical","status":"resolved","startedAt":"2026-02-12T22:10:54.000Z","resolvedAt":"2026-02-12T23:10:31.694Z","updatedAt":"2026-02-12T23:10:31.709Z","components":["MongoDB Cloud"],"url":"https://stspg.io/l0bdqs5grtgj","updates":[{"at":"2026-02-12T22:10:54.000Z","body":"We are currently investigating elevated errors for customers attempting to create a cluster on AWS","status":"investigating"},{"at":"2026-02-12T23:00:54.469Z","body":"We have identified the root cause and are implementing a fix to remediate the situation","status":"identified"},{"at":"2026-02-12T23:08:38.278Z","body":"We have implemented the fix.  Customers will now be able to create new clusters on AWS.","status":"monitoring"},{"at":"2026-02-12T23:10:31.694Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"76f1m0q04m6m","title":"Partial outage in Azure West US","impact":"major","status":"resolved","startedAt":"2026-02-07T09:07:32.196Z","resolvedAt":"2026-02-07T11:43:28.696Z","updatedAt":"2026-02-07T11:43:28.711Z","components":["MongoDB Cloud"],"url":"https://stspg.io/y4ws1khmx3bn","updates":[{"at":"2026-02-07T09:07:32.322Z","body":"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.","status":"investigating"},{"at":"2026-02-07T09:15:39.602Z","body":"Azure has posted the following to their public Status Page: https://azure.status.microsoft/en-us/status\n\nOngoing Service Degradation in West US\n\nWe 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.\n\nThis message was last updated at 09:10 UTC on 07 February 2026","status":"identified"},{"at":"2026-02-07T10:11:24.390Z","body":"We are seeing some nodes in the impacted Azure West US region recovering. We will continue to monitor and provide updates.","status":"monitoring"},{"at":"2026-02-07T11:43:28.696Z","body":"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.\n\nWe 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.","status":"resolved"}]}]}