Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for MongoDB and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for MongoDB.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
MongoDB Atlas App Services and Device Sync | Active |
MongoDB Atlas Data Federation and Online Archive | Active |
MongoDB Atlas for Government | Active |
MongoDB Atlas Stream Processing | Active |
MongoDB Charts | Active |
MongoDB Cloud | Active |
MongoDB Support Portal | Active |
View the latest incidents for MongoDB and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 11, 2024, 9:07 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 11, 2024, 4:52 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: June 4, 2024, 4:42 p.m.
Description: ### **Incident Summary** Between June 3rd 2024, 18:24 UTC and June 4th, 1:21 UTC, MongoDB Atlas customers across all commercial regions experienced degradation of the following functionalities. Changes to cluster configuration, both in response to API calls and automated triggers \(e.g., auto-scaling or node replacement\) were executed with delays varying between a few minutes and several hours. Similar delays applied to Alert processing, impacting both the Atlas built-in Alert functionality and integrations such as Datadog and PagerDuty. Part of the daily cost tabulation for compute, storage and data transfer on June 3rd will be delayed to June 6th or June 7th. Lower granularities of cluster metrics were unavailable until up to 1:56 UTC. Finally, the Data Explorer and Realtime Performance Panel UIs were impaired for several hours. ### **Root Cause** The root cause of this incident was an unexpected failure during an Atlas internal maintenance activity. A planned migration of metadata for an internal workflow management system that backs the Atlas control plane resulted in unexpected resource congestion on the target database cluster as traffic was redirected to the target. This issue did not occur during pre-production testing. The rollback process required complex reconciliation of data in the source and target databases, delaying recovery. ### **MongoDB Actions** The MongoDB Atlas team is designing a new metadata migration strategy for future maintenance activities. This process will allow for rollback within less than 15 minutes of detecting a potential issue. We will not execute similar maintenance activities until this procedure is implemented and thoroughly tested. ### Recommended Customer Actions This issue was fully eliminated by the MongoDB Atlas team and does not require customer action.
Status: Postmortem
Impact: Major | Started At: June 3, 2024, 6:45 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 23, 2024, 9:26 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.