Databases / Document database / MongoDB Atlas

MongoDB Atlas

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

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

CompareStatus page
GradeCLast 90 days
CPRODBSHIP
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 C
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.
46h 33m

By area

CProduction
6INCIDENTS
21h 15mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 5, 2026 · 6h 57mGCP capacity constraints affecting Atlas deployments
SEV 2Oct 1, 2026 · 5h 13mTrigger processing may be delayed globally
SEV 2Jul 29, 2026 · 4h 35mAtlas Stream Processing errors in Azure West Europe
Most hit
VoyageAI Embedding and Reranking Models2
MongoDB Atlas Search1
MongoDB Atlas App Services and Device Sync1
MongoDB Cloud1
Worse. 19 in the last 6 months, 5 in the 6 before.
BShipping
5INCIDENTS
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 3Sep 3, 2026 · ongoingImpaired Cluster operations in AWS me-central-1 and AWS me-south-1
SEV 3Sep 11, 2026 · 2h 23mAtlas is experiencing issues with issuing certificates from Lets Encrypt
Most hit
MongoDB Cloud3
MongoDB Atlas for Government1
Better. 6 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 down6
Sev 3 · Can't shipCan't deploy, build or manage it4
Sev 4 · PapercutDocs, status page, slow dashboard8

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 25Sev 1–2

Incident history

Show all 50
Oct 20, 202612h 36mSEV 4
GCP Availability Zone europe-west2-b connectivity issuesSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
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 4
Admin Admin API: Intermittent Increase in 5xx errorsSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
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 4
MongoDB Charts: Infinite login loop when creating new Charts projectsSev 4 because MongoDB Charts had degraded performanceMongoDB Charts
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 4
Delays in Atlas cluster management operationsSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
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 OutageSev 4 because MongoDB Support Portal had a major outageMongoDB Support Portal
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 4
Issues rotating certificates for projects containing only Atlas Free and Flex clustersSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
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 4
Atlas UI and API Periodic UnavailabilitySev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
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 4
Delayed cluster configuration affecting free and flex usersSev 4 because MongoDB Cloud had degraded performanceMongoDB Cloud
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

Peers, 90 days

Compare
UpstashGrade A+100.00% up4 incidentsMTTR 0m~$22.25/moPlanetScaleGrade A99.99% up5 incidentsMTTR 26m$10/moCockroachDB CloudGrade B100.00% up5 incidentsMTTR 7h 00m–/moMongoDB AtlasGrade C100.00% up18 incidentsMTTR 2h 35m$56.94/moSupabaseGrade F100.00% up26 incidentsMTTR 2h 02m$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)