# MongoDB Atlas change history Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=&page=N`. Company profile: [MongoDB Atlas](https://rewindex.com/company/mongodb-atlas.md) ## Changes by kind | Kind | Changes | Notable | Latest (UTC) | | --- | --- | --- | --- | | Major incident | 19 | 19 | 2026-10-09 16:29 UTC | ## Timeline | When (UTC) | Kind | Change | Label | Summary | | --- | --- | --- | --- | --- | | 2026-10-09 16:29 UTC | Major incident | [Major incident: Issue impacting Atlas Search availability on certain clusters](https://rewindex.com/change/ia71e1200ef62f7.md) | outage | MongoDB Atlas reported a major Atlas Search incident causing mongot crashes and potential search and vector search outages for a subset of users. It started at 2026-10-09 16:29 UTC and was resolved at 2026-10-09 18:17 UTC, lasting 1 h 47 min. A fix was deployed at 10-09 17:09 UTC. | | 2026-10-01 15:41 UTC | Major incident | [Major incident: Trigger processing may be delayed globally](https://rewindex.com/change/ia406dfe43f52d2.md) | degradation | MongoDB Atlas reported a major global incident affecting Triggers: unordered processing was delayed, and some triggers were not firing or visible in the Atlas UI. The incident started at 2026-10-01 15:41 UTC and was resolved at 2026-10-01 20:54 UTC, lasting 5 h 12 min; trigger processing was operational by 19:59 UTC. | | 2026-09-16 09:06 UTC | Major incident | [Major incident: Support Portal Outage](https://rewindex.com/change/i21cd8329675dca.md) | outage | MongoDB Atlas reported a major Support Portal outage that degraded or limited customers’ access to technical support. The incident started at 2026-09-16 09:06 UTC and was resolved at 2026-09-16 15:31 UTC, lasting 6 h 24 min; MongoDB stated that the platform issues were resolved. | | 2026-09-03 16:44 UTC | Major incident | [Major incident: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1](https://rewindex.com/change/i8a602f8b595625.md) | degradation | MongoDB Atlas reported major impairment of cluster operations in AWS me-central-1 and AWS me-south-1, affecting MongoDB Cloud, starting 2026-09-03 16:44 UTC. The incident remained open under monitoring when archived; the recorded open duration was 2 minutes, with no cause or fix stated. | | 2026-08-05 05:17 UTC | Major incident | [Major incident: GCP capacity constraints affecting Atlas deployments](https://rewindex.com/change/i3093e720d98621.md) | outage | MongoDB Atlas reported a major incident affecting some customers’ deployments due to GCP capacity constraints across North America, Europe, and Asia Pacific/Australia, including M50 and S70L instance types. It started at 2026-08-05 05:17 UTC and was resolved at 2026-08-05 12:14 UTC, lasting 6 h 56 min; MongoDB said symptoms had largely subsided and Atlas was fully operational. | | 2026-08-03 18:47 UTC | Major incident | [Major incident: Elevated errors on VoyageAI APIs](https://rewindex.com/change/i79133fe92775a1.md) | outage | VoyageAI APIs experienced elevated 5xx errors affecting VoyageAI Embedding and Reranking Models, with major impact, from 2026-08-03 18:47 UTC to 2026-08-03 21:18 UTC (2 h 31 min). A fix was applied at 19:02 UTC, and normal operation was confirmed at resolution. | | 2026-07-27 23:37 UTC | Major incident | [Major incident: VoyageAI elevated errors](https://rewindex.com/change/i103e2c6c443205.md) | outage | All VoyageAI models experienced elevated errors, affecting VoyageAI Embedding and Reranking Models; MongoDB Atlas rated the impact major. The incident started at 2026-07-27 23:37 UTC and was resolved at 2026-07-27 23:48 UTC, with a reported duration of 10 min. No cause or specific fix was stated. | | 2026-07-23 16:21 UTC | Major incident | [Major incident: Cluster connectivity issues in Azure westus](https://rewindex.com/change/i621c0184f99f8a.md) | outage | MongoDB Atlas reported a major outage affecting some Azure westus clusters: intermittent connection failures, inter-node communication issues, nodes appearing down, and delayed cluster modifications. It started 2026-07-23 16:21 UTC and resolved 2026-07-23 20:28 UTC (4 h 6 min); Azure confirmed networking issues, and recovery completed after Azure rolled out mitigation. | | 2026-06-02 23:00 UTC | Major incident | [Major incident: Investigating connection issues to ADFA in GCP](https://rewindex.com/change/i9d5b4619bcfedb.md) | outage | A major outage affected connections and queries to MongoDB Atlas Data Federation and Online Archive instances in GCP regions from 2026-06-02 23:00 UTC to 2026-06-03 00:11 UTC, lasting 1 h 11 min. MongoDB identified a networking issue in GCP regions and reported mitigation, with connections working at resolution. | | 2026-05-07 15:17 UTC | Major incident | [Major incident: AWS Cluster DNS Changes Degraded Performance](https://rewindex.com/change/id73179968fee27.md) | degradation | MongoDB Atlas for Government had a major AWS cluster DNS degradation from 2026-05-07 15:17 UTC to 2026-05-07 22:15 UTC, lasting 6 h 57 min; cluster topology changes could be delayed or fail. MongoDB patched bad metadata causing ACME-related DNS issues and confirmed DNS and cluster updates were healthy. | | 2026-04-27 17:16 UTC | Major incident | [Major incident: Increase in Billing for Backup Usage](https://rewindex.com/change/i1297291d8627a4.md) | other | MongoDB Atlas reported a major billing-only bug causing higher-than-expected backup charges on April 24, 2026 invoices; backups, cluster health and data were unaffected. The incident ran from 2026-04-27 17:16 UTC to 2026-04-27 20:50 UTC (3 h 33 min). MongoDB resolved the issue, promised automatic refunds, and said usage should display correctly by April 28th. | | 2026-04-17 17:03 UTC | Major incident | [Major incident: MongoDB Atlas BI Connector: Connections and queries fail](https://rewindex.com/change/iea360caa653ee7.md) | outage | MongoDB Atlas for Government BI Connector connections and queries failed in a major incident from 2026-04-17 17:03 UTC to 2026-04-21 13:45 UTC, lasting 3 days 20 h. No workaround was available, but cluster health was unaffected and data remained accessible to MongoDB clients. MongoDB implemented a fix and marked the incident resolved. | | 2026-03-25 21:31 UTC | Major incident | [Major incident: Intermittent 503 Errors on Atlas Admin API and Automation Tooling](https://rewindex.com/change/ia3287b3e5c5b18.md) | degradation | MongoDB Atlas reported a major degradation: intermittent HTTP 503 errors affected Atlas Admin API and automation tooling such as Terraform; requests typically succeeded on retry, while database connectivity remained healthy. It lasted 39 h 50 min, from 2026-03-25 21:31 UTC to 2026-03-27 13:21 UTC. MongoDB identified the root cause and applied a fix, without specifying details. | | 2026-03-19 18:11 UTC | Major incident | [Major incident: Issue querying Azure blob storage containers in Atlas Data Federation](https://rewindex.com/change/ibe489a9d25cfc3.md) | outage | MongoDB Atlas reported a major incident affecting Atlas Data Federation reads from customer Azure blob storage containers, starting 2026-03-19 18:11 UTC. A fix was implemented at 19:01 UTC, and the incident was resolved at 2026-03-19 19:19 UTC after 1 h 8 min. | | 2026-03-19 14:42 UTC | Major incident | [Major incident: MongoDB Atlas: Clusters page failing to load](https://rewindex.com/change/i2430029fe2fff4.md) | outage | MongoDB Atlas reported a major incident where affected users could see a blank Clusters page; cluster health was unaffected. It started at 2026-03-19 14:42 UTC and was resolved at 2026-03-19 15:28 UTC, lasting 45 min. A fix was implemented at 2026-03-19 15:17 UTC. | | 2026-03-10 23:18 UTC | Major incident | [Major incident: Atlas Clusters Snapshot Failures](https://rewindex.com/change/if2d43abdb2803a.md) | outage | MongoDB Atlas cluster snapshots were failing in a major-impact incident affecting MongoDB Cloud, from 2026-03-10 23:18 UTC to 2026-03-11 02:30 UTC (3 h 11 min). MongoDB implemented a fix and confirmed resolution; customers faced snapshot failures during the incident. | | 2026-03-02 15:50 UTC | Major incident | [Major incident: MongoDB Atlas: Email notifications may be failing](https://rewindex.com/change/id14330d6b771d7.md) | outage | MongoDB Atlas reported a major-impact MongoDB Cloud incident in which some users may not have received email notifications. It started at 2026-03-02 15:50 UTC and was resolved at 2026-03-02 16:28 UTC, lasting 38 min; MongoDB confirmed email notifications were being sent successfully. | | 2026-03-01 19:30 UTC | Major incident | [Major incident: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)](https://rewindex.com/change/if91f3d4aae3886.md) | outage | Major MongoDB Atlas disruption began 2026-03-01 19:30 UTC in AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain): impaired cluster operations, unavailable Bahrain workloads, and blocked migration, backup and restore. AWS power/connectivity issues and regional damage were reported; after 185 days 21 h, MongoDB marked it resolved on 2026-09-03 16:47 UTC while stating disruption remained ongoing. | | 2026-02-28 19:53 UTC | Major incident | [Major incident: MongoDB App Services: Connectivity issues](https://rewindex.com/change/i8e45746fd19b02.md) | outage | MongoDB Atlas reported a major incident affecting deprecated Atlas App Services Device Sync: affected users could see SSL validation errors. It started at 2026-02-28 19:53 UTC and lasted 31 h 11 min, resolving at 2026-03-02 03:05 UTC; a fix was implemented and monitored. | --- Canonical: https://rewindex.com/company/mongodb-atlas/changes · Markdown: https://rewindex.com/company/mongodb-atlas/changes.md · JSON: https://rewindex.com/api/v1/companies/mongodb-atlas/changes · Generated 2026-10-18T00:54:33.286Z