Skip to content

MongoDB Atlas (database clusters) SLA

MongoDB · Databases · promises up to 99.995% · SLA of Jun 23, 2021 · checked 26h ago

1 major outage in the last 365 days. Worst region me-central-1: 60 min counted, 99.989% observed against the 99.995% Dedicated clusters M10 and above, which applies per region.

1 of 12 months fell below it (credits are claimed per month).

Last 90 days: no major outage.

Incidents, last 365 days

Latest 25 of 54.

Major outage time per month

Allowed per month: 2.2 min

Commitments and credits

  • Dedicated clusters M10 and aboveAtlas deployments at level M10 or above that have been up at least 24 hours (replica sets, sharded and multi-region alike; the SLA makes no distinction)99.995%below 99.995%: 10% · below 99%: 25% · below 95%: 100%

SLA changes

  • Jun 23, 2021MongoDB Atlas (database clusters)Coverage expanded from M30+ to M10+ clusters; 99.995% and the 10/25/100% credit schedule unchanged. April 2021 snapshot (version 'Last updated: June 1, 2020') reads 'applies only to MongoDB Atlas deployments at level M30 or above'.Source
  • Jun 1, 2020MongoDB Atlas (database clusters)MongoDB's changelog states: 'We have updated our service credit offering for failures of uptime.' The pre-change numbers could not be verified: the earliest Wayback capture (2020-10-01) is already after this change.Source

More in databases

Terms, exclusions and sources
Measured
Monthly Uptime Percentage per Atlas cluster; a minute is unavailable if all continuous connection attempts to the cluster fail
Credit cap
100% of the Applicable Monthly Service Fees for the affected cluster
Claim window
Log a support ticket within 24 hours of becoming aware; submit claim by the end of the month following the month of Downtime
How to claim
Support ticket with request logs, time/duration of Downtime, affected users and remediation attempts; credit applied to a future invoice for that cluster
Not covered
Factors outside MongoDB's reasonable control (natural disaster, war, government action, network failures at customer site); Third-party services incl. the cloud platforms Atlas runs on; Use of customer's password or equipment; Improper use, scaling or configuration, or poor security practices; MongoDB Beta Offerings; Scheduled maintenance and upgrades (not counted as Downtime)
Status history
Status history since Sep 22, 2025
< 99.995% but equal to or greater than 99.0% | 10% | < 99.0% | 25% | < 95.0% | 100%
MongoDB, Last updated: June 23, 2021. Read the SLA

The current SLA has a single 99.995% commitment; there are no separate replica-set vs sharded vs multi-region tiers on the page. Free/shared tiers (M0, Flex) and anything below M10 are not covered. 'We will provide at least 90 days' advance notice for adverse changes to this SLA.' The old URL mongodb.com/cloud/atlas/sla redirects here.

All MongoDB SLAsHow this is measured

Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

SLA changes by email

Fridays, only in weeks when a cloud, data or AI vendor changed an SLA.

Double opt-in. Unsubscribe any time.