MongoDB Atlas reported this minor-impact incident on its official status page on Feb 19, 2026, 18:50 UTC. It was resolved after 22h 9m.
Right now MongoDB Atlas is operational. Live MongoDB Atlas status →
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate reports of Atlas Data Federation and Online Archive schema tables failing to load. As a workaround, please connect directly and run the sqlGetSchema command: https://www.mongodb.com/docs/sql-interface/schema/view/ If that does not work, you may need to generate the schema first: https://www.mongodb.com/docs/sql-interface/schema/create/#create-schema-using-mongosh It appears to affect only a very small number of users, but we will keep this alert open until the issue is resolved.
We are investigating reports of Atlas Data Federation and Online Archive schema tables failing to load. As a workaround, please connect directly and run the sqlGetSchema command: https://www.mongodb.com/docs/sql-interface/schema/view/ If that does not work, you may need to generate the schema first: https://www.mongodb.com/docs/sql-interface/schema/create/#create-schema-using-mongosh
Our 5-minute checks didn't record a change in MongoDB Atlas's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history