Atlas UI and API Periodic Unavailability
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.
The latest update from MongoDB Atlas.
State
Resolved
Started
75 d ago
2026-08-18 14:10 UTC
Lasted
1 h 6 min
until 2026-08-18 15:17 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
46 min 70%
Identified
7 min 11%
Monitoring
13 min 19%
Updates
Times in UTCAs posted by MongoDB Atlas
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.
We have disabled the workload and are monitoring the situation
We have identified a new workload that was putting more load than expected on the backing system. We are working on disabling it. Customer clusters remain unaffected.
We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.
Affected components
1MongoDB Atlas in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
90
Median duration
5 h
This incident
78% shorter than 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.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