Skip to content

Outage tracker / MongoDB Atlas

Is MongoDB Atlas down?

I'm having a problem

Vendor lists an old incident, not shown as liveWhat MongoDB Atlas reports

MongoDB Atlas still lists an incident opened on 2026-09-03 with no update since 2026-09-03; we do not show it as live.

As of the last successful poll, 2026-10-22 19:00 UTC.

MongoDB Atlas's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of MongoDB Atlas pass from all 10 regions we check.

As of Oct 22, 2026, 7:04 PM UTC, RealUptime's checks of MongoDB Atlas passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 7:04 PM UTC
US-East1203 msChecks passing
US-West1346 msChecks passing
Europe601 msChecks passing
Asia-Pacific2228 msChecks passing
US-Central335 msChecks passing
Canada977 msChecks passing
UK2374 msChecks passing
Southeast Asia1716 msChecks passing
Australia979 msChecks passing
South America1811 msChecks passing
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 22, 2026, 6:52 PM UTC
MongoDB Atlas's own status page shows no incident, and our checks of MongoDB Atlas pass 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
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 616ms2026-10-06 UTC: p95 720ms2026-10-07 UTC: p95 652ms2026-10-08 UTC: p95 651ms2026-10-09 UTC: p95 668ms2026-10-10 UTC: p95 550ms2026-10-11 UTC: p95 680ms2026-10-12 UTC: p95 637ms2026-10-13 UTC: p95 630ms2026-10-14 UTC: p95 620ms2026-10-15 UTC: p95 633ms2026-10-16 UTC: p95 671ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
US-West
1.6sp95 · 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-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 686ms2026-10-06 UTC: p95 723ms2026-10-07 UTC: p95 743ms2026-10-08 UTC: p95 751ms2026-10-09 UTC: p95 856ms2026-10-10 UTC: p95 683ms2026-10-11 UTC: p95 671ms2026-10-12 UTC: p95 804ms2026-10-13 UTC: p95 733ms2026-10-14 UTC: p95 851ms2026-10-15 UTC: p95 707ms2026-10-16 UTC: p95 778ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
Europe
731msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 608ms2026-10-06 UTC: p95 644ms2026-10-07 UTC: p95 635ms2026-10-08 UTC: p95 633ms2026-10-09 UTC: p95 676ms2026-10-10 UTC: p95 632ms2026-10-11 UTC: p95 590ms2026-10-12 UTC: p95 774ms2026-10-13 UTC: p95 575ms2026-10-14 UTC: p95 721ms2026-10-15 UTC: p95 642ms2026-10-16 UTC: p95 554ms2026-10-17 UTC: p95 899ms2026-10-18 UTC: p95 970ms2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 844ms2026-10-21 UTC: p95 706ms2026-10-22 UTC: p95 731ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.5s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.3s
Sep 23Oct 7Oct 22
US-Central
930msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 829ms2026-10-06 UTC: p95 825ms2026-10-07 UTC: p95 803ms2026-10-08 UTC: p95 736ms2026-10-09 UTC: p95 892ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 883ms2026-10-12 UTC: p95 942ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 759ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 949ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 892ms2026-10-22 UTC: p95 930ms
Sep 23Oct 7Oct 22
Canada
1.4sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 747ms2026-10-06 UTC: p95 729ms2026-10-07 UTC: p95 630ms2026-10-08 UTC: p95 686ms2026-10-09 UTC: p95 548ms2026-10-10 UTC: p95 646ms2026-10-11 UTC: p95 686ms2026-10-12 UTC: p95 709ms2026-10-13 UTC: p95 916ms2026-10-14 UTC: p95 797ms2026-10-15 UTC: p95 868ms2026-10-16 UTC: p95 902ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
UK
469msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 621ms2026-10-06 UTC: p95 606ms2026-10-07 UTC: p95 548ms2026-10-08 UTC: p95 566ms2026-10-09 UTC: p95 770ms2026-10-10 UTC: p95 873ms2026-10-11 UTC: p95 924ms2026-10-12 UTC: p95 871ms2026-10-13 UTC: p95 806ms2026-10-14 UTC: p95 762ms2026-10-15 UTC: p95 735ms2026-10-16 UTC: p95 718ms2026-10-17 UTC: p95 749ms2026-10-18 UTC: p95 968ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 999ms2026-10-21 UTC: p95 408ms2026-10-22 UTC: p95 469ms
Sep 23Oct 7Oct 22
Southeast Asia
2.8sp95 · 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-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.5s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.8s
Sep 23Oct 7Oct 22
Australia
2.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.7s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 3.1s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 3.2s2026-10-20 UTC: p95 2.9s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22
South America
2.4sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.4s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 983ms2026-10-11 UTC: p95 951ms2026-10-12 UTC: p95 998ms2026-10-13 UTC: p95 987ms2026-10-14 UTC: p95 956ms2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22

Check your own site while you wait on MongoDB Atlas

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.

Email me when MongoDB Atlas reports an incident on its status page, and again when it reports it resolved.

Get an email when MongoDB Atlas reports an incident

Email me when MongoDB Atlas reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is MongoDB Atlas's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1203msstatus code: 401checked: Oct 22, 2026, 7:04 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
      Checks passinglatency: 1346msstatus code: 401checked: Oct 22, 2026, 6:57 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
      Checks passinglatency: 335msstatus code: 401checked: Oct 22, 2026, 6:59 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
      Checks passinglatency: 977msstatus code: 401checked: Oct 22, 2026, 6:58 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
    Checks passinglatency: 1811msstatus code: 401checked: Oct 22, 2026, 6: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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 601msstatus code: 401checked: Oct 22, 2026, 7:00 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
      Checks passinglatency: 2374msstatus code: 401checked: Oct 22, 2026, 6:58 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2228msstatus code: 401checked: Oct 22, 2026, 7:04 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
      Checks passinglatency: 1716msstatus code: 401checked: Oct 22, 2026, 7:01 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
      Checks passinglatency: 979msstatus code: 401checked: Oct 22, 2026, 6:58 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 probe events

GCP Availability Zone europe-west2-b connectivity issues, 12h 36mdeclared on their status page2026-10-20
Issue impacting Atlas Search availability on certain clusters, 1h 48mdeclared on their status page2026-10-09
Admin Admin API: Intermittent Increase in 5xx errors, 2h 35mdeclared on their status page2026-10-09
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

check 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 check readings and MongoDB Atlas's own claim at the time, side by side.

Full check history for MongoDB Atlas: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![MongoDB Atlas uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is MongoDB Atlas down?", https://realuptime.io/outages/mongodb-atlas. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://cloud.mongodb.com/api/atlas/v2/groups
secondary
https://status.mongodb.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: cloud.mongodb.com

RealUptime is not affiliated with MongoDB Atlas; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.