Skip to content

MongoDB Atlas status · mongodb.com

Is MongoDB Atlas Down Today?

Managed MongoDB database.

Cloudmongodb.com
Report an issue

No, MongoDB Atlas is not down

mongodb.com is currently up. Our monitoring probes can reach mongodb.com and complete a check without errors. Latest response time was 236 ms. The latest automated check was run 2026-08-14 18:20 UTC from primary location.

Current status
Operational

Currently up for 2h 38m

Last check
Checked every 3 minutes

Latest 2026-08-14 18:20 UTC · Primary location

Last 24 hours
100%

1 incident, 1d down

Official status
Operational
Our check
Operational
Active incident
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
Last outage
2026-03-01
Response time
236 ms
User reports
Normal

None today

MongoDB Atlas live status

9 of 9 operational

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

Current incident

  • Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)

    MonitoringPartial outage

    AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the...

    Started · 2026-03-01 13:48 UTC

    Official incident update

    1. 2026-03-01 13:48 UTCIdentified

      Impact: Some Atlas customers with deployments in the AWS me-central-1 (United Arab Emirates) region may experience delays in cluster operations (for example, creating, scaling, or modifying clusters and infrastructure-level maintenance tasks). Root cause: AWS is reporting connectivity and power issues affecting APIs and instances in a single Availability Zone in the me-central-1 Region, which ...

    2. 2026-03-01 14:55 UTCIdentified

      Update: One or more instances backing MongoDB Atlas clusters in the AWS ME-CENTRAL-1 (United Arab Emirates) region may have been temporarily unavailable due to an underlying AWS issue in a single Availability Zone . According to AWS, a localized power issue in this Availability Zone has affected connectivity and power for some APIs and instances, and may have caused increased errors, latency, o...

    3. 2026-03-01 19:30 UTCIdentified

      Update: We are continuing to monitor an ongoing issue in AWS me-central-1 (United Arab Emirates) caused by an underlying AWS infrastructure disruption isolated to a single Availability Zone. Please visit the AWS Health Dashboard for detailed information on the Availability Zone outage (https://health.aws.amazon.com/health/status). If you have time-sensitive changes that are blocked and need ur...

    4. 2026-03-02 02:17 UTCIdentified

      Update: We are continuing to monitor an ongoing issue in AWS me-central-1 (United Arab Emirates) caused by an underlying AWS infrastructure disruption isolated to a single Availability Zone. Please visit the AWS Health Dashboard for detailed information on the Availability Zone outage (https://health.aws.amazon.com/health/status). If you have time-sensitive changes that are blocked and need ur...

    5. 2026-03-02 09:20 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience outages. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. CURRENT IMPACT Atlas clusters deployed only in me-central-1 may be fully unavailable. For clusters operating solely in me-central-1, backup operations in th...

    6. 2026-03-02 19:58 UTCIdentified

      CURRENT IMPACT According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. AWS is currently experiencing infrastructure impairments in two Middle East regions: * ME-CENTRAL-1 (Middle East – Central): Two Availabi...

    7. 2026-03-03 17:20 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to c...

    8. 2026-03-03 22:54 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to c...

    9. 2026-03-04 06:03 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to c...

    10. 2026-03-04 16:33 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to c...

    11. 2026-03-05 14:59 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, ...

    12. 2026-03-06 14:24 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in the United States, Europe, or Asia Pacific, ...

    13. 2026-03-07 15:28 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as a...

    14. 2026-03-08 15:42 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as a...

    15. 2026-03-09 16:02 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as a...

    16. 2026-03-10 15:59 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as a...

    17. 2026-03-11 15:48 UTCIdentified

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as a...

    18. 2026-03-18 15:51 UTCMonitoring

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as a...

    19. 2026-03-25 15:33 UTCMonitoring

      According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience impairments. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We continue to assist customers in their chosen remediation path to the extent possible. We encourage customers running workloads in the Middle East to c...

    20. 2026-03-26 21:35 UTCMonitoring

      Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, clusters in me-south-1 cannot be modified and may be unable to process normal operations. We strongly recommend that customers with workloads in the affected regions act now to move their clusters to alternate regions instead of waiting for full availability to be restored. We continu...

    21. 2026-04-01 16:02 UTCMonitoring

      Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. We strongly recommend that customers with workloads in AWS me-central-1 act now to mo...

    22. 2026-04-08 15:33 UTCMonitoring

      Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. We strongly recommend that customers with workloads in AWS me-central-1 act now to mo...

    23. 2026-05-06 16:02 UTCMonitoring

      AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the...

    24. 2026-06-03 15:46 UTCMonitoring

      AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the...

Response time

Latest 167 ms

Loading response-time chart…

Uptime

Availability from independent checks, with recorded incidents and downtime in each window.

Today

100%

1 incident, 18h 28m down

Last 7 days

100%

1 incident, 7d down

Last 30 days

100%

1 incident, 30d down

Last 365 days

100%

1 incident, 166d 4h down

Latest MongoDB Atlas incidents

Recorded outages with duration and start time.

Last recorded 2026-03-01 13:48 UTC

IncidentDurationStarted

Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)

Monitoring
Ongoing2026-03-01 13:48 UTC

How this status checker works

Who's Down Today monitors MongoDB Atlas independently of the company that runs it. We send reachability checks from our primary location every 3 minutes and record response time, HTTP errors, and timeouts.

When MongoDB Atlas publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.

This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.

Frequently asked questions

Is MongoDB Atlas down right now?

No. No, MongoDB Atlas is not down. Who's Down Today shows MongoDB Atlas as operational based on the latest official signals and independent checks. If you still cannot reach mongodb.com, the issue may be local to your connection, DNS, VPN, browser, or device.

Is MongoDB Atlas down for everyone or just me?

Who's Down Today currently shows MongoDB Atlas as operational from our monitoring location, which means mongodb.com is responding normally to our checks. If you are still having trouble, try another browser, device, or network, and check DNS or VPN settings.

What should I do if mongodb.com is up but I still cannot access it?

Try opening mongodb.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed MongoDB Atlas outage.

How does Who's Down Today check if MongoDB Atlas is down?

We combine independent HTTP reachability checks with public status information where it exists. When MongoDB Atlas publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.

What does a MongoDB Atlas outage mean?

An outage on this page means recorded incidents or failed checks indicated that MongoDB Atlas was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.

Can this page tell me the root cause of a MongoDB Atlas outage?

Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to MongoDB Atlas's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.

How do I report an issue with MongoDB Atlas?

Use the report form on this page if MongoDB Atlas looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.