← Live dashboard

MongoDB Atlas for Government: SSO login failures for some users

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Mar 19, 2026, 12:24 AM · Resolved Mar 31, 2026, 09:19 PM

This incident has been resolved.

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with MongoDB Atlas now? Check the current status

Affected services

MongoDB Atlas for Government

Updates (3)

  1. Mar 31, 2026, 09:19 PM
    MongoDB Atlas for Government: SSO login failures for some users

    This incident has been resolved.

    MongoDB Atlas ↗
  2. Mar 19, 2026, 10:15 PM
    MongoDB Atlas for Government: SSO login failures for some users

    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.

    MongoDB Atlas ↗
  3. Mar 19, 2026, 12:24 AM
    MongoDB Atlas for Government: SSO login failures for some users

    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 inabil

    MongoDB Atlas ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow MongoDB Atlas's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.