MongoDB incident
MongoDB Atlas for Government: SSO login failures for some users
MongoDB experienced a minor incident on March 19, 2026 affecting MongoDB Atlas for Government, lasting 12d 20h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Mar 19, 2026, 12:24 AM UTC
Impact: Some users may be unable to log into the Atlas for Government UI using SSO. Specifically, users accessing Atlas for Government via a saved SSO login URL may receive an error, and users attempting to log in via a federated identity provider link may be unable to complete authentication. Root cause: We have identified an issue with SSO routing that is preventing some federated login flows from completing successfully. These issues started around 2026-03-18 2:30 UTC. What you might see: - A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL. - An inability to complete login when using a federated identity provider link. Our actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users. User action: As a workaround, users can log in by entering their email address directly at https://account.mongodbgov.com and following the standard prompts. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as we progress toward resolution, or if we observe any change in impact to Atlas for Government.
- monitoring Mar 19, 2026, 10:15 PM UTC
A fix has been implemented and we are monitoring the results. Users who were previously unable to log in via SSO should now be able to authenticate successfully.
- resolved Mar 31, 2026, 09:19 PM UTC
This incident has been resolved.