outages.live
Live

MongoDB Atlas

MongoDB Atlas is operational

Checked 14 s ago Operational

Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

MongoDB Atlas reports impaired cluster operations in AWS me-central-1 and AWS me-south-1. MongoDB Cloud is affected. The provider continues to monitor for further issues.

Partial outageupdated 59 d ago

History

90 days agoToday

Incidents in 90 days

13

Days with an incident

90

Median duration

5 h 7 min

Longest incident

186 days

Components

10
MongoDB Cloud Operational
90 days ago90 days with an incidentToday
MongoDB Support Portal Operational
90 days ago1 day with an incidentToday
MongoDB Atlas App Services and Device Sync Operational
90 days ago1 day with an incidentToday
MongoDB Atlas Data Federation and Online Archive Operational
90 days agoNo incidentsToday
MongoDB Atlas Search Operational
90 days ago1 day with an incidentToday
MongoDB Charts Operational
90 days ago1 day with an incidentToday
MongoDB Atlas Stream Processing Operational
90 days agoNo incidentsToday
MongoDB Atlas for Government Operational
90 days ago1 day with an incidentToday
VoyageAI Embedding and Reranking Models Operational
90 days agoNo incidentsToday
MongoDB Atlas Agent Engine Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration12 h 36 min07:32 to 20:09GCP Availability Zone europe-west2-b connectivity issuesDegraded

This incident has been resolved.

Oct 9, 2026

Duration1 h 48 min16:29 to 18:17Issue impacting Atlas Search availability on certain clustersPartial outage

This incident has been resolved.

Duration2 h 35 min13:11 to 15:46Admin Admin API: Intermittent Increase in 5xx errorsNotice

This incident has been resolved.

Oct 2, 2026

Duration5 h00:01 to 05:02MongoDB Charts: Infinite login loop when creating new Charts projectsDegraded

This incident has been resolved.

Oct 1, 2026

Duration5 h 13 min15:41 to 20:54Trigger processing may be delayed globallyPartial outage

This incident has been resolved.

Sep 30, 2026

Duration2 h 10 min18:51 to 21:02Delays in Atlas cluster management operationsNotice

This incident has been resolved.

Sep 16, 2026

Duration6 h 25 min09:06 to 15:31Support Portal OutagePartial outage

The MongoDB Support Portal experienced service degradation issues between approximately 2026-09-16 09:00 UTC and 2026-09-16 15:15 UTC. These platform issues have been resolved. We apologize for the service interruption and greatly appreciate your patience. Regards, The MongoDB Team

Sep 11, 2026

Duration2 h 23 min01:28 to 03:51Atlas is experiencing issues with issuing certificates from Lets EncryptDegraded

This incident has been resolved.

Aug 19, 2026

Duration25 h 21 min20:45 to 22:07Issues rotating certificates for projects containing only Atlas Free and Flex clustersNotice

This incident has been resolved.

Aug 18, 2026

Duration1 h 6 min14:10 to 15:17Atlas UI and API Periodic UnavailabilityDegraded

This incident has been resolved. Following the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes. The issue was related to this incident "Atlas UI and API Periodic Unavailability" which has been remediated. Customer clusters and their data were not affected; the impact was limited to the timing of control-plane operations. This jobs issue has been resolved as well.

Aug 5, 2026

Duration6 h 57 min05:17 to 12:14GCP capacity constraints affecting Atlas deploymentsPartial outage

We believe the symptoms of this have largely subsided, looking at both customer cases and our internal metrics. We will share any more information as we get it, but for now resolving this incident as Atlas is fully operational.

Mar 1, 2026

Duration186 days19:30 to 16:47Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Partial outage

While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status We will update this post as necessary. Thanks in advance for your understanding.

Follow MongoDB Atlas

Your coding agent knows when MongoDB Atlas is down, and tells you when a failure is theirs, not yours. You can also get MongoDB Atlas incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mongodb" and tell me if MongoDB Atlas has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=mongodb
Slack
/feed subscribe https://outages.live/feed.xml?providers=mongodb

Go from tracking outages to fixing production issues with Polylane.

Try Polylane