Skip to content

Outage tracker / MongoDB Atlas

Is MongoDB Atlas down?

I'm having a problem

Operationalchecked 1 minute ago

We reached MongoDB Atlas from all 10 regions we check.

As of Oct 5, 2026, 9:03 PM UTC, MongoDB Atlas answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured MongoDB Atlas (since Aug 20, 2026).

MongoDB Atlas reports an active incident: "Impaired Cluster operations in AWS me-central-1 and AWS me-south-1" (partial outage, since Sep 3, 2026, 4:44 PM UTC). That is their claim, not our measurement: our probes are currently reaching MongoDB Atlas, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Oct 5, 2026, 9:03 PM UTC
US-East201 msOperational
US-West558 msOperational
Europe425 msOperational
Asia-Pacific884 msOperational
US-Central515 msOperational
Canada566 msOperational
UK560 msOperational
Southeast Asia1141 msOperational
Australia1296 msOperational
South America1033 msOperational
their status pagetheir claim, not our reading

MongoDB Atlas reports: All systems operational (“All Systems Operational”)

from MongoDB Atlas's own status page, checked Oct 5, 2026, 8:58 PM UTC

MongoDB Atlas reports an active incident: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1 (partial outage, since Sep 3, 2026, 4:44 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

Our probes and MongoDB Atlas's own status page agree: both show MongoDB Atlas as reachable right now.

MongoDB Atlas's own component breakdown, as they publish it

  • MongoDB CloudOperational
  • MongoDB Support PortalOperational
  • MongoDB Atlas App Services and Device SyncOperational
  • MongoDB Atlas Data Federation and Online ArchiveOperational
  • MongoDB Atlas SearchOperational
  • MongoDB ChartsOperational
  • MongoDB Atlas Stream ProcessingOperational
  • MongoDB Atlas for GovernmentOperational
  • VoyageAI Embedding and Reranking ModelsOperational
  • MongoDB Atlas Agent EngineOperational

These are MongoDB Atlas's components, named and scored by MongoDB Atlas. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is MongoDB Atlas's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

MongoDB Atlas response time, by region

US-East
617msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 610ms2026-09-07 UTC: p95 613ms2026-09-08 UTC: p95 605ms2026-09-09 UTC: p95 588ms2026-09-10 UTC: p95 602ms2026-09-11 UTC: p95 600ms2026-09-12 UTC: p95 577ms2026-09-13 UTC: p95 560ms2026-09-14 UTC: p95 587ms2026-09-15 UTC: p95 590ms2026-09-16 UTC: p95 762ms2026-09-17 UTC: p95 783ms2026-09-18 UTC: p95 697ms2026-09-19 UTC: p95 601ms2026-09-20 UTC: p95 559ms2026-09-21 UTC: p95 566ms2026-09-22 UTC: p95 556ms2026-09-23 UTC: p95 677ms2026-09-24 UTC: p95 662ms2026-09-25 UTC: p95 657ms2026-09-26 UTC: p95 638ms2026-09-27 UTC: p95 609ms2026-09-28 UTC: p95 567ms2026-09-29 UTC: p95 635ms2026-09-30 UTC: p95 563ms2026-10-01 UTC: p95 628ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 597ms2026-10-04 UTC: p95 596ms2026-10-05 UTC: p95 617ms
Sep 6Sep 20Oct 5
US-West
674msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 537ms2026-09-10 UTC: p95 582ms2026-09-11 UTC: p95 631ms2026-09-12 UTC: p95 549ms2026-09-13 UTC: p95 701ms2026-09-14 UTC: p95 554ms2026-09-15 UTC: p95 713ms2026-09-16 UTC: p95 761ms2026-09-17 UTC: p95 671ms2026-09-18 UTC: p95 675ms2026-09-19 UTC: p95 670ms2026-09-20 UTC: p95 645ms2026-09-21 UTC: p95 704ms2026-09-22 UTC: p95 825ms2026-09-23 UTC: p95 958ms2026-09-24 UTC: p95 962ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 981ms2026-09-27 UTC: p95 756ms2026-09-28 UTC: p95 710ms2026-09-29 UTC: p95 680ms2026-09-30 UTC: p95 724ms2026-10-01 UTC: p95 895ms2026-10-02 UTC: p95 702ms2026-10-03 UTC: p95 720ms2026-10-04 UTC: p95 717ms2026-10-05 UTC: p95 674ms
Sep 6Sep 20Oct 5
Europe
608msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 669ms2026-09-07 UTC: p95 602ms2026-09-08 UTC: p95 613ms2026-09-09 UTC: p95 601ms2026-09-10 UTC: p95 671ms2026-09-11 UTC: p95 646ms2026-09-12 UTC: p95 717ms2026-09-13 UTC: p95 680ms2026-09-14 UTC: p95 685ms2026-09-15 UTC: p95 770ms2026-09-16 UTC: p95 600ms2026-09-17 UTC: p95 624ms2026-09-18 UTC: p95 642ms2026-09-19 UTC: p95 621ms2026-09-20 UTC: p95 637ms2026-09-21 UTC: p95 609ms2026-09-22 UTC: p95 582ms2026-09-23 UTC: p95 529ms2026-09-24 UTC: p95 579ms2026-09-25 UTC: p95 575ms2026-09-26 UTC: p95 551ms2026-09-27 UTC: p95 573ms2026-09-28 UTC: p95 627ms2026-09-29 UTC: p95 660ms2026-09-30 UTC: p95 552ms2026-10-01 UTC: p95 707ms2026-10-02 UTC: p95 643ms2026-10-03 UTC: p95 625ms2026-10-04 UTC: p95 621ms2026-10-05 UTC: p95 608ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
US-Central
830msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 529ms2026-09-07 UTC: p95 537ms2026-09-08 UTC: p95 546ms2026-09-09 UTC: p95 532ms2026-09-10 UTC: p95 593ms2026-09-11 UTC: p95 775ms2026-09-12 UTC: p95 809ms2026-09-13 UTC: p95 809ms2026-09-14 UTC: p95 663ms2026-09-15 UTC: p95 831ms2026-09-16 UTC: p95 618ms2026-09-17 UTC: p95 514ms2026-09-18 UTC: p95 455ms2026-09-19 UTC: p95 576ms2026-09-20 UTC: p95 451ms2026-09-21 UTC: p95 507ms2026-09-22 UTC: p95 538ms2026-09-23 UTC: p95 514ms2026-09-24 UTC: p95 464ms2026-09-25 UTC: p95 646ms2026-09-26 UTC: p95 737ms2026-09-27 UTC: p95 700ms2026-09-28 UTC: p95 727ms2026-09-29 UTC: p95 729ms2026-09-30 UTC: p95 678ms2026-10-01 UTC: p95 665ms2026-10-02 UTC: p95 561ms2026-10-03 UTC: p95 577ms2026-10-04 UTC: p95 800ms2026-10-05 UTC: p95 830ms
Sep 6Sep 20Oct 5
Canada
756msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 632ms2026-09-07 UTC: p95 692ms2026-09-08 UTC: p95 645ms2026-09-09 UTC: p95 730ms2026-09-10 UTC: p95 754ms2026-09-11 UTC: p95 706ms2026-09-12 UTC: p95 662ms2026-09-13 UTC: p95 646ms2026-09-14 UTC: p95 668ms2026-09-15 UTC: p95 612ms2026-09-16 UTC: p95 546ms2026-09-17 UTC: p95 643ms2026-09-18 UTC: p95 634ms2026-09-19 UTC: p95 631ms2026-09-20 UTC: p95 620ms2026-09-21 UTC: p95 503ms2026-09-22 UTC: p95 567ms2026-09-23 UTC: p95 649ms2026-09-24 UTC: p95 612ms2026-09-25 UTC: p95 677ms2026-09-26 UTC: p95 572ms2026-09-27 UTC: p95 576ms2026-09-28 UTC: p95 531ms2026-09-29 UTC: p95 491ms2026-09-30 UTC: p95 554ms2026-10-01 UTC: p95 706ms2026-10-02 UTC: p95 575ms2026-10-03 UTC: p95 671ms2026-10-04 UTC: p95 636ms2026-10-05 UTC: p95 756ms
Sep 6Sep 20Oct 5
UK
621msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 515ms2026-09-07 UTC: p95 463ms2026-09-08 UTC: p95 475ms2026-09-09 UTC: p95 645ms2026-09-10 UTC: p95 504ms2026-09-11 UTC: p95 486ms2026-09-12 UTC: p95 522ms2026-09-13 UTC: p95 440ms2026-09-14 UTC: p95 434ms2026-09-15 UTC: p95 471ms2026-09-16 UTC: p95 613ms2026-09-17 UTC: p95 602ms2026-09-18 UTC: p95 597ms2026-09-19 UTC: p95 637ms2026-09-20 UTC: p95 673ms2026-09-21 UTC: p95 713ms2026-09-22 UTC: p95 739ms2026-09-23 UTC: p95 823ms2026-09-24 UTC: p95 877ms2026-09-25 UTC: p95 821ms2026-09-26 UTC: p95 764ms2026-09-27 UTC: p95 943ms2026-09-28 UTC: p95 974ms2026-09-29 UTC: p95 947ms2026-09-30 UTC: p95 984ms2026-10-01 UTC: p95 863ms2026-10-02 UTC: p95 868ms2026-10-03 UTC: p95 911ms2026-10-04 UTC: p95 826ms2026-10-05 UTC: p95 621ms
Sep 6Sep 20Oct 5
Southeast Asia
1.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 3.7s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 3.5s2026-09-24 UTC: p95 3.6s2026-09-25 UTC: p95 3.0s2026-09-26 UTC: p95 3.5s2026-09-27 UTC: p95 3.5s2026-09-28 UTC: p95 3.8s2026-09-29 UTC: p95 2.0s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
Australia
1.7sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.1s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 2.0s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.7s
Sep 6Sep 20Oct 5
South America
1.5sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 923ms2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 923ms2026-09-22 UTC: p95 991ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 922ms2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5

Is it MongoDB Atlas, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not MongoDB Atlas -- it cannot diagnose MongoDB Atlas's own systems.

Get an email when we see MongoDB Atlas go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching MongoDB Atlas, and again when they can reach it again. That is our own measurement from ten regions, not MongoDB Atlas's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 201msstatus code: 401checked: Oct 5, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach MongoDB Atlas normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 558msstatus code: 401checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach MongoDB Atlas normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 515msstatus code: 401checked: Oct 5, 2026, 8:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach MongoDB Atlas normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 566msstatus code: 401checked: Oct 5, 2026, 9:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach MongoDB Atlas normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1033msstatus code: 401checked: Oct 5, 2026, 8:59 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach MongoDB Atlas normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 425msstatus code: 401checked: Oct 5, 2026, 8:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach MongoDB Atlas normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 560msstatus code: 401checked: Oct 5, 2026, 9:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach MongoDB Atlas normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 884msstatus code: 401checked: Oct 5, 2026, 8:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach MongoDB Atlas normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1141msstatus code: 401checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach MongoDB Atlas normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1296msstatus code: 401checked: Oct 5, 2026, 8:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach MongoDB Atlas normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using MongoDB Atlas, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for MongoDB Atlas yet, which is not evidence that nothing is wrong.

Recent outages

MongoDB Charts: Infinite login loop when creating new Charts projects, 5hdeclared on their status page2026-10-02
Trigger processing may be delayed globally, 5h 13mdeclared on their status page2026-10-01
Delays in Atlas cluster management operations, 2h 10mdeclared on their status page2026-09-30
Support Portal Outage, 6h 25mdeclared on their status page2026-09-16
Atlas is experiencing issues with issuing certificates from Lets Encrypt, 2h 23mdeclared on their status page2026-09-11
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1declared on their status page2026-09-03
MongoDB Atlas Log Integration service degraded, 1mdeclared on their status page2026-08-28
Issues rotating certificates for projects containing only Atlas Free and Flex clusters, 25h 21mdeclared on their status page2026-08-19

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring MongoDB Atlas since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for MongoDB Atlas covering any window you pick, with our measurements and MongoDB Atlas's own claim at the time, side by side.

Full availability history for MongoDB Atlas: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

MongoDB Atlas uptime measured by RealUptimeLive, from this page's own readings.
[![MongoDB Atlas uptime measured by RealUptime](https://realuptime.io/outages/mongodb-atlas/badge.svg?days=30)](https://realuptime.io/outages/mongodb-atlas)
<a href="https://realuptime.io/outages/mongodb-atlas"><img src="https://realuptime.io/outages/mongodb-atlas/badge.svg?days=30" alt="MongoDB Atlas uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What MongoDB Atlas's SLA implies, from our measurement

At or above your target

We measured none of downtime for MongoDB Atlas over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from MongoDB Atlas's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://cloud.mongodb.com/api/atlas/v2/groups
secondary
https://status.mongodb.com/
RealUptime is not affiliated with MongoDB Atlas; the name identifies what we measured, and nothing here speaks for MongoDB Atlas's own team. We send a single web request to MongoDB Atlas from 10 regions on our own schedule and time the response. We do not see inside MongoDB Atlas's systems, do not use an account or real transaction, and are not the same signal MongoDB Atlas's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for MongoDB Atlas is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.