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. The provider continues to monitor for further issues.
A language model wrote this summary from the updates of MongoDB Atlas.
State
Monitoring
Started
58 d ago
2026-09-03 16:44 UTC
Ongoing for
58 days
Worst impact
Partial outage
Timeline
1 updateMonitoring
58 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
1
Days with an incident
60
Median duration
Not enough data
This incident
Not comparable
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.cc/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.cc/feed.xml?providers=mongodb/feed subscribe https://outages.cc/feed.xml?providers=mongodbFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane