Databases / Document database / MongoDB Atlas

MongoDB Atlas

SEV 3 · CAN'T SHIP · 49d 2h

Since Feb 2026 · 50 incidents · status.mongodb.com · checked just now

CompareStatus page
GradeDLast 90 days
CPRODCSHIP
Happening now
Sep 3, 2026ongoingSEV 3
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Cluster operations are impaired in AWS me-central-1 and me-south-1, per a linked original post; details of the impact are not given here.AI-graded · regional · MongoDB Cloud
Why this grade
  1. RULES · SEV 3
    Sev 3 because MongoDB Cloud had a partial outage
  2. CLAUDE · SEV 3 · REGIONAL · LOW CONFIDENCE
    Cluster operations are impaired in AWS me-central-1 and me-south-1, per a linked original post; details of the impact are not given here.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 16:44 UTC · monitoring
    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.
  2. 16:47 UTC · monitoring
    We are continuing to monitor for any further issues.
Source

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade D
IncidentsEverything posted on the status page except scheduled maintenance.
180 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
2h 35m
LongestLongest single incident, start to resolved.
185d 21h
Since lastTime since the last counted incident was resolved.
47h 12m

By area

CProduction
8INCIDENTS
2d 11hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 19, 2026 · 25h 21mIssues rotating certificates for projects containing only Atlas Free and Flex clusters
SEV 2Oct 20, 2026 · 12h 36mGCP Availability Zone europe-west2-b connectivity issues
SEV 2Aug 5, 2026 · 6h 57mGCP capacity constraints affecting Atlas deployments
Most hit
MongoDB Cloud3
VoyageAI Embedding and Reranking Models2
MongoDB Atlas Search1
MongoDB Atlas App Services and Device Sync1
Worse. 21 in the last 6 months, 5 in the 6 before.
CShipping
10INCIDENTS
90d 0hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 2Aug 5, 2026 · 6h 57mGCP capacity constraints affecting Atlas deployments
SEV 2Oct 9, 2026 · 2h 35mAdmin Admin API: Intermittent Increase in 5xx errors
SEV 3Sep 3, 2026 · ongoingImpaired Cluster operations in AWS me-central-1 and AWS me-south-1
Most hit
MongoDB Cloud7
MongoDB Charts1
MongoDB Atlas for Government1
Worse. 11 in the last 6 months, 8 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production database, per month10 GB of data, about 1 GB of RAM on all month, 10M queries a month, one region, no replicas, commercial use. Cheapest plan that runs it.
Atlas M10, AWS us-east-13 of 4 cheaper · Upstash: cheaper, better grade
$56.94/mo
M10 (2 GB RAM, 10 GB storage)$56.94

Flex tops out at 5 GB, so 10 GB needs a dedicated cluster. M10 is a three-node replica set. Backups are extra. www.mongodb.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 36 in the last 6 months, 14 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down9
Sev 3 · Can't shipCan't deploy, build or manage it8
Sev 4 · PapercutDocs, status page, slow dashboard1

When it breaks

Start times, last 12 months, UTC.

What breaks

MongoDB Cloud28 incidents
MongoDB Atlas for Government11 incidents
MongoDB Atlas Search3 incidents
MongoDB Atlas Stream Processing3 incidents
MongoDB Atlas Data Federation and Online Archive3 incidents
MongoDB Charts2 incidents

Communication

Updates eachStatus page updates per incident, on average.
3.6Last 12 months
Update gapMedian time between status page updates during an incident.
1h 34mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 28Sev 1–2

Incident history

Oct 20, 202612h 36mSEV 2
GCP Availability Zone europe-west2-b connectivity issuesAtlas cluster nodes in GCP availability zone europe-west2-b lost connectivity from about 06:00 UTC. Clusters spread across zones kept serving reads and writes from nodes in the other zones. Atlas worked with its partners and Google Cloud on the cause. Signs of recovery appeared around 11:40 UTC, and the incident was resolved at about 20:09 UTC.AI-graded · one location · MongoDB Cloud
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Cloud had degraded performance
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Cluster nodes in one GCP availability zone (europe-west2-b) had connectivity issues for about 13 hours; clusters kept serving from other zones.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 07:32 UTC · identified
    Since 0600 UTC we have observed cluster node connectivity issues isolated to a single availability zone, GCP europe-west2-b. Atlas clusters are distributed across multiple AZs and 3-node clusters can continue to serve reads and writes from nodes in the other 2 Availability Zones in this region. We are working with our partners to resolve the cause of the issue and restore service to the affected nodes.
  2. 08:38 UTC · identified
    The Google Cloud status page has been updated to report further information, follow this link for details https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj
  3. 11:43 UTC · monitoring
    We are seeing signs of Availability Zone connectivity improving and are continuing to monitor.
  4. 20:09 UTC · resolved
    This incident has been resolved.
Source
Oct 9, 20261h 48mSEV 2
Issue impacting Atlas Search availability on certain clustersA known issue caused mongot crashes, leading to search and vector search outages on a subset of Atlas clusters. A fix was deployed around 17:09 UTC and the incident was resolved about 18:17 UTC on October 9, 2026.AI-graded · some customers · MongoDB Atlas Search
Why this grade
  1. RULES · SEV 1
    Sev 1 because MongoDB Atlas Search had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Atlas Search and vector search queries failed for a subset of clusters after mongot crashes; resolved in about two hours.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 16:29 UTC · investigating
    Ongoing Atlas Search incident known to cause mongot crashes, potential search and vector search outage, impacting a subset of search and vector search users in the Atlas fleet. We have identified the issue and are working on a fix.
  2. 16:30 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 17:09 UTC · monitoring
    A fix has been deployed and we are monitoring.
  4. 18:17 UTC · resolved
    This incident has been resolved.
Source
Oct 9, 20262h 35mSEV 2
Admin Admin API: Intermittent Increase in 5xx errorsElevated HTTP 500 errors hit the MongoDB Atlas Admin API from about 13:11 to 15:46 UTC on October 9, causing intermittent failures for API calls. A mitigation was deployed around 14:43 UTC and the incident was resolved after monitoring. The text gives no further detail on root cause or how many customers were affected.AI-graded · MongoDB Cloud
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Cloud had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Atlas Admin API returned intermittent HTTP 500 errors for about two and a half hours; scope across customers was not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 13:11 UTC · investigating
    We are seeing elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. Users may experience intermittent failures when making API calls. We are investigating the root cause and will share another update as our investigation continues.
  2. 14:43 UTC · monitoring
    We have deployed a mitigation for the elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. We are seeing signs of recovery and are monitoring the service to confirm the issue does not recur before resolving this incident.
  3. 15:46 UTC · resolved
    This incident has been resolved.
Source
Oct 2, 20265h 00mSEV 3
MongoDB Charts: Infinite login loop when creating new Charts projectsUsers creating new Charts projects were stuck in a login loop for about five hours; existing Charts projects were unaffected.AI-graded · some customers · MongoDB Charts
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Charts had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Users creating new Charts projects were stuck in a login loop for about five hours; existing Charts projects were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 00:01 UTC · identified
    Since approximately 23:30 UTC on 2026-10-01, users creating new Charts projects by clicking on the "Visualization" tab will repeatedly be prompted to login and will not be able to view the Charts interface. While these Charts projects will be created, we cannot guarantee the timing at this moment. Existing Charts projects are not affected.
  2. 05:02 UTC · resolved
    This incident has been resolved.
Source
Oct 1, 20265h 13mSEV 2
Trigger processing may be delayed globallyAtlas Triggers processing was delayed from about 15:00 UTC, and some triggers stopped firing or disappeared from the Atlas UI. Trigger processing was restored at 19:59 UTC and the incident was resolved at 20:54 UTC. Delayed events were being verified, and no cause was given.AI-graded · MongoDB Atlas App Services and Device Sync
Why this grade
  1. RULES · SEV 1
    Sev 1 because MongoDB Atlas App Services and Device Sync had a partial outage
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Atlas Triggers were delayed or not firing globally for about five hours; the Atlas UI also failed to show some triggers.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 15:41 UTC · investigating
    As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.
  2. 18:21 UTC · investigating
    We are continuing to investigate this issue.
  3. 19:51 UTC · investigating
    Some users may find that their Atlas Triggers are not firing or are not visible in the Atlas UI. We are investigating both symptoms and working to restore trigger processing. We will provide another update as we learn more.
  4. 19:59 UTC · monitoring
    Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.
  5. 20:54 UTC · resolved
    This incident has been resolved.
Source
Sep 30, 20262h 10mSEV 3
Delays in Atlas cluster management operationsMetrics ingestion delays slowed Atlas cluster creation and modification for some customers from 18:51 to 21:02 UTC on 30 September 2026. Cluster health was unaffected, but some clusters wrongly appeared degraded in the UI. A fix was deployed and operations returned to normal.AI-graded · some customers · MongoDB Cloud
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Cloud had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Cluster creation and modification were delayed for some customers for about two hours; running clusters kept serving, though the UI showed some as degraded.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 18:51 UTC · investigating
    We are investigating an issue with Atlas metrics ingestion that may delay cluster management operations, including cluster creation and modification.
  2. 19:01 UTC · identified
    We've identified an issue with metric ingestion that is causing delays to Atlas Cluster management operations for some customers. Clusters may also appear degraded in the Atlas UI while metrics ingestion is delayed; however, the cluster health is unaffected.
  3. 19:26 UTC · monitoring
    The team has implemented a fix and latency of Atlas Cluster management operations are returning to normal. Clusters that incorrectly appeared as degraded in the Atlas UI are also beginning to correctly update their status.
  4. 21:02 UTC · resolved
    This incident has been resolved.
Source
Sep 16, 20266h 25mSEV 4
Support Portal OutageMongoDB's Customer Support Portal had degraded or limited access from about 09:00 to 15:15 UTC on 2026-09-16. Customers needing urgent help were given phone numbers. The provider resolved the platform issues; no cause was stated and no database impact was reported.AI-graded · MongoDB Support Portal
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Support Portal had a major outage
  2. CLAUDE · SEV 4 · UNCLEAR · HIGH CONFIDENCE
    MongoDB Support Portal was degraded or inaccessible for about six hours; databases and product APIs were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 09:06 UTC · investigating
    MongoDB customers are currently experiencing degraded or limited access to the MongoDB Customer Support Portal (https://support.mongodb.com/). If 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: [These numbers have been removed. Active MongoDB customers can access them at the support portal.] We appreciate your patience.
  2. 09:09 UTC · investigating
    We are continuing to investigate this issue.
  3. 15:31 UTC · resolved
    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. We apologize for the service interruption and greatly appreciate your patience. Regards, The MongoDB Team
Source
Sep 11, 20262h 23mSEV 3
Atlas is experiencing issues with issuing certificates from Lets EncryptFree and Flex cluster provisioning was delayed by Let's Encrypt certificate issuance errors for about 2.5 hours; other operations were not described as affected.AI-graded · some customers · MongoDB Cloud +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because MongoDB Atlas for Government had a partial outage
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Free and Flex cluster provisioning was delayed by Let's Encrypt certificate issuance errors for about 2.5 hours; other operations were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 01:28 UTC · investigating
    We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.
  2. 02:01 UTC · monitoring
    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.
  3. 03:51 UTC · resolved
    This incident has been resolved.
Source
Sep 3, 2026ongoingSEV 3
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Cluster operations are impaired in AWS me-central-1 and me-south-1, per a linked original post; details of the impact are not given here.AI-graded · regional · MongoDB Cloud
Why this grade
  1. RULES · SEV 3
    Sev 3 because MongoDB Cloud had a partial outage
  2. CLAUDE · SEV 3 · REGIONAL · LOW CONFIDENCE
    Cluster operations are impaired in AWS me-central-1 and me-south-1, per a linked original post; details of the impact are not given here.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 16:44 UTC · monitoring
    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.
  2. 16:47 UTC · monitoring
    We are continuing to monitor for any further issues.
Source
Aug 28, 20260mSEV 3
MongoDB Atlas Log Integration service degradedSev 3 from the incident title (no components listed)
1 update
  1. 14:30 UTC · resolved
    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.
Source
Aug 19, 202625h 21mSEV 2
Issues rotating certificates for projects containing only Atlas Free and Flex clustersFor some projects with only Atlas Free or Flex clusters, TLS certificates were not rotating correctly, which could block connections to those clusters. Remediation was applied to impacted projects on 2026-08-19, and a fix was deployed on 2026-08-20 before the incident was resolved about 25 hours after it started.AI-graded · some customers · MongoDB Cloud
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Cloud had degraded performance
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    TLS certificate rotation failed for some projects containing only Free or Flex clusters, risking connection failures to those clusters; other clusters were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
7 updates
  1. 20:45 UTC · identified
    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.
  2. 21:50 UTC · monitoring
    We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue.
  3. 21:57 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 21:58 UTC · monitoring
    We are continuing to monitor for any further issues.
  5. 22:00 UTC · monitoring
    We are continuing to monitor for any further issues.
  6. 21:39 UTC · monitoring
    We have deployed fix, continuing the monitor for any further issues.
  7. 22:07 UTC · resolved
    This incident has been resolved.
Source
Aug 18, 20261h 06mSEV 3
Atlas UI and API Periodic UnavailabilityAtlas UI and API were periodically unavailable from 14:10 to 15:17 UTC on 18 August. A new internal workload overloaded a backing system; it was disabled and the incident resolved. Customer clusters and data were unaffected. Some internal jobs were delayed, slowing certain control-plane changes, and that was also resolved.AI-graded · MongoDB Cloud
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Cloud had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Atlas UI and control-plane API were intermittently unreachable for about an hour, blocking config changes; customer clusters stayed up.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 14:10 UTC · investigating
    We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.
  2. 14:57 UTC · identified
    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.
  3. 15:04 UTC · monitoring
    We have disabled the workload and are monitoring the situation
  4. 15:17 UTC · resolved
    This incident has been resolved. Following the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes. The issue was related to this incident "Atlas UI and API Periodic Unavailability" which has been remediated. Customer 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.
Source
Aug 5, 20266h 57mSEV 2
GCP capacity constraints affecting Atlas deploymentsA GCP capacity shortage across multiple regions caused errors and delays creating or modifying Atlas clusters, especially search-node deployments, and some customers saw host-down alerts. Starting 05:17 UTC, resolved 12:14 UTC on Aug 5 once symptoms subsided. Customers were advised to retry later or use another region or instance size.}AI-graded · some customers · MongoDB Cloud
Why this grade
  1. RULES · SEV 3
    Sev 3 because MongoDB Cloud had a partial outage
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    GCP capacity shortage caused cluster provisioning and modification errors across several regions for about seven hours; some customers saw host-down alerts.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 05:17 UTC · investigating
    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. Customers 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. MongoDB is working with GCP to understand the scope of the issue and restore capacity. Customers 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. We will provide another update as more information becomes available.
  2. 12:14 UTC · resolved
    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.
Source
Aug 3, 20262h 31mSEV 2
Elevated errors on VoyageAI APIsVoyageAI embedding and reranking APIs returned elevated 5xx errors for about 30 minutes before a fix; scope not stated.AI-graded · VoyageAI Embedding and Reranking Models
Why this grade
  1. RULES · SEV 1
    Sev 1 because VoyageAI Embedding and Reranking Models had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    VoyageAI embedding and reranking APIs returned elevated 5xx errors for about 30 minutes before a fix; scope not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:47 UTC · investigating
    VoyageAI APIs are experiencing elevated 5xx errors. We are investigating the issue.
  2. 19:02 UTC · monitoring
    A fix has been applied and we are monitoring the system.
  3. 21:18 UTC · resolved
    The system has returned to normal operation.
Source
Jul 29, 202642mSEV 3
Delayed cluster configuration affecting free and flex usersConfiguration updates for MongoDB Atlas free and flex tier clusters were delayed for about 40 minutes starting 18:55 UTC on July 29, 2026. Cluster access was unaffected. A configuration change rolled out to remediate the delay, and the incident was resolved at 19:37 UTC.AI-graded · some customers · MongoDB Cloud
Why this grade
  1. RULES · SEV 4
    Sev 4 because MongoDB Cloud had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Cluster configuration changes were delayed for free and flex tier users for about 40 minutes; cluster access was unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 18:55 UTC · investigating
    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.
  2. 19:06 UTC · identified
    We have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.
  3. 19:31 UTC · monitoring
    We have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.
  4. 19:37 UTC · resolved
    This incident has been resolved.
Source
Jul 29, 20264h 35mSEV 2
Atlas Stream Processing errors in Azure West EuropeStream processors in Azure West Europe hit internal errors for some users for about four and a half hours; other regions were not reported affected.AI-graded · regional · MongoDB Atlas Stream Processing
Why this grade
  1. RULES · SEV 2
    Sev 2 because MongoDB Atlas Stream Processing had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Stream processors in Azure West Europe hit internal errors for some users for about four and a half hours; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:11 UTC · investigating
    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.
  2. 22:35 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 22:47 UTC · resolved
    This incident has been resolved.
Source
Jul 27, 202611mSEV 2
VoyageAI elevated errorsVoyageAI embedding and reranking models showed elevated errors for about 11 minutes; the text does not say how many requests failed.AI-graded · VoyageAI Embedding and Reranking Models
Why this grade
  1. RULES · SEV 1
    Sev 1 because VoyageAI Embedding and Reranking Models had a partial outage
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    VoyageAI embedding and reranking models showed elevated errors for about 11 minutes; the text does not say how many requests failed.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 23:37 UTC · investigating
    All VoyageAI models are experiencing elevated errors. We are investigating the issue.
  2. 23:47 UTC · investigating
    We have fully recovered as of 16:41 PST.
  3. 23:48 UTC · resolved
    This incident has been resolved.
Source
Jul 23, 20264h 07mSEV 3
Cluster connectivity issues in Azure westusSev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
5 updates
  1. 16:21 UTC · investigating
    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.
  2. 16:38 UTC · identified
    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
  3. 18:26 UTC · identified
    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.
  4. 18:54 UTC · identified
    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.
  5. 20:28 UTC · resolved
    Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete.
Source
Jul 17, 20263d 20hSEV 2
MongoDB Atlas and Atlas for Government: New AWS Backup and AWS Data Transfer costs will be unavailable between July 17 and 20Sev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Cloud +1
3 updates
  1. 16:14 UTC · identified
    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. Cluster and backup health are unaffected. Other cloud providers' billing data is unaffected. You can follow the upstream incident at https://health.aws.amazon.com/health/status
  2. 15:06 UTC · monitoring
    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.
  3. 13:08 UTC · resolved
    This incident has been resolved.
Source
Jul 9, 20262h 07mSEV 2
Atlas Stream Processing is experiencing issues in Azure - West EuropeSev 2 because MongoDB Atlas Stream Processing had degraded performanceMongoDB Atlas Stream Processing
3 updates
  1. 23:03 UTC · investigating
    We are currently investigating an issue affecting Stream Processing Azure West Europe. User initiated commands & workloads may see intermittent failures.
  2. 00:32 UTC · monitoring
    A fix has been implemented and we are monitoring the region.
  3. 01:11 UTC · resolved
    The issue has been resolved.
Source
Jul 9, 202619h 19mSEV 4
Atlas is experiencing issues with issuing certificates from Lets EncryptSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
3 updates
  1. 19:37 UTC · investigating
    We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Tenant cluster provisioning is currently impacted.
  2. 21:22 UTC · monitoring
    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.
  3. 14:56 UTC · resolved
    Let's Encrypt service has returned to normal.
Source
Jul 9, 202643mSEV 2
Atlas Data Federation and Online Archive cloud-provider IAM authentication errorSev 2 because MongoDB Atlas Data Federation and Online Archive had degraded performanceMongoDB Atlas Data Federation and Online Archive
4 updates
  1. 10:23 UTC · investigating
    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.
  2. 10:57 UTC · identified
    We have identified that the issue is caused by a recent configuration change to IAM authentication and are working on a fix.
  3. 11:01 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 11:06 UTC · resolved
    This incident has been resolved.
Source
Jul 2, 202627mSEV 2
Impaired Cluster Operations due to Lets Encrypt Service DegradationSev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Cloud +1
2 updates
  1. 23:09 UTC · monitoring
    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.
  2. 23:36 UTC · resolved
    Let's Encrypt services have returned back to normal. Cluster operations have now returned to normal.
Source
Jul 2, 20261h 32mSEV 2
Impaired Cluster Operations due to Lets Encrypt OutageSev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Cloud +1
2 updates
  1. 19:34 UTC · monitoring
    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.
  2. 21:06 UTC · resolved
    We've confirmed that Lets Encrypt has returned to normal operations. Cluster operations are now back to normal.
Source
Jul 2, 202623mSEV 4
AWS cluster backup and restore operations are failingSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
3 updates
  1. 10:45 UTC · investigating
    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. We are also investigation potential impact to other operations on AWS clusters such as modifying instance size.
  2. 10:50 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 11:09 UTC · resolved
    This incident has been resolved. AWS clusters should no longer encounter errors during backup and restore.
Source
Jun 25, 20260mSEV 4
MongoDB Atlas: Atlas UI loading issuesSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
1 update
  1. 10:16 UTC · resolved
    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. We 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.
Source
Jun 4, 20262h 07mSEV 2
Increased error rate creating and managing Search and Vector Search indexesSev 2 because MongoDB Atlas Search had degraded performanceMongoDB Atlas Search
2 updates
  1. 15:33 UTC · monitoring
    A fix has been implemented and we are monitoring the results
  2. 17:39 UTC · resolved
    This incident has been resolved.
Source
Jun 2, 20261h 11mSEV 1
Investigating connection issues to ADFA in GCPSev 1 because MongoDB Atlas Data Federation and Online Archive had a partial outageMongoDB Atlas Data Federation and Online Archive
5 updates
  1. 23:00 UTC · investigating
    We are currently investigating issues connecting and querying to Atlas Data Federation and Online Archive instances in GCP regions
  2. 23:42 UTC · identified
    We've identified an issue with networking in GCP regions and are working on fix
  3. 00:01 UTC · identified
    Issues connecting to ADF and OA instances in GCP belgium-eu region has been mitigated, and working on other GCP regions.
  4. 00:05 UTC · monitoring
    All ADF and OA connections in GCP are reporting as successful, and we will continue to monitor.
  5. 00:11 UTC · resolved
    Issue has been mitigated and connections should be working now to ADF and OA instances in GCP regions.
Source
May 28, 20261h 13mSEV 2
Metrics may fail to send to DataDog Gov integrationsSev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Atlas for Government
2 updates
  1. 22:02 UTC · investigating
    Starting approximately 17:00 UTC, some Atlas for Government users may be experiencing gaps in metrics sent to their DataDog Gov integration. We are investigating this issue.
  2. 23:15 UTC · resolved
    The issue has been resolved.
Source
May 23, 20266h 18mSEV 2
Authentication failures when running search queries for some clustersSev 2 because MongoDB Atlas Search had degraded performanceMongoDB Cloud +1
4 updates
  1. 19:48 UTC · investigating
    We are investigating an issue impacting some clusters that causes search queries to fail with authentication failures.
  2. 20:14 UTC · identified
    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.
  3. 00:14 UTC · monitoring
    We have resolved the issue for all impacted clusters. We continue to monitor the fleet for any residual impact.
  4. 02:05 UTC · resolved
    This incident has been resolved.
Source
May 22, 20261h 45mSEV 2
[Atlas for Government] Data plane node logs unavailable for last 6 daysSev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Atlas for Government
3 updates
  1. 20:32 UTC · investigating
    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.
  2. 21:17 UTC · monitoring
    We have applied the fix. The data plane node logs will start to be available to customers within the next 30 minutes.
  3. 22:17 UTC · resolved
    The data plane node log download has recovered.
Source
May 8, 20262h 33mSEV 2
Impaired Cluster Operations due to Lets Encrypt OutageSev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Cloud +1
3 updates
  1. 19:33 UTC · monitoring
    Cluster operations are currently impaired due to issues with Lets Encrypt. We are actively monitoring the situation as more updates come in.
  2. 21:39 UTC · monitoring
    Lets Encrypt is now reporting as healthy. We will continue monitoring as cluster operations return to a healthy state.
  3. 22:07 UTC · resolved
    This incident has been resolved.
Source
May 8, 202636h 00mSEV 4
AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
5 updates
  1. 02:24 UTC · identified
    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. Please see https://health.aws.amazon.com/health/status for more information.
  2. 03:12 UTC · monitoring
    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. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.
  3. 12:34 UTC · monitoring
    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. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.
  4. 20:41 UTC · monitoring
    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. We continue to monitor the situation. Please see https://health.aws.amazon.com/health/status for more information.
  5. 14:24 UTC · resolved
    This incident has been resolved.
Source
May 7, 20266h 58mSEV 1
AWS Cluster DNS Changes Degraded PerformanceSev 1 because MongoDB Atlas for Government had a partial outageMongoDB Atlas for Government
7 updates
  1. 15:17 UTC · identified
    DNS changes for AWS clusters are currently degraded. We've identified the issue and are pushing out a patch.
  2. 15:20 UTC · identified
    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.
  3. 16:58 UTC · identified
    Mitigation is in progress; recovery for DNS operations and downstream cluster topology changes has begun.
  4. 17:50 UTC · investigating
    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.
  5. 19:47 UTC · monitoring
    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.
  6. 19:47 UTC · monitoring
    We are continuing to monitor for any further issues.
  7. 22:15 UTC · resolved
    DNS updates for ACME are confirmed healthy. Cluster updates are now proceeding as expected.
Source
May 6, 202623h 07mSEV 1
Atlas Backup Export Jobs Degraded PerformanceSev 1 because MongoDB Atlas for Government had a partial outageMongoDB Cloud +1
4 updates
  1. 21:48 UTC · identified
    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
  2. 01:20 UTC · identified
    We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.
  3. 20:02 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 20:55 UTC · resolved
    This incident has been resolved.
Source
May 3, 202647h 54mSEV 4
Partial outage in Azure West EuropeSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
3 updates
  1. 17:33 UTC · investigating
    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.
  2. 20:19 UTC · monitoring
    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.
  3. 17:28 UTC · resolved
    We are no longer observing these issues in Azure West Europe. Atlas Clusters in the region should be healthy and fully operational.
Source
Apr 27, 20263h 33mSEV 3
Increase in Billing for Backup UsageSev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
2 updates
  1. 17:16 UTC · identified
    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. We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end. Please contact MongoDB Support with any questions. We will post another update by April 27 at 22:00 UTC.
  2. 20:50 UTC · resolved
    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.
Source
Apr 17, 20263d 20hSEV 1
MongoDB Atlas BI Connector: Connections and queries failSev 1 because MongoDB Atlas for Government had a partial outageMongoDB Atlas for Government
4 updates
  1. 17:03 UTC · investigating
    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. Underlying cluster health is not affected.
  2. 20:24 UTC · identified
    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. Cluster health is unaffected.
  3. 19:17 UTC · monitoring
    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.
  4. 13:45 UTC · resolved
    This incident has been resolved.
Source
Apr 1, 20260mSEV 2 · SECURITY
Atlas Charts users unable to loginSev 3 because MongoDB Charts had degraded performance, raised to Sev 2 for securityMongoDB Charts
1 update
  1. 12:55 UTC · resolved
    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.
Source
Mar 30, 20261h 23mSEV 4
Delays in cluster creation and adding new cluster nodes in Azure East US 2 regionSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
2 updates
  1. 21:47 UTC · identified
    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. What you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region. User action: As a workaround, users can provision clusters in other Azure regions.
  2. 23:10 UTC · resolved
    We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.
Source
Mar 25, 202639h 50mSEV 3
Intermittent 503 Errors on Atlas Admin API and Automation ToolingSev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
4 updates
  1. 21:31 UTC · investigating
    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. Our 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.
  2. 23:39 UTC · monitoring
    The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
  3. 19:12 UTC · monitoring
    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.
  4. 13:21 UTC · resolved
    We are no longer seeing intermittent spikes in HTTP 503 errors.
Source
Mar 19, 20261h 09mSEV 1
Issue querying Azure blob storage containers in Atlas Data FederationSev 1 because MongoDB Atlas Data Federation and Online Archive had a partial outageMongoDB Atlas Data Federation and Online Archive
5 updates
  1. 18:11 UTC · investigating
    We are currently investigating an issue when Atlas Data Federation tries to read data from customer Azure blob storage containers.
  2. 18:25 UTC · identified
    The issue has been identified and we are working on a fix.
  3. 19:01 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:14 UTC · monitoring
    We are continuing to monitor for any further issues.
  5. 19:19 UTC · resolved
    This incident has been resolved.
Source
Mar 19, 202645mSEV 3
MongoDB Atlas: Clusters page failing to loadSev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
3 updates
  1. 14:42 UTC · identified
    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. Cluster health is unaffected.
  2. 15:17 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 15:28 UTC · resolved
    This incident has been resolved.
Source
Mar 19, 202612d 20hSEV 2
MongoDB Atlas for Government: SSO login failures for some usersSev 2 because MongoDB Atlas for Government had degraded performanceMongoDB Atlas for Government
3 updates
  1. 00:24 UTC · identified
    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. Root 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. What you might see: - A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL. - An inability to complete login when using a federated identity provider link. Our actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users. User 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. Next 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.
  2. 22:15 UTC · monitoring
    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.
  3. 21:19 UTC · resolved
    This incident has been resolved.
Source
Mar 11, 20260mSEV 2
Issue affecting stream processing within the AWS US-EAST-1 regionSev 2 because MongoDB Atlas Stream Processing had degraded performanceMongoDB Atlas Stream Processing
1 update
  1. 20:10 UTC · resolved
    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.
Source
Mar 11, 20260mSEV 3
MongoDB Atlas Admin API: Temporary failures for tools using older API versionsSev 3 from the incident title (no components listed)
1 update
  1. 12:00 UTC · resolved
    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. This 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. We 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. From 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. No user action is required. Previously failed operations can be retried and should now succeed.
Source
Mar 10, 20263h 11mSEV 3
Atlas Clusters Snapshot FailuresSev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
4 updates
  1. 23:18 UTC · investigating
    Atlas cluster snapshots are failing. We are actively investigating.
  2. 00:45 UTC · identified
    The issue has been identified and a fix is being implemented.
  3. 02:21 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 02:30 UTC · resolved
    This incident has been resolved.
Source
Mar 2, 202639mSEV 3
MongoDB Atlas: Email notifications may be failingSev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
2 updates
  1. 15:50 UTC · investigating
    We are currently investigating this issue. Some users may not be receiving emails from MongoDB. We are looking into the cause and will provide an update as soon as we know more.
  2. 16:28 UTC · resolved
    This incident has been resolved. Email notifications are being sent successfully.
Source
Mar 1, 2026185d 21hSEV 3
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Sev 3 because MongoDB Cloud had a partial outageMongoDB Cloud
25 updates
  1. 13:48 UTC · identified
    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). Root 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. What you might see: - Cluster create/scale/modify operations remaining in a pending or in-progress state longer than usual - Slower completion of some maintenance and infrastructure operations in the affected region Our actions: - Monitoring the AWS incident and Atlas fleet behavior in me-central-1 Customer 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. Next update: We will provide updates on this page as AWS progresses mitigation or if we observe any change in impact to Atlas customers.
  2. 14:55 UTC · identified
    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. We continue to closely monitor Atlas deployments in ME-CENTRAL-1 and will provide additional updates if we observe any further impact to Atlas customers.
  3. 19:30 UTC · identified
    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). If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.
  4. 02:17 UTC · identified
    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). If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support.
  5. 16:17 UTC · identified
    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. CURRENT IMPACT Atlas clusters deployed only in me-central-1 may be fully unavailable. For clusters operating solely in me-central-1, backup operations in this region are impaired. Clusters 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. AWS has indicated an extended resolution timeline for service in the impacted Regions and Availability Zones. RECOMMENDED CUSTOMER ACTIONS If you have a multi-region configuration that includes a healthy secondary region, we recommend routing application traffic to that secondary region. If you have clusters in me-south-1 taking backups, we recommend enabling "Additional Snapshot Copies Policy" to a different region. If 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. WHAT WE ARE DOING We 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. We will provide further updates as circumstances continue to change.
  6. 19:58 UTC · identified
    CURRENT IMPACT 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. AWS is currently experiencing infrastructure impairments in two Middle East regions: * 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. * 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. Because 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. The impact of these events depends on your Atlas cluster topology and configuration: * Customers using multi–region deployments, global clusters, or replicas located in unaffected Availability Zones or regions may see little to no impact. * Customers with clusters or workloads primarily located in the affected Availability Zones may experience reduced availability or degraded performance. * Clusters deployed entirely in unaffected Availability Zones or outside the impacted regions are operating normally. AVAILABLE OPTIONS Depending on your application requirements and cluster configuration, you may consider the following options: 1. Move the cluster to another region that is not impacted. 2. Add electable nodes in another region, which can enable the cluster to establish a minimum viable topology and restore database operations. 3. Take no action and wait for the affected Availability Zones to be fully recovered. HOW TO GET HELP If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  7. 17:20 UTC · identified
    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. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 4 at 00:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  8. 22:54 UTC · identified
    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. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 4 at 06:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  9. 06:03 UTC · identified
    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. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 4 at 12:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  10. 16:33 UTC · identified
    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. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 5 at 12:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  11. 14:59 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 6 at 14:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  12. 14:24 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 7 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  13. 15:28 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. We will provide another update by March 8 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  14. 15:42 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We will provide another update by March 9 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  15. 16:02 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We will provide another update by March 10 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  16. 15:59 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We will provide another update by March 11 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  17. 15:48 UTC · identified
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  18. 15:51 UTC · monitoring
    According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  19. 15:33 UTC · monitoring
    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. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may consider extending their backup snapshot expirations in me-central-1 as needed. We 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  20. 21:35 UTC · monitoring
    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. We 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. We 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. 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  21. 16:02 UTC · monitoring
    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. We 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. We 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. We 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  22. 15:33 UTC · monitoring
    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. We 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. We 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. We 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  23. 16:02 UTC · monitoring
    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. We 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. We 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. We 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. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  24. 15:46 UTC · monitoring
    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. We 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. We 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. We will move to an as-needed status post update cadence as new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
  25. 16:47 UTC · resolved
    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 We will update this post as necessary. Thanks in advance for your understanding.
Source
Feb 28, 202631h 11mSEV 1
MongoDB App Services: Connectivity issuesSev 1 because MongoDB Atlas App Services and Device Sync had a partial outageMongoDB Atlas App Services and Device Sync
3 updates
  1. 19:53 UTC · investigating
    We are currently investigating an issue with Atlas App Services Device Sync. Affected users of this deprecated service may see SSL validation errors. We will update this post with more details as they become available.
  2. 05:37 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 03:05 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
UpstashGrade A+100.00% up4 incidentsMTTR 0m~$22.25/moPlanetScaleGrade A100.00% up5 incidentsMTTR 26m$10/moCockroachDB CloudGrade B100.00% up5 incidentsMTTR 7h 00m–/moMongoDB AtlasGrade D100.00% up18 incidentsMTTR 2h 35m$56.94/moSupabaseGrade F100.00% up26 incidentsMTTR 2h 00m$25.25/mo

README badge

MongoDB Atlas's live grade, for your README.

MongoDB Atlas grade badge
[![mongodb on downagain.dev](https://downagain.dev/badge/mongodb.svg)](https://downagain.dev/p/mongodb)