MongoDB incident
Issue connecting to Atlas Data Federation and Online Archive
MongoDB experienced a major incident on December 19, 2025 affecting MongoDB Cloud and MongoDB Atlas Data Federation and Online Archive and 1 more component, lasting 2h 43m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 19, 2025, 09:45 PM UTC
We are investigating report of issues connecting and authenticating to Atlas Data Federation and Online Archive instances.
- investigating Dec 19, 2025, 09:46 PM UTC
We are continuing to investigate this issue.
- identified Dec 19, 2025, 09:51 PM UTC
We have identified an issue causing the following symptoms: - Atlas Data Explorer connections and queries failing - Atlas Data Federation and Online Archive queries failing - Atlas Stream Processing being interrupted - MongoDB Charts data being delayed Affected users will see the above symptoms, often with timeout or host not found errors. Underlying cluster health is unaffected, including Atlas search queries.
- identified Dec 19, 2025, 09:57 PM UTC
We have identified an issue causing the following symptoms: - Atlas Data Explorer connections and queries failing - Atlas Data Federation and Online Archive queries failing, as well as the creation of new Data Federation or Online Archive instances - Atlas Stream Processing being interrupted - MongoDB Charts data being delayed Affected users will see the above symptoms, often with timeout or host not found errors. Underlying cluster health is unaffected, including Atlas search queries. Additionally, Vercel users may not be able to get directly to Atlas from within Vercel. As a workaround, users are encouraged to login directly to Atlas at cloud.mongodb.com
- monitoring Dec 19, 2025, 10:42 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 20, 2025, 12:28 AM UTC
Issue is resolved, and affected components are confirmed to be operational again.