Skip to content

Outage tracker / MongoDB Atlas

Is MongoDB Atlas down?

Short linkrlup.io/down/mongodb-atlas

I'm having a problem

Operationalchecked 23 minutes ago

We reached MongoDB Atlas from all 4 regions we check.

Functional endpoints verified

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

our independent probeslive · checked Sep 3, 2026, 1:08 AM UTC
US-East380 msOperational
US-West1480 msOperational
Europe529 msOperational
Asia-Pacific1682 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 Sep 3, 2026, 12:26 AM UTC
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

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
710msp95 · 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-08-20 UTC: p95 414ms2026-08-21 UTC: p95 528ms2026-08-22 UTC: p95 656ms2026-08-23 UTC: p95 536ms2026-08-24 UTC: p95 335ms2026-08-25 UTC: p95 627ms2026-08-26 UTC: p95 794ms2026-08-27 UTC: p95 971ms2026-08-28 UTC: p95 893ms2026-08-29 UTC: p95 709ms2026-08-30 UTC: p95 683ms2026-08-31 UTC: p95 854ms2026-09-01 UTC: p95 949ms2026-09-02 UTC: p95 915ms2026-09-03 UTC: p95 710ms
Aug 5Aug 19Sep 3
US-West
1.8sp95 · 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-08-20 UTC: p95 632ms2026-08-21 UTC: p95 685ms2026-08-22 UTC: p95 1.2s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.5s2026-08-28 UTC: p95 1.4s2026-08-29 UTC: p95 1.4s2026-08-30 UTC: p95 1.5s2026-08-31 UTC: p95 1.5s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.5s2026-09-03 UTC: p95 1.8s
Aug 5Aug 19Sep 3
Europe
402msp95 · 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-08-20 UTC: p95 476ms2026-08-21 UTC: p95 555ms2026-08-22 UTC: p95 510ms2026-08-23 UTC: p95 734ms2026-08-24 UTC: p95 760ms2026-08-25 UTC: p95 682ms2026-08-26 UTC: p95 699ms2026-08-27 UTC: p95 627ms2026-08-28 UTC: p95 674ms2026-08-29 UTC: p95 790ms2026-08-30 UTC: p95 550ms2026-08-31 UTC: p95 742ms2026-09-01 UTC: p95 861ms2026-09-02 UTC: p95 706ms2026-09-03 UTC: p95 402ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.9sp95 · 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-08-20 UTC: p95 1.5s2026-08-21 UTC: p95 1.5s2026-08-22 UTC: p95 1.4s2026-08-23 UTC: p95 1.6s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.7s2026-08-27 UTC: p95 1.5s2026-08-28 UTC: p95 1.5s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.4s2026-09-02 UTC: p95 2.0s2026-09-03 UTC: p95 1.9s
Aug 5Aug 19Sep 3

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.

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

  • US-East
    Operationallatency: 380msstatus code: 401checked: Sep 3, 2026, 1:04 AM 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: 1480msstatus code: 401checked: Sep 3, 2026, 1:03 AM 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.
  • Europe
    Operationallatency: 529msstatus code: 401checked: Sep 3, 2026, 1:08 AM 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.
  • Asia-Pacific
    Operationallatency: 1682msstatus code: 401checked: Sep 3, 2026, 1:08 AM 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.
  • US-Central
    Not monitored from this regionMongoDB Atlas is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionMongoDB Atlas is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionMongoDB Atlas is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionMongoDB Atlas is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionMongoDB Atlas is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionMongoDB Atlas is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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 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
Atlas UI and API Periodic Unavailability, 1h 6mdeclared on their status page2026-08-18
GCP capacity constraints affecting Atlas deployments, 6h 57mdeclared on their status page2026-08-05
Elevated errors on VoyageAI APIs, 2h 31mdeclared on their status page2026-08-03
Delayed cluster configuration affecting free and flex users, 42mdeclared on their status page2026-07-29
Atlas Stream Processing errors in Azure West Europe, 4h 35mdeclared on their status page2026-07-29
VoyageAI elevated errors, 11mdeclared on their status page2026-07-27

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

Tell me when this goes down

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.

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 337h 31m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 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 4 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. MongoDB Atlas operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)