MongoDB Atlas change history

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.