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.
State
Monitoring
Started
59 d ago
2026-09-03 16:44 UTC
Ongoing for
59 days
Worst impact
Partial outage
Timeline
1 updateMonitoring
59 days 100%
Updates
Times in UTCAs posted by MongoDB Atlas
We are continuing to monitor for any further issues.
Affected components
1MongoDB Atlas in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
90
Median duration
5 h 7 min
This incident
279× the median
Other MongoDB Atlas incidents
All incidentsMongoDB Atlas·GCP Availability Zone europe-west2-b connectivity issues
This incident has been resolved.
MongoDB Atlas·Issue impacting Atlas Search availability on certain clusters
This incident has been resolved.
MongoDB Atlas·Admin Admin API: Intermittent Increase in 5xx errors
This incident has been resolved.
MongoDB Atlas·MongoDB Charts: Infinite login loop when creating new Charts projects
This incident has been resolved.
MongoDB Atlas·Trigger processing may be delayed globally
This incident has been resolved.
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.
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.
https://outages.live/feed.xml?providers=mongodb/feed subscribe https://outages.live/feed.xml?providers=mongodbFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane